From: Richard <rocon46@hotmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Possible Bug(s) in Cero 3.10.50-1
Date: Sat, 13 Sep 2014 18:06:35 +0000 (UTC) [thread overview]
Message-ID: <loom.20140913T181555-194@post.gmane.org> (raw)
Hi, all. End user here. Just thought I'd post a few possible bugs I've run
into since updating to 3.10.50-1. I'm not exactly sure if these have been
reported or are intentional, but I figured it couldn't hurt to post them anyway.
1) When using PPPoE on the outbound interface, traffic skips classification
MARKS set by iptables in the QOS_MARK_ge00 chain entirely. This is whilst
using simple.qos. Everything is placed in the 1:12 class in HTB in both
ingress and egress regardless of rules set. This was tried using 3.10.34-4
and then a fresh install of 3.10.50-1.
2) In 3.10.50-1, whilst running multiple Intermediate Functional Blocks,
restarting SQM often has a chance to not close IFBs after the first IFB. i.e
Anything after ifb0 has a chance to not close. Cero then creates a new
Block(s) after the ones that haven't closed as it believes they are still in
use. Doing this enough eventually fills up all available Blocks and then
ingress shaping fails to start.
Workaround for me has been to SSH in, stop SQM completely, and then start it
back up again whenever I change settings as that ensures any lingering IFBs
are closed down.
Unfortunately, I foolishly forgot to keep any logs using cerostats.sh and no
longer have a modem to test PPPoE on; the one I had couldn't hold the DSL
line for very long and was subsequently returned. I also ran into something
which I thought was Bug #442 after updating to 3.10.50-1. I had moved from
3.10.34-4 using the sysupgrade image.
The router seemed to lock up twice within the first 15mins after boot and
again after reboot. Only the 2.4Ghz network went nuts while 5Ghz remained
fine. Everything on the 2.4Ghz network was still connected, yet nothing on
2.4 could get through - both to the internet and to the router itself. I
then decided to do a clean install and haven't run into it since. This is
something which has happened to me before on an earlier release and I only
ever seem to run into this bug whenever I use a sysupgrade image, or restore
my settings from an archive.
Something I've noticed is that #442 (or something similar) never seems
happen if I do a clean install and rewrite my settings from scratch...
Just a thought.
I think that's about it.
And if anyone's willing to answer this, I know this isn't exactly the place
ask this, but, aside from having Cero handle external ICMPs requests, is
there any inherent performance/security/bufferbloat benefits from having
Cero handle my external ip over a gateway --> router combo?
Right now, my setup consist of a gateway and I'm unable to put it in bridge
mode. The gateway does NAT, has SPI disabled, and has a static route and DMZ
defined towards Cero. Cero is connected to the end of it with Masquerading
disabled and the firewall still up. Every device we have runs through Cero.
I'd like to know anything at all before I decide to go looking for another
dedicated modem, or if I should even bother to go looking in the first place.
Hope this helps!
—Regards, Richard
next reply other threads:[~2014-09-13 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 18:06 Richard [this message]
2014-09-13 19:27 ` Sebastian Moeller
2014-09-14 7:45 ` Richard
2014-09-14 9:25 ` Sebastian Moeller
2014-09-14 16:56 ` Richard
2014-09-14 10:45 ` Dave Taht
2014-09-14 16:28 ` Sebastian Moeller
2014-09-15 21:56 ` 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=loom.20140913T181555-194@post.gmane.org \
--to=rocon46@hotmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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