From: Florian Westphal <fw@strlen.de>
To: netdev <netdev@vger.kernel.org>
Cc: Daniel Walter <sahne@0x90.at>
Subject: IPv6 PREFSRC behaves different than IPv4 PREFSRC?
Date: Fri, 29 Apr 2011 10:09:16 +0200 [thread overview]
Message-ID: <20110429080916.GB11260@Chamillionaire.breakpoint.cc> (raw)
I tested todays net-next and tried to use the new ipv6 prefsrc
patch that went in this month.
But as far as I can say it does not work, or at least
the behaviour I see is unexpected.
Test setup:
eth0 has addresses 192.168.10.100/24 and dead:1::100/64
With IPv4,
I get this behaviour:
$ ip addr add 192.168.10.101 dev eth0
$ ip route get 192.168.10.1
192.168.10.1 dev eth0 src 192.168.10.100
cache
$ ip route add 192.168.10.1 src 192.168.10.101 dev eth0
$ ip route get 192.168.10.1
192.168.10.1 dev eth0 src 192.168.10.101
cache
$ ip route get 192.168.10.2
192.168.10.2 dev eth0 src 192.168.10.100
cache
And that is what I would have expected... But with ipv6 the behaviour
differs:
ipv6
$ ip route get dead:1::1
dead:1::1 via dead:1::1 dev eth0 src dead:1::100 metric 0
cache
$ ip addr add dead:1::101/64 dev eth0
$ ip route add dead:1::1 src dead:1::101
$ ip route get dead:1::1
dead:1::1 via dead:1::1 dev eth0 src dead:1::101 metric 0
cache
$ ip route add dead:1::2 src dead:1::100
$ ip route get dead:1::2
dead:1::2 via dead:1::2 dev eth0 src dead:1::101 metric 0
-> src is dead:1:101, and not 100 as I had expected...
This behaviour is rather irritating.
What am I doing wrong?
Thanks,
Florian
reply other threads:[~2011-04-29 8:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110429080916.GB11260@Chamillionaire.breakpoint.cc \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=sahne@0x90.at \
/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