From: Peter Bieringer <pb@bieringer.de>
To: Maillist netdev <netdev@vger.kernel.org>
Subject: Bug in order of multiple IPv6 addresses per interface? Newest added one is preferred in difference to IPv4
Date: Mon, 21 Aug 2006 07:36:19 +0200 [thread overview]
Message-ID: <44E94653.1040002@bieringer.de> (raw)
Hi,
if I add an additional IPv4 address of the same subnet ("IP aliasing",
used for virtual hosting), it's added after the first one and also get
the flag "secondary":
# ip -4 addr show dev eth0 | grep -w inet
inet 192.0.2.11/24 brd 192.0.2.255 scope global eth0
# ip -4 addr add 192.0.2.253/24 dev eth0
# ip -4 addr show dev eth0 | grep -w inet
inet 192.0.2.11/24 brd 192.0.2.255 scope global eth0 <- #1
inet 192.0.2.253/24 scope global secondary eth0 <- #2
The new added address is also *not* used for outgoing connections by
default.
In IPv6, the behavior is completly different:
# ip -6 addr show dev eth0 |grep -w inet6 |grep -w global
inet6 2001:db8:0:1::11/64 scope global
# ip -6 addr add 2001:db8:0:1::253/64 dev eth0
# ip -6 addr show dev eth0 |grep -w inet6 |grep -w global
inet6 2001:db8:0:1::253/64 scope global <- #2 !!!!
inet6 2001:db8:0:1::11/64 scope global <- #1
So the last added on is now the first in list. Also, it gets no
"secondary" flag and "ip" doesn't even support this flag.
And the worse thing is that the first one in list (= last added one) is
now used as default for outgoing connections. Can be easily tested using
"ping6".
Is this a bug (I hope so) or a (undocumented?) feature?
How can I add additional IPv6 addresses from the same subnet to an
interface without changing implicit the default outgoing address.
Current workaround: adding new address, remove and readd primary IPv6
address (which is afterwards the first one in list again).
BTW: this can break at least initscripts, which support more than one
address per interface (a primary and some secondary ones), see also:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199862 (a
workaround is described here)
Used versions:
kernel-2.6.17-1.2174_FC5 (happen also below, e.g. 2.6.9 from RHEL4)
iproute-2.6.15-1.2
Regards,
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto:pb@bieringer.de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
next reply other threads:[~2006-08-21 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 5:36 Peter Bieringer [this message]
2006-08-21 10:42 ` Bug in order of multiple IPv6 addresses per interface? Newest added one is preferred in difference to IPv4 YOSHIFUJI Hideaki / 吉藤英明
2006-08-21 10:47 ` (usagi-users 03687) " Peter Bieringer
2006-08-21 11:55 ` JINMEI Tatuya / 神明達哉
2006-08-21 12:36 ` (usagi-users 03690) " Peter Bieringer
-- strict thread matches above, loose matches on Subject: below --
2006-08-21 9:26 Mark Smith
2006-08-21 10:00 ` Peter Bieringer
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=44E94653.1040002@bieringer.de \
--to=pb@bieringer.de \
--cc=netdev@vger.kernel.org \
/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).