From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Alan Jenkins <alan.christopher.jenkins@gmail.com>,
openwrt-devel@lists.openwrt.org, luis@bitamins.net,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [sqm-scripts] not started at boot?
Date: Sun, 15 Feb 2015 17:18:34 +0100 [thread overview]
Message-ID: <87lhjz1739.fsf@toke.dk> (raw)
In-Reply-To: <9EB28655-6E25-470B-A13B-036EE00D84D7@gmx.de> (Sebastian Moeller's message of "Sun, 15 Feb 2015 17:12:41 +0100")
Sebastian Moeller <moeller0@gmx.de> writes:
> Not that I have shown great taste in the past, but I think it
> would be somewhat cleaner to put the logic into the hot plug script
> and keep run.sh “simple” (in the past I had introduced a large number
> of leakage, especially of IFBs by not properly removing/stopping old
> instances and was quite happy to have the take all active interfaces
> down loop as a last defense against accidental leaks).
Well, the biggest issue I can see with not having any logic in run.sh is
that in that case, *all* interfaces will be reconfigured when the
hotplug event happens. However, I'm not sure exactly how common it is to
have more than one interface configured for SQM, and if so, whether or
not reconfiguring everything on every hotplug event (well, only for for
SQM-enabled interfaces I suppose) is an issue.
The modifications to run.sh should keep it functioning the way it does
currently if run 'manually' the shell or LUCI. Unless the $DEVICE
env-var is set for some other reason...
> But I am now also running pppoe directly from cerowrt and see
> the same issue, sqm is confused when the pppoe interface
> temporarily goes away, so at least I can now test this issue ;)
Well, a first pass could be to see if the modified run.sh I sent last
time around actually works... ;)
-Toke
next prev parent reply other threads:[~2015-02-15 16:18 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 [this message]
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
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=87lhjz1739.fsf@toke.dk \
--to=toke@toke.dk \
--cc=alan.christopher.jenkins@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=luis@bitamins.net \
--cc=moeller0@gmx.de \
--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