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
-
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/
This archive was generated by hypermail 2b29 : Wed Oct 31 2001 - 21:00:29 EST