From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] atomic route updates?
Date: Wed, 24 Apr 2013 15:03:39 +0100 [thread overview]
Message-ID: <5177E63B.4060700@gmail.com> (raw)
In-Reply-To: <5177DDA8.8010801@gmail.com>
On 24/04/13 14:27, Robert Bradley wrote:
> At the moment, the code compiles fine, and I am in the process of
> testing it here.
>
For the moment, it seems to work on the Ubuntu 3.5 kernel fine, but
still generates stuck unreachable routes as mentioned in the babeld
1.3.4 changelog. It may still be worth trying this fork on 3.8+ kernels
though to see if anything changes.
--
Robert Bradley
next prev parent reply other threads:[~2013-04-24 14:03 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 [this message]
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
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=5177E63B.4060700@gmail.com \
--to=robert.bradley1@gmail.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