[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1421145346.13626.12.camel@redhat.com>
Date: Tue, 13 Jan 2015 11:35:46 +0100
From: Hannes Frederic Sowa <hannes@...hat.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: David Ahern <dsahern@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: why are IPv6 addresses removed on link down
On Mo, 2015-01-12 at 23:10 -0800, Stephen Hemminger wrote:
> On Mon, 12 Jan 2015 22:06:44 -0700
> David Ahern <dsahern@...il.com> wrote:
>
> > We noticed that IPv6 addresses are removed on a link down. e.g.,
> > ip link set dev eth1
> >
> >
> > Looking at the code it appears to be this code path in addrconf.c:
> >
> > case NETDEV_DOWN:
> > case NETDEV_UNREGISTER:
> > /*
> > * Remove all addresses from this interface.
> > */
> > addrconf_ifdown(dev, event != NETDEV_DOWN);
> > break;
> >
> > IPv4 addresses are NOT removed on a link down. Is there a particular
> > reason IPv6 addresses are?
> >
> > Thanks,
> > David
>
> See RFC's which describes how IPv6 does Duplicate Address Detection.
> Address is not valid when link is down, since DAD is not possible.
It should be no problem if the kernel would reacquire them on ifup and
do proper DAD. We simply must not use them while the interface is dead
(also making sure they don't get used for loopback routing).
The problem the IPv6 addresses get removed is much more a historical
artifact nowadays, I think. It is part of user space API and scripts
deal with that already.
Bye,
Hannes
--
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