| 1 |
On Friday, 8 June 2018 23:21:52 BST Grant Taylor wrote: |
| 2 |
> On 06/08/2018 03:31 PM, Hilco Wijbenga wrote: |
| 3 |
> > Sigh, I take it back. That causes the internal sites to no longer work. |
| 4 |
> |
| 5 |
> Okay. |
| 6 |
> |
| 7 |
> So you're on the proper track. |
| 8 |
> |
| 9 |
> I'm guessing the work network isn't a simple single prefix. Or at least |
| 10 |
> the VPN client doesn't route enough through the VPN. |
| 11 |
> |
| 12 |
> Check your routing table with the VPN connected. Is enough being routed |
| 13 |
> through? Do you need to add additional prefixes? |
| 14 |
> |
| 15 |
> If DNS is working properly for internal resources, make sure that what |
| 16 |
> they resolve to is routed through the VPN. |
| 17 |
|
| 18 |
I don't know what networkmanager offers in terms of VPN settings, but as Grant |
| 19 |
says you need to set split routing. As it currently is, everything is sent |
| 20 |
out through the tunnel and your work's router is not set up to route out to |
| 21 |
the Internet your VPN connection. |
| 22 |
|
| 23 |
If networkmanager does not get you what you want, you can do this with 'ip |
| 24 |
route'. Delete the default route, then set again the default route via the |
| 25 |
your local gateway: |
| 26 |
|
| 27 |
# ip route del default via 192.168.1.254 dev wlan0 |
| 28 |
# ip route add default via 192.168.1.254 dev wlan0 |
| 29 |
|
| 30 |
then create an additional route for the remote subnet if it's not there: |
| 31 |
|
| 32 |
# ip route add 10.10.20.0/24 via 172.16.1.1 dev wlan0 |
| 33 |
|
| 34 |
Where 10.10.20.0/24 is your work's subnet and 172.16.1.1 is the local VPN IP |
| 35 |
address for your PC. Something along these lines ought to work. |
| 36 |
|
| 37 |
-- |
| 38 |
Regards, |
| 39 |
Mick |
Archives