| 1 |
Okay, with all that advice, I gave it another try. I'm also setting up |
| 2 |
a VirtualBox for my WFH stuff and VB wants to use 10.0.0.0 for its |
| 3 |
networking. I've changed this to 172.16.0.0 so now I can easily tell |
| 4 |
that network from work network (which seems to use 10.25.0.0) |
| 5 |
|
| 6 |
I wanted to add a route to NetworkManager's VPN connection. It wants |
| 7 |
Address, Network, Gateway, and Metric so I gave it "10.0.0.0", |
| 8 |
"255.0.0.0" (this one shows up automatically), "207.x.y.z", "1". But |
| 9 |
then VPN fails to start with the complaint that the configuration is |
| 10 |
invalid. |
| 11 |
|
| 12 |
So I tried what I think is the same on the CL: |
| 13 |
|
| 14 |
$> route add -net 10.0.0.0/8 gw "207.x.y.z" metric 1 |
| 15 |
SIOCADDRT: Network is unreachable |
| 16 |
|
| 17 |
So apparently, it's not quite as straightforward as I thought it might be. :-) |
Archives