mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: pekkas@netcore.FI (Pekka Savola)
Cc: linux-kernel@vger.kernel.org
Subject: Re: IPv6: the same address can be added multiple times
Date: Sun, 13 May 2001 21:59:07 +0400 (MSK DST)	[thread overview]
Message-ID: <200105131759.VAA27768@ms2.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.33.0105031202080.13012-100000@netcore.fi> from "Pekka Savola" at May 3, 1 01:15:01 pm

Hello!

> It appears you can add _exactly_ same IPv6 address on an interface many
> times:

Yes. BTW, look here:

kuznet@dust:~ # ip -6 a ls sit0
7: sit0@NONE: <NOARP,UP> mtu 1480 qdisc noqueue
    inet6 ::127.0.0.1/96 scope host
    inet6 ::193.233.7.100/96 scope global
    inet6 ::193.233.7.100/96 scope global

I have two equal addresses inherited from one IPv4 address
on two interfaces. Nothing illegal.



> FWIW, KAME stack adds the address only once(, but BSD ifconfig(8)
> doesn't show errors when you try to do it again; just doesn't add the
> second one).

8)

> It looks like a check or two in kernel is missing, or is there some
> reasoning to this behaviour?

Well, it is one of well defined approaches (unlike KAME's one).
Alternative is to implement full set of options NLM_F_* like used
in IPv4 routing to block undefined cases. In IPv6 flags are hardwired
to NLM_F_CREATE|NLM_F_APPEND both for addresses and routes.

Alexey

       reply	other threads:[~2001-05-13 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0105031202080.13012-100000@netcore.fi>
2001-05-13 17:59 ` kuznet [this message]
2001-05-13 20:26   ` Pekka Savola
2001-05-14 10:48     ` David Woodhouse
2001-05-14 18:21     ` kuznet
2001-05-18 14:00       ` Pekka Savola
2001-05-14  2:47   ` David S. Miller
2001-05-14  7:42   ` Kai Henningsen

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=200105131759.VAA27768@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pekkas@netcore.FI \
    /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

all inboxes | Powered by JetHome®