From: Jim Westfall <jwestfall@surrealistic.net>
To: netdev@vger.kernel.org
Subject: ipv6 secondary ips and default ipv6 ip for new outbound connections
Date: Fri, 18 Mar 2011 16:03:12 -0700 [thread overview]
Message-ID: <20110318230312.GX13831@surrealistic.net> (raw)
Hi
On ipv4 the first ip added to a nic will be used as the source ip for
new outbound connections. Any additional ips, in the same netblock,
will be added as secondaries.
ipv6 seems to have the opposite behavior. The last ipv6 ip added to a
nic is be used for new outbound connections.
~# ip -6 addr list br0
11: br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500
inet6 fe80::21a:64ff:fe12:54bd/64 scope link
valid_lft forever preferred_lft forever
~# ip addr add 2600:c00:0:1::1101/64 dev br0
~# traceroute6 www.kame.net | head -0
traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2600:c00:0:1::1101, 30 hops max, 16 byte packets
~# ip addr add 2600:c00:0:1::1102/64 dev br0
~# traceroute6 www.kame.net | head -0
traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2600:c00:0:1::1102, 30 hops max, 16 byte packets
~# ip -6 addr list br0
11: br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500
inet6 2600:c00:0:1::1102/64 scope global
valid_lft forever preferred_lft forever
inet6 2600:c00:0:1::1101/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::21a:64ff:fe12:54bd/64 scope link
valid_lft forever preferred_lft forever
This makes things a bit of a pita when dealing with floater ipv6 ips for
HA.
This there some way to change this behavior to be like ipv4 or force
a specific ipv6 ip to be the default used for new outbound connections?
thanks
Jim Westfall
next reply other threads:[~2011-03-18 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 23:03 Jim Westfall [this message]
2011-03-19 2:23 ` ipv6 secondary ips and default ipv6 ip for new outbound connections Brian Haley
2011-03-19 3:35 ` Jim Westfall
2011-03-19 8:02 ` Andreas Schwab
2011-03-22 0:15 ` Jim Westfall
2011-03-22 2:14 ` Brian Haley
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=20110318230312.GX13831@surrealistic.net \
--to=jwestfall@surrealistic.net \
--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).