View previous topic :: View next topic |
Author |
Message |
zebbedi Tux's lil' helper
Joined: 05 Sep 2003 Posts: 123
|
Posted: Fri Jan 26, 2018 11:08 am Post subject: PPP, VPN and tunnel all mode |
|
|
I'm using NetExtender vpn client at work which uses ppp under the hood. This worked fine but I need to use 'tunnel all' mode.
On all our other ubuntu machines this works fine, however on my gentoo machine it doesn't. It connects, but I can't then access anything and I can't work out why. It doesn't seem to be setting a default route properly.
After my vpn account is changed to tunnel all and i connect, i get this:
Code: | default via 192.168.180.42 dev ppp0 scope link
default via 192.168.0.1 dev wlp2s0 proto static metric 600
10.10.0.0/16 via 192.168.180.42 dev ppp0 scope link
128.0.0.0/1 via 192.168.180.42 dev ppp0 scope link
172.17.0.0/16 via 192.168.180.42 dev ppp0 scope link
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.0.2.1 via 192.168.180.42 dev ppp0 scope link
192.0.2.1 dev ppp0 proto kernel scope link src 192.168.180.42
192.168.0.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.32 metric 600
192.168.36.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.37.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.40.0/21 via 192.168.180.42 dev ppp0 scope link
192.168.99.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.100.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.102.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.144.0/21 via 192.168.180.42 dev ppp0 scope link
192.168.160.0/21 via 192.168.180.42 dev ppp0 scope link
192.168.181.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.182.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.183.0/24 via 192.168.180.42 dev ppp0 scope link
192.168.184.0/24 via 192.168.180.42 dev ppp0 scope link
192.245.184.0/24 via 192.168.180.42 dev ppp0 scope link |
wlp2s0 is my wireless connection and ppp0 is the new interface that is created. Sorry if this isn't much information i'm not terribly good when it comes to networking. Can anyone help me work out why it doesn't work please? |
|
Back to top |
|
|
zebbedi Tux's lil' helper
Joined: 05 Sep 2003 Posts: 123
|
Posted: Fri Jan 26, 2018 2:08 pm Post subject: |
|
|
So i've finally managed to make it work, by running the following after connecting through the vpn:
Code: |
route add -net <vpn-ip> netmask 255.255.255.255 gw 192.168.0.1 dev enp0s20f0u2
|
But can anyone tell me why this works magically on ubuntu and not on gentoo? why am i missing the route? |
|
Back to top |
|
|
AngelKnight Tux's lil' helper
Joined: 14 Jan 2003 Posts: 127
|
Posted: Tue Feb 13, 2018 8:08 am Post subject: |
|
|
I've seen this a bunch with software that doesn't know how to add a specific route back to the VPN gateway host itself.
If you're looking for a "why was the software written this way" that lets you fix it within the software, I'm not sure there's an answer to that.
With the xl2tpd setups I've configured, the PPTP server can submit specific routes to inject into the client's routing table, but this information gets ignored and xl2tpd cuts off its own access to the target LNS.
Even with vanilla PPTP setups I've resigned myself to just shell scripting around this to add a specific route before turning the PPTP client on. |
|
Back to top |
|
|
|