From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: notifications of interfaces going down/up/being created/destroyed?
Date: Mon, 30 Mar 2015 13:59:34 -0700 [thread overview]
Message-ID: <20150330205934.GA29542@f1.synalogic.ca> (raw)
In-Reply-To: <CAA93jw7u=aPjXVME5WwCa97tbD1-5XpgRPg_C9y2kH9qkrt1mw@mail.gmail.com>
On 2015/03/28 09:37, Dave Taht wrote:
> is there an asynchronous way to register for a notification of an
> interface going down/up?
Look at what `ip monitor` is doing.
>
> ---------- Forwarded message ----------
> From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
> Date: Sat, Mar 28, 2015 at 9:30 AM
> Subject: Re: [Babel-users] Looping in EAGAIN
> To: Dave Taht <dave.taht@gmail.com>
> Cc: Simon Kelley <simon@thekelleys.org.uk>,
> "babel-users@lists.alioth.debian.org"
> <babel-users@lists.alioth.debian.org>
>
>
> > Say wlan0 vanishes. All the routes going out that interface are no
> > longer valid, but from what I understood of this patch, it will loop for
> > a while, then give up.
>
> If wlan0 vanishes, this will be recognised the next time check_interfaces
> is run, and all neighbours visible through wlan0 will be flushed.
>
> The issue we're having is a race condition -- if wlan0 goes down and then
> back up before we run check_interfaces, and the IP addresses don't change,
> then check_interfaces will not notice the transition, and Babel will think
> that its routes through wlan0 are still up -- end you end up with a FIB
> that is not a subset of the RIB. Ouch.
>
> So it might be a good idea to run check_interfaces early when we get
> EAGAIN, but I'm not sure what consequences it might have -- EAGAIN can
> also happen when we're under load, and we'd rather not be repeatedly
> scanning our interfaces in that case.
>
> It would be better to get async notifications from the kernel about
> interfaces going down.
>
> > Not clear to me if this would happen for 4 hello intervals before the
> > interface is recognised as gone?
>
> No, the hellos are used to notice vanishing neighbours, not vanishing
> interfaces. That's a completely different mechanism.
>
> -- Juliusz
>
>
> --
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
>
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-30 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 16:37 notifications of interfaces going down/up/being created/destroyed? Dave Taht
2015-03-30 20:59 ` Benjamin Poirier [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150330205934.GA29542@f1.synalogic.ca \
--to=benjamin.poirier@gmail.com \
--cc=dave.taht@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).