| 1 |
On Sunday, 10 June 2018 19:07:59 BST Wol's lists wrote: |
| 2 |
> On 10/06/18 17:53, Mick wrote: |
| 3 |
> > On Sunday, 10 June 2018 01:31:50 BST Hilco Wijbenga wrote: |
| 4 |
> >> Okay, with all that advice, I gave it another try. I'm also setting up |
| 5 |
> >> a VirtualBox for my WFH stuff and VB wants to use 10.0.0.0 for its |
| 6 |
> >> networking. I've changed this to 172.16.0.0 so now I can easily tell |
| 7 |
> >> that network from work network (which seems to use 10.25.0.0) |
| 8 |
> >> |
| 9 |
> >> I wanted to add a route to NetworkManager's VPN connection. It wants |
| 10 |
> >> Address, Network, Gateway, and Metric so I gave it "10.0.0.0", |
| 11 |
> >> "255.0.0.0" (this one shows up automatically), "207.x.y.z", "1". But |
| 12 |
> >> then VPN fails to start with the complaint that the configuration is |
| 13 |
> >> invalid. |
| 14 |
> >> |
| 15 |
> >> So I tried what I think is the same on the CL: |
| 16 |
> >> |
| 17 |
> >> $> route add -net 10.0.0.0/8 gw "207.x.y.z" metric 1 |
| 18 |
> >> SIOCADDRT: Network is unreachable |
| 19 |
> >> |
| 20 |
> >> So apparently, it's not quite as straightforward as I thought it might |
| 21 |
> >> be. |
| 22 |
> >> |
| 23 |
> >> :-) |
| 24 |
> > |
| 25 |
> > Ahh! If you're trying to set this up within a VM, this adds a whole new |
| 26 |
> > layer of complexity. I assume you're setting up a bridge between host |
| 27 |
> > and guest device(s)? |
| 28 |
> |
| 29 |
> No if he's assigned 172.16/16 to the VM network he hasn't. VB defaults |
| 30 |
> to a NAT'd network and it's always given me grief. I was going to |
| 31 |
> suggest he switched to bridged. |
| 32 |
> |
| 33 |
> In settings, change the network adaptor type to bridged, and then the VM |
| 34 |
> will get its settings and IP address from the DHCP server serving the |
| 35 |
> local network. Makes things MUCH easier. |
| 36 |
> |
| 37 |
> Cheers, |
| 38 |
> Wol |
| 39 |
|
| 40 |
If NAT'ed between guest and host and then NAT'ed again at the home router, you |
| 41 |
are double NAT'ed. As far as I know VPNs will not work through a double NAT |
| 42 |
situation, unless you use your gateway or host as the VPN end point and then |
| 43 |
setup port forwarding to the host from there. Bridge the host to guest |
| 44 |
adaptors and you should be good to go (once any other conventionla VPN |
| 45 |
configuration problem is solved). :-) |
| 46 |
|
| 47 |
-- |
| 48 |
Regards, |
| 49 |
Mick |
Archives