I'm not an experienced user, I managed to install, configure and maintain my server thanks to this forum and hundreds of hours of videos on YouTube. Thanks for that!
But now there's a wall in front of my knowledge and none of the research I've done in the last few days has helped me... probably something stupid that I'm missing. Let's go.
I have an LXC container configured as a VPN which has been working well for years, I use this container as a gateway for others that need to go through a VPN, like qbit, etc.
My problem started when I migrated from a domestic Huawei router to a TP-Link Omada, where I separated my network into two VLANs, one for the Proxmox and one for the rest of the house.
- Proxmox got 192.168.3.X
- The home network 192.168.10.X
Since then I have not been able to access, for example, the container with the qbit from my PC 192.168.10.4 > 192.168.3.102.
I believe the problem is in the LXC VPN configuration, since the other containers and VMs on the 192.168.3.X network are accessible through 192.168.10.X.
Only those behind the VPN and the VPN itself have a problem.
What I've already tried.
Edit the IP TABLE, used in VPN configuration, to include:
ORIGINAL SETUP Which worked fine when there were no VLANs
CONFIGURATION INSERTED TO TRY TO RESOLVE THE PROBLEM
Did not work.
What am I missing?
Thanks!
But now there's a wall in front of my knowledge and none of the research I've done in the last few days has helped me... probably something stupid that I'm missing. Let's go.
I have an LXC container configured as a VPN which has been working well for years, I use this container as a gateway for others that need to go through a VPN, like qbit, etc.
My problem started when I migrated from a domestic Huawei router to a TP-Link Omada, where I separated my network into two VLANs, one for the Proxmox and one for the rest of the house.
- Proxmox got 192.168.3.X
- The home network 192.168.10.X
Since then I have not been able to access, for example, the container with the qbit from my PC 192.168.10.4 > 192.168.3.102.
I believe the problem is in the LXC VPN configuration, since the other containers and VMs on the 192.168.3.X network are accessible through 192.168.10.X.
Only those behind the VPN and the VPN itself have a problem.
What I've already tried.
Edit the IP TABLE, used in VPN configuration, to include:
ORIGINAL SETUP Which worked fine when there were no VLANs
Bash:
# Make sure that you can communicate within your own network
iptables -A INPUT -s 192.168.3.0/24 -d 192.168.3.0/24 -j ACCEPT
iptables -A OUTPUT -s 192.168.3.0/24 -d 192.168.3.0/24 -j ACCEPT
CONFIGURATION INSERTED TO TRY TO RESOLVE THE PROBLEM
Bash:
# Make sure that you can communicate within your own network
iptables -A INPUT -s 192.168.10.0/24 -d 192.168.10.0/24 -j ACCEPT
iptables -A OUTPUT -s 192.168.10.0/24 -d 192.168.10.0/24 -j ACCEPT
# Allow traffic from network 192.168.3.0/24 to network 192.168.10.0/24
iptables -A FORWARD -s 192.168.3.0/24 -d 192.168.10.0/24 -j ACCEPT
# Allow traffic from network 192.168.10.0/24 to network 192.168.3.0/24
iptables -A FORWARD -s 192.168.10.0/24 -d 192.168.3.0/24 -j ACCEPT
Did not work.
What am I missing?
Thanks!
Last edited: