From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9C5623B2A4 for ; Wed, 31 Jul 2019 16:01:52 -0400 (EDT) Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id suHhhFdekfwuCsunHhK2uT; Wed, 31 Jul 2019 20:01:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1564603311; bh=CoUT5wb581+VYmO+5Tv5mS95PunVPa5P1Zt2DCopfHQ=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=YbOSBKpVUNW8koO76LJibThvAoI/KgRwySO49Kmta4b8qsqpvVhd5Y2BstBts009G 7ERoPxgXZAJdWK3NHtl7VMYk9ntBqu0xEY6r6YYzZBlMYhVYoB4efTp4P8fcBde5Q/ QWNf/0nIs5GwWgiHdvTDP5azq7rkWbEOhgU63a8SsTmcdJlTfDU2Pt26YgrtZuYMvU 5HKFRo3WSIKzRECiG9nwiifXMpaqV0qCBfRHf1Xctsn6nQJPDSquoq6DIKvQrXDLcg IXSMivBAfHED9Jg0ZWDVxWkXoSUU4fXtgzcxfT37/mt0ofsi9GIIDgncWwVZ3iCXpN sZwXvIZ7P07WQ== Received: from home.sewingwitch.com ([IPv6:2601:644:0:c177::ae3]) by resomta-ch2-07v.sys.comcast.net with ESMTPA id sumzhUrLxBmBKsunHhvu4M; Wed, 31 Jul 2019 20:01:51 +0000 X-Xfinity-VMeta: sc=0;st=legit Received: from Z220 ([10.96.7.39]) (authenticated bits=0) by home.sewingwitch.com (8.14.7/8.14.7) with ESMTP id x6VK1VJk017207 for ; Wed, 31 Jul 2019 13:01:31 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 home.sewingwitch.com x6VK1VJk017207 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sewingwitch.com; s=default; t=1564603292; bh=CoUT5wb581+VYmO+5Tv5mS95PunVPa5P1Zt2DCopfHQ=; h=Date:From:To:Subject:In-Reply-To:References:From; b=tO68EVDDb6xSsq9H6rZ4z0rwEo4uxx5Vl8A1z2cVq5t5piWf9JqfTJS0oEuFO1jWG pYzTAScQ9VEqkDr038OV1EYlqOJnBRu/5BDDt0i2nOvfukaKd+aEIaVsSW0RSNuHWg YObG/ykgxBaShO+5S+FGKchNaDilWhQ1lzpBTwYg= Date: Wed, 31 Jul 2019 13:01:30 -0700 From: Kenneth Porter To: bloat@lists.bufferbloat.net Message-ID: <85DFBE069FB380F4A8B2D9EC@[192.168.1.16]> In-Reply-To: References: <92FC145B7421C60FA15458F4@[192.168.1.16]> X-Mailer: Mulberry/4.1.0a3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=2007 X-Antivirus: Avast (VPS 190703-0, 07/02/2019), Outbound message X-Antivirus-Status: Clean X-Scanned-By: MIMEDefang 2.84 on 10.96.0.132 Subject: Re: [Bloat] RPM for sqm-scripts X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2019 20:01:52 -0000 --On Wednesday, July 31, 2019 10:37 PM +0200 Sebastian Moeller 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