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