1 |
On 06/09/2018 06:31 PM, Hilco Wijbenga wrote: |
2 |
> Okay, with all that advice, I gave it another try. I'm also setting |
3 |
> up 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", "255.0.0.0" |
9 |
> (this one shows up automatically), "207.x.y.z", "1". But then VPN fails |
10 |
> to start with the complaint that the configuration is 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 |
18 |
> be. :-) |
19 |
|
20 |
I think you're actually quite close. |
21 |
|
22 |
I believe the reason NetworkManager's VPN and the route command are |
23 |
complaining are the same. |
24 |
|
25 |
Routing almost always wants the next hop, not the ultimate destination. |
26 |
|
27 |
Think about it this way, if you ask for directions in an unfamiliar |
28 |
building, do you want to be told that you need to go to the office |
29 |
across the hall from Mary? Or do you want to be told, take the elevator |
30 |
tot he 4th floor, turn left, and go to the office across the haul from |
31 |
Mary, she has a big sign on her office. |
32 |
|
33 |
"Across the haul from Mary" by itself is useless and unactionable. The |
34 |
directions that start with the elevator in the lobby is actionable. ;-) |
35 |
|
36 |
|
37 |
|
38 |
-- |
39 |
Grant. . . . |
40 |
unix || die |