From: Harald Welte <laforge@gnumonks.org>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Neil Horman <nhorman@redhat.com>,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: primary and secondary ip addresses
Date: Thu, 16 Dec 2004 10:28:32 +0100 [thread overview]
Message-ID: <20041216092831.GO2862@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0411100034320.10593@filer.marasystems.com>
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
[Cc'ing netdev, since nobody replied since november]
On Wed, Nov 10, 2004 at 12:38:19AM +0100, Henrik Nordstrom wrote:
> On Tue, 9 Nov 2004, Neil Horman wrote:
>
> >Can anyone tell me why when removing a primary ip address from an
> >interface, all of its associated secondary ip addresses (those addresses
> >on the same subnet), are also removed? Theres a comment in the kernel
> >thats pretty clear on the subject indicating it needs to be done, but I
> >don't quite grasp the reasoning behind why.
>
> A more valid question is why one can not add more than one primary in the
> same subnet.
>
> ip addr add x.x.x.x/y dev eth0 primary
>
> would make sense to me, clearly indicating that these addresses are
> maintained separately.
agreed.
> or put in another way why the addresses automatically become secondary
> addresses to the first added address.
... and why does removing the primary address remove all secondary
addresses. This makes it complicated if you have one interface with
multiple ip addresse, that change over time (failover, let's say.) You
don't know yet, which address you need to remove, because you don't know
which of your peers fails.
So you have all this complicated userspace magic that checks whether the
address that is about to be deleted is the primary, and if yes, re-add
all the other addresses. If if is a secondary, you're happy and only
need to delete that one.
Can anyone comment what the idea of all this was?
Thanks.
--
- Harald Welte <laforge@gnumonks.org> http://www.gnumonks.org/
============================================================================
Programming is like sex: One mistake and you have to support it your lifetime
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2004-12-16 9:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41912F7A.6000408@redhat.com>
[not found] ` <Pine.LNX.4.61.0411100034320.10593@filer.marasystems.com>
2004-12-16 9:28 ` Harald Welte [this message]
2004-12-16 9:53 ` primary and secondary ip addresses Hasso Tepper
2004-12-16 10:07 ` Henrik Nordstrom
2004-12-16 11:02 ` Hasso Tepper
2004-12-16 16:02 ` Henrik Nordstrom
2004-12-17 15:10 ` Andrea G Forte
2004-12-17 15:27 ` Henrik Nordstrom
2004-12-17 15:58 ` Andrea G Forte
2004-12-17 16:39 ` Henrik Nordstrom
2004-12-17 17:17 ` Andrea G Forte
2004-12-17 19:17 ` Henrik Nordstrom
2004-12-17 18:03 ` Hasso Tepper
2004-12-17 18:37 ` Martin A. Brown
2004-12-17 18:53 ` Hasso Tepper
2004-12-17 19:25 ` Henrik Nordstrom
2004-12-17 20:55 ` Hasso Tepper
2004-12-17 20:54 ` Andrea G Forte
2004-12-17 19:20 ` David S. Miller
2004-12-17 19:48 ` Henrik Nordstrom
2004-12-19 20:18 ` jamal
2004-12-19 21:41 ` Harald Welte
2004-12-19 22:02 ` Thomas Graf
2004-12-19 22:59 ` jamal
2004-12-19 23:56 ` jamal
2004-12-20 13:55 ` jamal
2004-12-20 14:29 ` Harald Welte
2005-04-12 10:54 ` Harald Welte
2005-05-08 12:31 ` Hasso Tepper
2005-05-26 18:11 ` Harald Welte
2005-05-26 18:21 ` Thomas Graf
2005-05-26 21:58 ` David S. Miller
2004-12-16 16:48 ` Paul Jakma
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=20041216092831.GO2862@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=hno@marasystems.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=nhorman@redhat.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 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).