From: Sebastian Moeller <moeller0@gmx.de>
To: Richard O <rocon46@hotmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Cero 3.10.24-5 no longer supports multiple AQMs?
Date: Sun, 22 Dec 2013 20:22:12 +0100 [thread overview]
Message-ID: <56938ED3-0D0A-4269-BCC4-6C8D5BB3BAE8@gmx.de> (raw)
In-Reply-To: <loom.20131222T093307-169@post.gmane.org>
Hi Richard,
On Dec 22, 2013, at 09:38 , Richard O <rocon46@hotmail.com> wrote:
> Heya,
>
> I'll try to keep this short, but I'm simply just an end-user of Cero who has
> using it for a few months now. It's been great! So great that I've been
> using it as my main router after the first few weeks.
>
> Anyway, I've just recently upgraded from 3.10.11-2 to the latest build
> (3.10.42-5), and I noticed that you can only set one AQM at any given time.
> Restoring my old settings restores my old set of AQMs - all of which startup
> nicely - but only two out four have their "ingress" start up: ifb0 and ifb1
> while ifb2 and ifb3 remain down. Their entries still appear in the firewall
> and I'm unable to bring them up using ifconfig.
>
If I recall correctly, we just disabled the ability to setup AQM on multiple interfaces, as to our knowledge it was not clear whether it would work at all and whether someone had actually tested it. It should be relatively easy to reenable it, if it works. Question, since most people are happy with just running AQM on the wan link, why do you run it on 4 interfaces?
Best Regards
Sebastian
> As you can probably tell, I don't know very much Linux and simply use
> rc.local to modify the classes and qdiscs for each interface to suit my needs.
>
> I'm just curious if this is going to be a permanent thing or not. Other then
> that, keep up the great work guys. Cero's been good to me, and I'll probably
> just revert to the old build if newer builds are going to be running with a
> single aqm. I never really did encountered any problems with it.
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2013-12-22 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 8:38 Richard O
2013-12-22 19:22 ` Sebastian Moeller [this message]
2013-12-22 20:40 ` Dave Taht
2013-12-23 13:33 ` Richard O
2013-12-23 19:00 ` Dave Taht
2013-12-24 15:26 ` Richard O
2013-12-24 18:46 ` Dave Taht
2013-12-25 15:33 ` Richard O
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=56938ED3-0D0A-4269-BCC4-6C8D5BB3BAE8@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=rocon46@hotmail.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