General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] RPM for sqm-scripts
Date: Wed, 31 Jul 2019 13:01:30 -0700	[thread overview]
Message-ID: <85DFBE069FB380F4A8B2D9EC@[192.168.1.16]> (raw)
In-Reply-To: <B7537C85-D0FE-4F95-A039-82D9B25DEB03@gmx.de>

--On Wednesday, July 31, 2019 10:37 PM +0200 Sebastian Moeller 
<moeller0@gmx.de> 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



  reply	other threads:[~2019-07-31 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 19:32 Kenneth Porter
2019-07-31 19:37 ` Sebastian Moeller
2019-07-31 20:01   ` Kenneth Porter [this message]
2019-08-08 14:07 ` Toke Høiland-Jørgensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='85DFBE069FB380F4A8B2D9EC@[192.168.1.16]' \
    --to=shiva@sewingwitch.com \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox