Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
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 14:27:04 +0100	[thread overview]
Message-ID: <5177DDA8.8010801@gmail.com> (raw)
In-Reply-To: <CAA93jw5K3xo1Sp5JGf9pWaFbUOCdO0nwW8KqFG5En=qk28kKxA@mail.gmail.com>

On 20/04/13 10:56, Dave Taht wrote:
> iproute2's ip/iproute2.c code has a function called iproute_modify,
> which to a blurring eye appears to be capable of doing an atomic route
> update via it's netlink interface.
>
> "        if (matches(*argv, "change") == 0 || strcmp(*argv, "chg") == 0)
>                  return iproute_modify(RTM_NEWROUTE, NLM_F_REPLACE,
>                                        argc-1, argv+1);
>          if (matches(*argv, "replace") == 0)
>                  return iproute_modify(RTM_NEWROUTE, NLM_F_CREATE|NLM_F_REPLACE,
>                                        argc-1, argv+1);"
>
> The babel  native daemon and the quagga-re code, however, does a
> delete/add, which results in packets dropping on the floor when a
> route changes.
>

I think quagga-RE would take a lot of work, as you'd need to teach it 
about modifying routes.  The standalone babeld looks promising though, 
and I have a basic patch up on GitHub 
(git://github.com/rb12345/babeld.git).  One issue is that it seems 
difficult to actually flush the IPv6 route cache, at least on Ubuntu, as 
writes to /proc/sys/net/ipv6/route/flush appear to be ignored.  The 
iproute2 approach is to query all cached routes and misuse its internal 
print_route function to remove each route when flushing the IPv6 cache.

At the moment, the code compiles fine, and I am in the process of 
testing it here.

-- 
Robert Bradley


  parent reply	other threads:[~2013-04-24 13:27 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 [this message]
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

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=5177DDA8.8010801@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