From: Peter Bieringer <pb@bieringer.de>
To: usagi-users@linux-ipv6.org, netdev@oss.sgi.com
Cc: linux-kernel@vger.kernel.org, ds6-devel@deepspace6.net
Subject: Re: (usagi-users 02296) IPv6 duplicate address bugfix
Date: Mon, 31 Mar 2003 20:23:58 +0200 [thread overview]
Message-ID: <9360000.1049135038@worker.muc.bieringer.de> (raw)
In-Reply-To: <20030330122705.GA18283@ferrara.linux.it>
Hi,
just my 2 cents, I already saw, that newest USAGI snapshot include a fix.
--On Sunday, March 30, 2003 02:27:05 PM +0200 Simone Piunno
<pioppo@ferrara.linux.it> wrote:
> When adding an IPv6 address to a given interface, I'm allowed to
> add that address multiple time, e.g.:
...
I didn't dig into any patch and also not into related drafts/RFCs, but one
scenario should be catched I think - or to be discussed:
Scenario:
Address was already added by autoconfiguration on receiving advertisement
(limited lifetime). Now the same address would be added manually (unlimited
lifetime).
What (should) happen?
Mho: manual add is allowed, both addresses need to be listed.
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
next prev parent reply other threads:[~2003-03-31 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 12:27 IPv6 duplicate address bugfix Simone Piunno
2003-03-30 13:08 ` (usagi-users 02296) " YOSHIFUJI Hideaki / 吉藤英明
2003-03-30 14:58 ` [PATCH] IPv6: Don't assign a same IPv6 address on a same interface (is Re: IPv6 duplicate address bugfix) YOSHIFUJI Hideaki / 吉藤英明
2003-03-30 16:36 ` Simone Piunno
2003-03-30 18:35 ` YOSHIFUJI Hideaki / 吉藤英明
2003-03-31 1:34 ` [PATCH] IPv6: Don't assign a same IPv6 address on a same interface YOSHIFUJI Hideaki / 吉藤英明
2003-03-31 19:05 ` David S. Miller
2003-03-31 18:23 ` Peter Bieringer [this message]
2003-03-31 18:56 ` [ds6-devel] Re: (usagi-users 02296) IPv6 duplicate address bugfix Simone Piunno
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=9360000.1049135038@worker.muc.bieringer.de \
--to=pb@bieringer.de \
--cc=ds6-devel@deepspace6.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=usagi-users@linux-ipv6.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).