| 1 |
On Sunday, 10 June 2018 01:31:50 BST Hilco Wijbenga wrote: |
| 2 |
> Okay, with all that advice, I gave it another try. I'm also setting up |
| 3 |
> a VirtualBox for my WFH stuff and VB wants to use 10.0.0.0 for its |
| 4 |
> networking. I've changed this to 172.16.0.0 so now I can easily tell |
| 5 |
> that network from work network (which seems to use 10.25.0.0) |
| 6 |
> |
| 7 |
> I wanted to add a route to NetworkManager's VPN connection. It wants |
| 8 |
> Address, Network, Gateway, and Metric so I gave it "10.0.0.0", |
| 9 |
> "255.0.0.0" (this one shows up automatically), "207.x.y.z", "1". But |
| 10 |
> then VPN fails to start with the complaint that the configuration is |
| 11 |
> invalid. |
| 12 |
> |
| 13 |
> So I tried what I think is the same on the CL: |
| 14 |
> |
| 15 |
> $> route add -net 10.0.0.0/8 gw "207.x.y.z" metric 1 |
| 16 |
> SIOCADDRT: Network is unreachable |
| 17 |
> |
| 18 |
> So apparently, it's not quite as straightforward as I thought it might be. |
| 19 |
> :-) |
| 20 |
|
| 21 |
Ahh! If you're trying to set this up within a VM, this adds a whole new layer |
| 22 |
of complexity. I assume you're setting up a bridge between host and guest |
| 23 |
device(s)? |
| 24 |
|
| 25 |
Grant may be better equipped to answer here how to configure this, it is |
| 26 |
beyond my amateurish skills ... |
| 27 |
|
| 28 |
-- |
| 29 |
Regards, |
| 30 |
Mick |
Archives