-----Original Message-----
From: Tom Eastep
Sent: Monday, May 6, 2019 12:31 AM
To: shorewall-users@lists.sourceforge.net
Subject: Re: [Shorewall-users] Switching between multi-ISP
On 5/5/19 2:27 PM, Andrey Andreev wrote:
>> Then don't specify GW in the network config, and define it in
>> /etc/shorewall/providers instead.
> ISP #2 with static IP has already its GW listed in /etc/shorewall/providers:
>
> #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS
> COPY
> N3 1 1 - enp3s0
> GW1 track,primary -
> A1 2 2 - enp1s0
> 192.168.42.1 track -
Then simply take it out of the systemd network config for that interface.
-Tom
--
Tom Eastep \ Q: What do you get when you cross a mobster with
Shoreline, \ an international standard?
Washington, USA \ A: Someone who makes you an offer you can't
http://shorewall.org \ understand
\_______________________________________________
Tomorrow will go to the site and test it.
Under NM control of the network, omitting GW lead to no internet connectivity
through ISP A1 when ISP N3 is down. In table 254 there was:
192.168.42.0/24 dev enp1s0 proto kernel scope link src 192.168.42.253
metric 100
192.168.42.1 dev enp1s0 scope link src 192.168.42.253
Shorewall restart did not help if GW is not listed in the ifcfg-enp1s0 file.
With GW present, a restart added:
default via 192.168.42.1 dev enp1s0 proto static metric 100
and net was restored.
Hope with networkd things are different.
Andrei
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
