netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: lorenzo@google.com
Cc: brian.haley@hp.com, shemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: addrconf: clear IPv6 addresses and routes when losing link
Date: Tue, 26 Oct 2010 10:47:10 -0700 (PDT)	[thread overview]
Message-ID: <20101026.104710.232747902.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTi=P80OUBSy3xCt_qOjPGTwNjrtFL1iLJnkc9joq@mail.gmail.com>

From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 26 Oct 2010 10:37:53 -0700

> So when the link comes back, we'd have to wait for all RAs to come in
> (there could be multiple routers on a link, each announcing different
> prefixes), and when this is all done, compare the list of addresses to
> the prefixes that are currently on the link and delete the ones that
> don't match. We'd have to do the same with default routers and /64
> routes to all the link prefixes.

Why would you do this when there are link layer indications that
we are attached to a different network?

The only thing missing is a new device notification type, some code to
generate it in the wireless subsystem, and an ipv6 handler to zap the
addresses when received.

Please think out of the box for a second, thanks :-)

  reply	other threads:[~2010-10-26 17:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  2:08 [PATCH] ipv6: addrconf: clear IPv6 addresses and routes when losing link Lorenzo Colitti
2010-10-26  4:38 ` Stephen Hemminger
2010-10-26  5:44   ` Lorenzo Colitti
2010-10-26 15:28     ` Stephen Hemminger
2010-10-26 17:11       ` Lorenzo Colitti
2010-11-02  2:54       ` Dan Williams
2010-11-05  6:40         ` Lorenzo Colitti
2010-10-26 16:58     ` Brian Haley
2010-10-26 17:09       ` Lorenzo Colitti
2010-10-26 17:10       ` David Miller
2010-10-26 17:13         ` Lorenzo Colitti
2010-10-26 17:21           ` David Miller
2010-10-26 17:37             ` Lorenzo Colitti
2010-10-26 17:47               ` David Miller [this message]
2010-10-26 17:50                 ` Lorenzo Colitti
2010-10-26 17:55                   ` David Miller
2010-10-26 18:02                     ` Lorenzo Colitti
2010-10-26 18:21                       ` David Miller
2010-11-02  2:50                       ` Dan Williams
2010-10-26 18:17                 ` Lorenzo Colitti
2010-10-26 18:23                   ` David Miller
2010-10-26 22:53                     ` Lorenzo Colitti
2010-10-27 15:51                       ` David Miller
2010-10-27 16:01                         ` Lorenzo Colitti
2010-10-27 16:05                           ` David Miller
2010-10-27  2:31 ` Brian Haley
2010-10-27  8:35   ` Maciej Żenczykowski
2010-10-27 16:03     ` Lorenzo Colitti
2010-10-27 20:39       ` Maciej Żenczykowski
2010-10-28 22:23         ` Lorenzo Colitti
2010-10-28 22:41           ` Lorenzo Colitti
2010-10-28 22:50           ` Maciej Żenczykowski

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=20101026.104710.232747902.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=brian.haley@hp.com \
    --cc=lorenzo@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).