Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Alan Jenkins <alan.christopher.jenkins@gmail.com>
Cc: luis@bitamins.net, openwrt-devel@lists.openwrt.org,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [sqm-scripts] not started at boot?
Date: Sun, 15 Feb 2015 17:16:28 +0100	[thread overview]
Message-ID: <50D74441-06F7-4C4D-A59F-C205979C2253@gmx.de> (raw)
In-Reply-To: <54E0AFB2.5040806@gmail.com>

Hi Alan,

On Feb 15, 2015, at 15:39 , Alan Jenkins <alan.christopher.jenkins@gmail.com> wrote:

> Hi Toke
> 
> I tried installing sqm-scripts from trunk, on Barrier Breaker on my wndr3800.
> 
> It's very effective, but I notice SQM isn't applied at boot time. The system log complains about pppoe-wan interface not existing, when the sqm init script is started.
> 
> My guess is it'd be the same even if my WNDR was running the base system from trunk.  Because the sqm scripts don't have nice integration like the qos scripts package.
> 
> Is that useful enough as a bug report?  Do you need me to work on a proper patch?
> 
> qos-scripts has a hotplug script, so I copied it for sqm and the problem is "fixed".  Though my stupid script re-runs the sqm as every single network interface comes up, so it spams the log and probably slows things down a bit.  

	I will see how it looks if the hot plug script decides more intelligently whether to call sqm or not, but I will need a few days due to unrelated deadlines...

> (Maybe sqm script also wants to not be so noisy in the log)

	As far as I am concerned SQM is still on probation (in the openwrt repository) and has not seen sufficient testing, so the output is verbose to facilitate debugging of remote issues. I might be wrong though and all is well, and it can be toned down a lot...

> 
> cat <<EOF > /etc/hotplug.d/iface/10-sqm
> #!/bin/sh
> 
> # my sqm isn't being enabled on boot
> # cargo-cult this hotplug script from qos-scripts
> 
> [ "$ACTION" = ifup ] && /etc/init.d/sqm enabled && /usr/lib/sqm/run.sh
> EOF

	I will, if you do not mind take this as starting point for a slightly more selective hot plug script…

Best Regards
	Sebastian

> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


      parent reply	other threads:[~2015-02-15 16:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 14:39 Alan Jenkins
2015-02-15 15:00 ` Toke Høiland-Jørgensen
2015-02-15 15:48   ` Sebastian Moeller
2015-02-15 15:56     ` Toke Høiland-Jørgensen
2015-02-15 16:12       ` Sebastian Moeller
2015-02-15 16:18         ` Toke Høiland-Jørgensen
2015-02-16 23:23           ` Sebastian Moeller
2015-02-15 16:33       ` Alan Jenkins
2015-02-16  9:05         ` Sebastian Moeller
2015-03-03 17:06         ` Sebastian Moeller
2015-03-03 21:23           ` Alan Jenkins
2015-03-03 21:27             ` Toke Høiland-Jørgensen
2015-03-03 21:35             ` Sebastian Moeller
2015-03-03 22:39               ` Alan Jenkins
2015-03-03 22:46                 ` Sebastian Moeller
2015-02-15 16:16 ` 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=50D74441-06F7-4C4D-A59F-C205979C2253@gmx.de \
    --to=moeller0@gmx.de \
    --cc=alan.christopher.jenkins@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=luis@bitamins.net \
    --cc=openwrt-devel@lists.openwrt.org \
    /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