From: David Miller <davem@davemloft.net>
To: dr@cluenet.de
Cc: netdev@vger.kernel.org
Subject: Re: "src" attribute ignored for IPv6 (preferred source address selection)
Date: Fri, 29 Oct 2010 13:11:06 -0700 (PDT) [thread overview]
Message-ID: <20101029.131106.183062581.davem@davemloft.net> (raw)
In-Reply-To: <20101017011205.GA10610@srv03.cluenet.de>
From: Daniel Roesen <dr@cluenet.de>
Date: Sun, 17 Oct 2010 03:12:08 +0200
> http://lkml.indiana.edu/hypermail/linux/kernel/0409.0/1768.html
>
> Unfortunately I don't have the time (and most probably not the necessary
> kernel knowhow) to hack this up myself, but I'm still interested. :-)
The routing table in ipv6 can very much handle routing by source
address now, if the ip commands mention do not work it's some
bug in the tool or the routing table rule adding code in the
kernel.
It's not a fundamental limitation any more.
prev parent reply other threads:[~2010-10-29 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 9:47 "src" attribute ignored for IPv6 (preferred source address selection) Xavier Roche
2010-10-17 1:12 ` Daniel Roesen
2010-10-29 20:11 ` David Miller [this message]
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=20101029.131106.183062581.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dr@cluenet.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).