Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] SQM restart and problems on boot fixed
Date: Sun, 19 Jan 2014 19:21:02 +0100	[thread overview]
Message-ID: <CD40B591-6B95-4069-B718-218393E3A8D5@gmx.de> (raw)
In-Reply-To: <CAA93jw7ysaEHZVTxyfhWHbuwmzjhfSa1PeNBRhG47t36hbex8A@mail.gmail.com>

Hi Dave,


On Jan 19, 2014, at 17:36 , Dave Taht <dave.taht@gmail.com> wrote:

> The /etc/hotplug.d/iface/00-debloat script has been wrong in the face
> of the qos-scripts, aqm-scripts, and stuff inbetween.
> 
> Thus on a fresh boot, or after a DHCP renew
> or a variety of other circumstances, the portion of sqm that sets up
> the egress portion of itself gets wiped out.
> 
> this explains a lot of network performance issues that others have had
> after a cero box had been up for a while... the sqm code was getting
> partially disabled!
> 
> This was also probably wrong on a ton of previous releases going back
> to 3.7.5 or earlier. (however since the name has changed, it would be
> aqm for stuff prior to the great renaming, and for 3.7.5 the solution
> is also different because we
> weren't using uci at the time.
> 
> but for 3.10.24 and later replace /etc/hotplug.d/iface/00-debloat with this.
> 
> #!/bin/sh
> 
> #DEBLOAT_LOG=/tmp/debloat.log
> #DEBLOAT_LOG2=/tmp/debloat2.log
> DEBLOAT_LOG=/dev/null
> DEBLOAT_LOG2=/dev/null
> 
> SQM=0
> SQM=`uci get sqm.${DEVICE}.enabled`
> 
> [ "$ACTION" = "ifup" -a "$SQM" != "1" ] && {
>        IFACE=$DEVICE QMODEL=fq_codel_ll /usr/sbin/debloat >>
> $DEBLOAT_LOG 2>> $DEBLOAT_LOG2
> }

	Excellent find, must have been tricky to catch with it only triggering ever so often. I assume that this triggering will also have removed the HTB from egress, so that "tc -d qdisc" always reported the actual running setup?

best
	Sebastian


> 
> 
> -- 
> Dave Täht
> 
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


      reply	other threads:[~2014-01-19 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 16:36 Dave Taht
2014-01-19 18:21 ` Sebastian Moeller [this message]

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CD40B591-6B95-4069-B718-218393E3A8D5@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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