So i have VPN to family members homes, and I've recently started to segregate my network (VLAN's)
Everything on my physical interface (eno2 - 192.168.4.0/24) works fine accessing any VPN network. When i try access the VPN from VLAN2 (eno2.2 - 192.168.20.0/24) i get nothing.
Route Information:
Any ideas as to what the issue could be?
Everything on my physical interface (eno2 - 192.168.4.0/24) works fine accessing any VPN network. When i try access the VPN from VLAN2 (eno2.2 - 192.168.20.0/24) i get nothing.
Route Information:
[root@gateway ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default xx-xxx-xx-x.xxx 0.0.0.0 UG 0 0 0 eno1
10.20.0.0 10.20.0.2 255.255.255.0 UG 0 0 0 tun0
10.20.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
10.32.0.9 0.0.0.0 255.255.255.255 UH 0 0 0 torguard
xx.xxx.xx.0 0.0.0.0 255.255.192.0 U 0 0 0 eno1
192.168.1.0 192.168.110.2 255.255.255.0 UG 0 0 0 tun1
192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eno2
192.168.5.0 192.168.120.2 255.255.255.0 UG 0 0 0 tun2
192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eno2.2
192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eno2.3
192.168.40.0 0.0.0.0 255.255.255.0 U 0 0 0 eno2.4
192.168.110.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun1
192.168.120.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun2
[root@gateway ~]#Any ideas as to what the issue could be?
Share this post:
Responses (2)
-
Accepted Answer
Nick Howitt wrote:
That does not look like standard ClearOS! tun0 may be ClearOS OpenVPN where you've changed the subnet. tun1 is not standard ClearOS as the gateway is wrong for that, so it is not the normal clients-tcp.conf. tun2. I've no idea what tun2 is but it looks similar to tun1. Be careful if you've got rid of clients-tcp.conf or the OpenVPN may break and remember any update to the webconfig changes both clients.conf and clients-tcp.conf.
Have you gone into manual configuration with OpenVPN in the webconfig? If so the 'push "route ...."' lines for the VLANs have probably not been added to clients(-tcp).conf.
This is your standard ClearOS gateway system, the only thing I've done is, set everything up and removed the clients-tcp.conf as i don't need it. I don't make any changes via web interface, so this doesn't bother me.
tun0 is the usual ClearOS clients.conf for my laptops and phones. (who are able to access the VLAN2)
tun1 is a custom config for family member 1 and has all routes needed, including the route for the VLAN2.
tun2 is a custom config for family member 2 and has all routes needed
edit:
Well, things are just working now ... not sure what the hell happened
While replying to your post, i tried to ping and i shit you not, it now goes through! 
I am 100% sure i restarted the tunnels on both ends, triple checked the configurations, double checked my firewall rules... -
Accepted Answer
That does not look like standard ClearOS! tun0 may be ClearOS OpenVPN where you've changed the subnet. tun1 is not standard ClearOS as the gateway is wrong for that, so it is not the normal clients-tcp.conf. tun2. I've no idea what tun2 is but it looks similar to tun1. Be careful if you've got rid of clients-tcp.conf or the OpenVPN may break and remember any update to the webconfig changes both clients.conf and clients-tcp.conf.
Have you gone into manual configuration with OpenVPN in the webconfig? If so the 'push "route ...."' lines for the VLANs have probably not been added to clients(-tcp).conf.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »