From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Stale IPv6 address accumulation on linux 3.2.17
Date: Tue, 22 Oct 2013 12:18:11 +0200 [thread overview]
Message-ID: <20131022101811.GA3200@order.stressinduktion.org> (raw)
In-Reply-To: <2134F8430051B64F815C691A62D9831813520C@XCH-BLV-504.nw.nos.boeing.com>
Hi Fred!
On Mon, Oct 21, 2013 at 03:50:24PM +0000, Templin, Fred L wrote:
> On linux 3.2.17, I have a host that configures IPv6 addresses on
> an eth0 interface based on Router Advertisements received from an
> on-link linux box configured as an IPv6 router and running radvd.
> When the host gets an RA, it configures both an EUI-64-based IPv6
> address and an IPv6 privacy address, so it has two IPv6 addresses.
> But, if I leave the host up for long periods of time, it seems to
> accumulate additional IPv6 addresses - perhaps these are stale
> IPv6 privacy addresses?
>
> Is this known behavior, and if so is there a way to turn it off?
> Or, perhaps this was a known bug that has been corrected in more
> recent linux kernel versions?
Could you send me the output of ip -6 a l?
Greetings,
Hannes
next prev parent reply other threads:[~2013-10-22 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.1303241153000.20041@envy.nxs.se>
2013-03-26 16:26 ` unmanaged L2TPv3 ethernet pseudowire Cisco <=> Linux James Chapman
2013-03-27 20:08 ` Tomas Agartz
2013-03-27 20:56 ` James Chapman
2013-10-21 15:08 ` Pierre Desvaux
2013-10-21 15:50 ` Stale IPv6 address accumulation on linux 3.2.17 Templin, Fred L
2013-10-22 10:18 ` Hannes Frederic Sowa [this message]
2014-04-29 17:49 ` unmanaged L2TPv3 ethernet pseudowire Cisco <=> Linux Esteban Lopez
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=20131022101811.GA3200@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=Fred.L.Templin@boeing.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).