On 05/16/2018 04:09 AM, Jean-Francois Bogaerts wrote: > Dear Tom, > > I made some extensive tests and have the following results: > > Disabling link with command: /var/lib/shorewall/firewall disable eth2 > while physical link is down makes the internet speed very slow through > firewall > Like if there where timeout hanging before routing packets through the > working interface. > > Restarting shorewall with physical eth2 link down gives normal behavior. > > When checking routing with : shorewall show routing I have a difference > between the two cases: > > Table main: > > 192.168.0.0/24 dev eth2 proto kernel scope link src 192.168.0.51 (with > disable command) > > 192.168.0.0/24 dev eth2 proto kernel scope link src 192.168.0.51 > linkdown (with shorewall restart) > > When restarting shorewall "linkdown" is added > > Might this be the problem ? >
Possibly - but I don't understand how that route is being modified by 'disable'. The generated script should not be touching that route. -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 \_______________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
