From: Robert Bradley <robert.bradley1@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] atomic route updates?
Date: Sun, 05 May 2013 18:01:03 +0100 [thread overview]
Message-ID: <5186904F.60403@gmail.com> (raw)
In-Reply-To: <CAA93jw7XuuJFjPcL00bN39cmhgKo7Qe0nmSLO4pnJt4hXt9sCg@mail.gmail.com>
On 05/05/13 13:02, Dave Taht wrote:
> On Thu, Apr 25, 2013 at 8:05 AM, Robert Bradley
> <robert.bradley1@gmail.com> wrote:
>> I was seeing that bug on the quantal 3.5 kernel as well. So far, testing
>> with the raring 3.8 kernel seems to fix both the unreachable route bug and
>> the random /128 route bugs. My patched babeld also appears to work no worse
>> than the distro-provided 1.3.1 build. That said, with both versions I see
>> that babeld switches to wireless routes and stays there if eth0 is
>> disconnected and later restored.
> Still stuck on this? I'm planning a new build this week with your
> atomic route stuff in it. babel 1.3.6 and 1.40 have been released.
>
The current code is behaving identically to the upstream master branch
to me, so I think this is fine for the new build.
--
Robert Bradley
prev parent reply other threads:[~2013-05-05 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 9:56 Dave Taht
2013-04-24 6:14 ` Maciej Soltysiak
2013-04-24 9:33 ` Dave Taht
2013-04-24 13:27 ` Robert Bradley
2013-04-24 14:03 ` Robert Bradley
2013-04-24 15:46 ` Dave Taht
2013-04-25 15:05 ` Robert Bradley
2013-05-05 12:02 ` Dave Taht
2013-05-05 13:58 ` Daniel Ezell
2013-05-05 18:31 ` Dave Taht
2013-05-05 17:01 ` Robert Bradley [this message]
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=5186904F.60403@gmail.com \
--to=robert.bradley1@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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