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