From: Simone Piunno <pioppo@ferrara.linux.it>
To: Peter Bieringer <pb@bieringer.de>
Cc: usagi-users@linux-ipv6.org, netdev@oss.sgi.com,
ds6-devel@deepspace6.net, linux-kernel@vger.kernel.org
Subject: Re: [ds6-devel] Re: (usagi-users 02296) IPv6 duplicate address bugfix
Date: Mon, 31 Mar 2003 20:56:48 +0200 [thread overview]
Message-ID: <20030331185648.GA3928@ferrara.linux.it> (raw)
In-Reply-To: <9360000.1049135038@worker.muc.bieringer.de>
On Mon, Mar 31, 2003 at 08:23:58PM +0200, Peter Bieringer wrote:
> 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.
I'd prefer this variant:
manual add is allowed and overwrites the autoconfigured address.
--
Simone Piunno -- http://members.ferrara.linux.it/pioppo
.------- Adde parvum parvo magnus acervus erit -------.
Ferrara Linux Users Group - http://www.ferrara.linux.it
Deep Space 6, IPv6 on Linux - http://www.deepspace6.net
GNU Mailman, Mailing List Manager - http://www.list.org
`-------------------------------------------------------'
prev parent reply other threads:[~2003-03-31 18:56 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 ` (usagi-users 02296) IPv6 duplicate address bugfix Peter Bieringer
2003-03-31 18:56 ` Simone Piunno [this message]
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=20030331185648.GA3928@ferrara.linux.it \
--to=pioppo@ferrara.linux.it \
--cc=ds6-devel@deepspace6.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pb@bieringer.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.