public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Tim Hockin <thockin@sun.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: issue: deleting one IP alias deletes all
Date: 25 Oct 2001 22:29:40 +0200	[thread overview]
Message-ID: <k21yjrea4r.fsf@zero.aec.at> (raw)
In-Reply-To: <Pine.LNX.4.31.0110251234430.32029-100000@netmonster.pakint.net> <3BD86FA9.A992FE96@sun.com>
In-Reply-To: Tim Hockin's message of "Thu, 25 Oct 2001 13:01:45 -0700"

In article <3BD86FA9.A992FE96@sun.com>,
Tim Hockin <thockin@sun.com> writes:
> "Matthew G. Marsh" wrote:
>> The original thought refers to the old concept of address "class" where is
>> a "class" (think subnet) went away then there was no need (and indeed
>> incorrect) behaviour to still be able to have addresses on it. Thus when
>> the primary address is deleted you should clear all addresses within that

> I don't really think the original thought matters.  What matters is that
> the behavior is 
> a) non-obvious - you don't expect it

It's bug to bug compatibility with 2.0. If you never rename ip aliases
manually and always create the "main" device first it is actually
not too unobvious.

> b) undetectable - you can't find out which alias is "primary"

The information is actually exported to user space via the ifaddrmsg 
flags in rtnetlink, but not displayed currently by iproute2.

> c) inconsistent - some aliases act differently that other aliases

> All of these violate the principle of least surprise.  Whether it was
> intentional or not, it behaves like a nasty hack, or worse, a bug.  It is
> easily fixed, and should be.

It is an nasty hack, but needed to not void all the documentation and scripts
that rely on the old 2.0 alias behaviour.

If you want to avoid it only use ifconfig add/del or ip addr add/del..
to create aliases; never named ip aliases. They're deprecated, but
unfortunately still quite popular.

-Andi



  parent reply	other threads:[~2001-10-25 20:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24  1:01 issue: deleting one IP alias deletes all Julian Anastasov
2001-10-24  5:28 ` David Ford
2001-10-24  6:18   ` Petr Titera
2001-10-24  6:52     ` David Ford
2001-10-24 12:48     ` Wilson
2001-10-25 16:34     ` Matthew G. Marsh
2001-10-24  8:19   ` Julian Anastasov
2001-10-24 14:02   ` Christopher Friesen
2001-10-24 15:34     ` Tim Hockin
2001-10-24 17:14       ` Christopher Friesen
2001-10-24 20:36     ` David Ford
2001-10-24 20:54       ` Tim Hockin
2001-10-27 17:26         ` kuznet
2001-10-25 17:40       ` Matthew G. Marsh
2001-10-25 20:01         ` Tim Hockin
2001-10-25 19:56           ` David S. Miller
2001-10-25 20:29           ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-23 17:54 Tim Hockin
2001-10-24 11:36 ` Kurt Roeckx
2001-10-24 12:00   ` Kurt Roeckx
2001-10-25 16:30 ` Matthew G. Marsh
2001-10-26 19:51   ` Michal Jaegermann

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=k21yjrea4r.fsf@zero.aec.at \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thockin@sun.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