27 May
2019
27 May
'19
8:41 a.m.
On 5/26/19 10:59 PM, Jack Craig wrote:
On Sun, May 26, 2019 at 10:52 PM Ed Greshko <ed.greshko@greshko.com mailto:ed.greshko@greshko.com> wrote:
On 5/27/19 1:38 PM, Jack Craig wrote: > > > On Sun, May 26, 2019 at 10:17 PM Ed Greshko <ed.greshko@greshko.com <mailto:ed.greshko@greshko.com> > <mailto:ed.greshko@greshko.com <mailto:ed.greshko@greshko.com>>> wrote: > > On 5/27/19 12:17 PM, Jack Craig wrote: > > i thought what i read was after nm brings up the vpn, only then is the default > route to > > vpn created. more, its torn down first on shutdown. > > > > i'm thinking along this line, ... > > > > https: <https://www.debuntu.org/how-to-network-manager-openvpn-overwrites-default-route/>xpect what should happen is that after each interface comes up via NM a default route > is set to it > so eth0 up, default route to , say, 10.0.0./24 <http://10.0.0./24> <http://10.0.0./24>, then vpn comes and > default route is now pointed at the vpn. > > and this process in reverse on shutdown...
What I've seen is two additional, more specific, default routes added: 0.0.0.0/1 and 128.0.0.0/1, which cover the entire ipv4 address space. By doing it this way the new routes can be deleted and the original default route remains. This works because a more specific route trumps the less specific route (0.0.0.0).
Unfortunately, I can't remember who adds/removes those routes but I suspect it is NM.
Good travels on your adventure, :m