Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jonathan Foulkes <jf@jonathanfoulkes.com>
Cc: bloat@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Bloat] New OpenWrt release fixing several dnsmasq CVEs
Date: Fri, 22 Jan 2021 22:15:34 +0100	[thread overview]
Message-ID: <875z3o65c9.fsf@toke.dk> (raw)
In-Reply-To: <557C22F5-BF2E-478A-8C48-BE52F9C75256@jonathanfoulkes.com>

Jonathan Foulkes <jf@jonathanfoulkes.com> writes:

> I installed the updated package on a 19.07.4 box running cake, and QoS performance went down the tubes.
> Last night it locked up completely while attempting to stream.
>
> See the PingPlots others have posted to this forum thread, mine look similar, went from constant sub 50ms to very spiky, then some loss, loss increasing, and if high traffic, lock-up.
> https://forum.openwrt.org/t/security-advisory-2021-01-19-1-dnsmasq-multiple-vulnerabilities/85903/39
>
> load is low, sirq is low, so box does not seem stressed.
>
> Any reason Cake would be sensitive to a dnsmasq bug?

No, not really. I mean, dnsmasq could be sending some traffic that
interferes with stuff? Or it could be a kernel regression - the release
did bump the kernel version as well...

-Toke

  reply	other threads:[~2021-01-22 21:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 23:20 Toke Høiland-Jørgensen
2021-01-22 19:33 ` [Cerowrt-devel] [Bloat] " Jonathan Foulkes
2021-01-22 21:15   ` Toke Høiland-Jørgensen [this message]
2021-01-22 21:25     ` Jonathan Foulkes
2021-01-22 21:27       ` Daniel Sterling
2021-01-22 21:40         ` Toke Høiland-Jørgensen
2021-01-22 21:40       ` [Cerowrt-devel] " Sebastian Moeller
2021-01-23 16:29         ` Jonathan Foulkes
2021-01-23 16:33           ` Daniel Sterling
2021-01-23 20:04           ` Etienne Champetier

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=875z3o65c9.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jf@jonathanfoulkes.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