[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKD1Yr37t2RJm-fmz=mVYcYWerM5Bu1O1cJMLEqSh=ogvxMrGg@mail.gmail.com>
Date: Mon, 18 Mar 2013 11:39:02 -0700
From: Lorenzo Colitti <lorenzo@...gle.com>
To: Lorenzo Colitti <lorenzo@...gle.com>,
Dan Williams <dcbw@...hat.com>,
Sylvain Munaut <s.munaut@...tever-company.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Who/What is supposed to remove IPv6 address from interface when
moving from one network to another ?
On Mon, Mar 18, 2013 at 11:34 AM, Hannes Frederic Sowa
<hannes@...essinduktion.org> wrote:
>> Actually, it *does* trigger events on carrier change: it creates the
>> addresses when you connect. It just doesn't delete them when you
>> disconnect. So you can get addresses without a userspace daemon, but
>> you can never delete them without a userspace daemon.
>
> Not directly related, but I wonder if we should treat the change of the
> mac address as a carrier change in ipv6 to create a new ll address. I
> did not find any satisfying answer yet.
Yes, we should - because if we're attaching to a new link, there might
be someone with a duplicate IPv6 address on it, so we'd need to
perform DAD.
I think the kernel does do this though. So in effect, every new link
you attach to gives you new IPv6 addresses, and never deletes them.
The old ones usually don't work on the new link, so you end up with
broken connectivity. Current solutions are either disable IPv6 or
start a userspace daemon to clean up the non-working addresses.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists