From: Brian Haley <brian.haley@hp.com>
To: David Miller <davem@davemloft.net>
Cc: vladislav.yasevich@hp.com, netdev@vger.kernel.org
Subject: Re: Configuring the same IP on multiple addresses
Date: Tue, 30 Oct 2007 00:23:40 -0400 [thread overview]
Message-ID: <4726B1CC.2070203@hp.com> (raw)
In-Reply-To: <20071029.154258.39630263.davem@davemloft.net>
David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Mon, 29 Oct 2007 15:25:59 -0700 (PDT)
>
>> Can you guys please just state upfront what virtualization
>> issue is made more difficult by features you want to remove?
>
> Sorry, I mentioned "virtualization" because that's been the
> largest majority of the cases being presented lately.
>
> I suspect in your case it's some multicast or SCTP thing :-)
It's actually neither in this case :)
We have customers migrating from BSD stacks to Linux. They notice all
the differences in the sockets API, sometimes even find bugs, and we fix
them and send patches upstream. They also do stupid things like
duplicate address configurations on two interfaces in different subnets.
IPv6 was the curious one for us here since it falls into an RFC gray
area - addresses are assigned to interfaces, not hosts (RFC 4291), but
they should be tested for uniqueness before being assigned (RFC 4862).
This address didn't pass the uniqueness test, although it did pass DAD
because the links were different. We couldn't find another OS for a
host or router (including IOS) that allows this, hence the question.
Thanks, and sorry if it's just another waste of your time to explain it.
-Brian
next prev parent reply other threads:[~2007-10-30 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 18:03 Configuring the same IP on multiple addresses Vlad Yasevich
2007-10-29 19:36 ` David Stevens
2007-10-29 19:44 ` Vlad Yasevich
2007-10-29 20:36 ` David Stevens
2007-10-29 22:25 ` David Miller
2007-10-29 22:42 ` David Miller
2007-10-30 4:23 ` Brian Haley [this message]
2007-10-30 13:47 ` Vlad Yasevich
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=4726B1CC.2070203@hp.com \
--to=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.com \
/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.