On 06/09/2018 06:31 PM, Hilco Wijbenga wrote:
Okay, with all that advice, I gave it another try. I'm also setting
up a VirtualBox for my WFH stuff and VB wants to use 10.0.0.0 for its
networking. I've changed this to 172.16.0.0 so now I can easily tell
that network from work network (which seems to use 10.25.0.0)
I wanted to add a route to NetworkManager's VPN connection. It wants
Address, Network, Gateway, and Metric so I gave it "10.0.0.0", "255.0.0.0"
(this one shows up automatically), "207.x.y.z", "1". But then VPN fails
to start with the complaint that the configuration is invalid.
So I tried what I think is the same on the CL:
$> route add -net 10.0.0.0/8 gw "207.x.y.z" metric 1
SIOCADDRT: Network is unreachable
So apparently, it's not quite as straightforward as I thought it might
be. :-)
I think you're actually quite close.
I believe the reason NetworkManager's VPN and the route command are
complaining are the same.
Routing almost always wants the next hop, not the ultimate destination.
Think about it this way, if you ask for directions in an unfamiliar
building, do you want to be told that you need to go to the office
across the hall from Mary? Or do you want to be told, take the elevator
tot he 4th floor, turn left, and go to the office across the haul from
Mary, she has a big sign on her office.
"Across the haul from Mary" by itself is useless and unactionable. The
directions that start with the elevator in the lobby is actionable. ;-)
--
Grant. . . .
unix || die
