--On Wednesday, July 31, 2019 10:37 PM +0200 Sebastian Moeller
<[email protected]> wrote:
Pretty cool! (Caveat: due to lack of a centos system I will not be able
to actually test it)
It should work on any recent Red Hat system, including RHEL, Fedora,
CentOS, and Scientific. It's using the systemd files so it can't start
automatically with the older initscript-based versions. RH doesn't have the
ifup hook for packages so it doesn't include that feature to enable/disable
the SQM on interface up/down.
Note that this is just a packaging wrapper. I didn't change any of the
scripts. This just drops all the files into the correct place and updates
the package database so they can be easily removed or upgraded as
necessary.
To install, just use "yum install sqm-scripts-1.3.0-1kp.noarch.rpm".
Start with "systemctl start sqm@eth0" (substituting your interface name for
eth0). You need to first create /etc/sqm/eth0.iface.conf based on the
provided example.
So maybe run the following to get some debug output:
SQM_DEBUG=1 SQM_VERBOSITY_MAX=10 /etc/init.d/sqm start ; tc -s qdisc ; tc
-d qdisc ; SQM_DEBUG=1 SQM_VERBOSITY_MAX=10 /etc/init.d/sqm stop
I would hope that this should undo its damage at the end but will also
capture the wedged state in between. Then again this still might lead to
an unusable interface....
Thanks, I'll give that a try, probably tomorrow morning before everyone
gets in. I was able to quickly get in to repair the damage and stop the
service ("systemctl stop sqm@em2") by remoting in through a server I have
in parallel and shelling to the router's internal interface (which isn't
being shaped). The slowness didn't happen instantly but after a minute or
more, when I got a call from the office that "the internet is down!". The
external interface wasn't completely dead, just extremely slow, enough to
eventually kill my ssh session. It recovered instantly with the stop
command.
Ken
_______________________________________________
Bloat mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/bloat
