From: Dave Taht <dave.taht@gmail.com>
To: Neil Shepperd <nshepperd@gmail.com>
Cc: cerowrt@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] [Bug #442] from hell
Date: Sat, 5 Apr 2014 12:06:47 -0700 [thread overview]
Message-ID: <CAA93jw7XGC_-pw=pRR8ezWhkdM0-hVmYAUqA9Kd2GqsuSA=OMw@mail.gmail.com> (raw)
In trying to sort this stuff out (been looking at a ton of commits between
3.10.34 and 3.14) I have a few candidates in various parts of the
stack to try to backport.
3.10.34-3.10.36 does not seem to have any relevant patches, but I just
updated to 3.10.36 anyway.
In openwrt head, there has been a problem in dhcpv6 renews, which you
can see on the dhcpv6 web page after a day or so. That looks to be
fixed now.
So I just merged from openwrt head.
I try to be happy that most of our problems are now taking days to crop up.
I will probably produce a topic branch at this point which will have heavy
levels of debugging enabled. I'd like to be able to trace packets from
origin to (non) exit, somehow...
reply other threads:[~2014-04-05 19:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw7XGC_-pw=pRR8ezWhkdM0-hVmYAUqA9Kd2GqsuSA=OMw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cerowrt@lists.bufferbloat.net \
--cc=nshepperd@gmail.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