On Friday, October 5, 2018, 6:51:04 PM GMT+2, Tom Eastep <teas...@shorewall.net> wrote:
>> >> Finally, a shorewall restart (full stop and start) actually DID solve the >> issue. I magically got my ppp3 link working again. >> So, of course, I'm worried that if there's a power outage or if someone >> reboots the modems then the gateway might get cut off from the Internet if >> shorewall doesn't restart. > > I can't comment without seeing the difference between the ruleset after '> reenable' and the ruleset after 'restart'. Here's the dump after "reenable ppp3" (no traffic through provider): https://drive.google.com/open?id=13MOhqHX7Im6uu8khr5DQTNuMypxQG8U3 And here's the dump after "restart" (traffic OK through provider): https://drive.google.com/open?id=1GKOjtcEzc8H7JLI1V7hgPwMe3n6ECiXg >>> 10003: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc tbf state >>> UP group default qlen >> 3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state >> UP group default qlen 1000 >> I still don't know why some interfaces are set to use pfifo_fast, or if it's >> recommended or not for a gateway/router. > > Which has nothing to do with Shorewall... OK, I was just asking because the tbf qdisc is set by Shorewall when enabling traffic shaping. Also , /usr/share/shorewall/Shorewall/Tc.pm seems to deal with fq_codel, and there's documentation referencing fq_codel here: http://shorewall.net/manpages4/manpages/shorewall-tcclasses.html http://shorewall.org/traffic_shaping.htm Anyway, I'll study that later on if time permits. Thanks, Vieri _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
