public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@blue-labs.org>
To: Julian Anastasov <ja@ssi.bg>
Cc: Tim Hockin <thockin@sun.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: issue: deleting one IP alias deletes all
Date: Wed, 24 Oct 2001 01:28:40 -0400	[thread overview]
Message-ID: <3BD65188.1060203@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0110240042570.1210-100000@u.domain.uli>

Actually it is quite sane.  The tool is not.

Switch to 'ip' instead of 'ifconfig', several large distros now include 
it.  Addresses can be added and removed completely indiscriminately on 
interfaces.

The "ethN:X" is a legacy design that is now deprecated.

David

Julian Anastasov wrote:

>	Hello,
>
>Tim Hockin wrote:
>
>>If you have several IP aliases on an interface (eth0:0, eth0:1, eth0:2) you
>>get inconsistent behavior when downing them.
>>
>>* if I 'ifconfig down' eth0:1, I am left with eth0:0 and eth0:2
>>* if I 'ifconfig down' eth0:0, eth0:1 and eth0:2 go away, too
>>
>>I assert that this should not happen.  I have a simple patch to fix this
>>behavior, but I want to know a few things.
>>
>>* Is this supposed to happen? Why?
>>* Is it correct that both the real interface and the first alias are marked
>>as primary (! IFA_F_SECONDARY), while all other aliases are secondary?  It
>>
>
>	If you look again into the sources you can see that
>secondary addresses are those that are attached when there is
>already IP address from the same subnet. The aliases don't play
>here nor their number. The analyze points that the semantic
>covers the selection of source addresses (probably when you don't
>use preferred source address in your routes) and in some way they
>look as an IP address lookup and kernel routes handling
>optimizations. The other thing that I don't know is that may be
>there is some compatibility reasons for such secondary flag.
>
>>seems to me that ALL ALIASES should be secondary.  Is this wrong? Why?
>>
>
>	IMO, to keep the semantic of "attaching or detaching an IP
>address" clear and independent, all addresses should be primary
>because it is hard to keep correct setup when it is dynamicaly
>changed. There is already mechanism (the scope) to make one address
>"secondary" in the source address selection mechanism or even there
>is a preferred source to make it primary. This is my opinion but
>may be I'm missing some other usage. At least, the current handling
>looks very dangerous.
>
>Regards
>
>--
>Julian Anastasov <ja@ssi.bg>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>



  reply	other threads:[~2001-10-24  5:31 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 [this message]
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
  -- 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=3BD65188.1060203@blue-labs.org \
    --to=david@blue-labs.org \
    --cc=ja@ssi.bg \
    --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