From: Baruch Even <baruch@ev-en.org>
To: YOSHIFUJI Hideaki <yoshfuji@kame.net>
Cc: Ian McDonald <imcdnzl@gmail.com>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: IPv6 source address selection
Date: Sun, 30 Jul 2006 15:05:57 +0100 [thread overview]
Message-ID: <44CCBCC5.7070507@ev-en.org> (raw)
Hello,
My network has several IPv6 addresses and they don't route between
themselves, due to the current source address selection it means that
many times the network is simply not operational since Linux will choose
an address for a different network than targeted for the connection.
I have seen in thread [1] that there is a patch for this and that
another patch was supposed to be applied for 2.6.15(!), yet I'm using
2.6.17 and nothing works.
Another report about this is at [2]
Could whatever difference exists be resolved and this issue fixed? IPv6
is completely unusable on my network due to this issue.
Thanks,
Baruch
[1] http://marc.theaimsgroup.com/?t=113045346500003&r=1&w=2
[2] http://marc.theaimsgroup.com/?l=linux-net&m=111989050303975&w=2
reply other threads:[~2006-07-30 14:06 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=44CCBCC5.7070507@ev-en.org \
--to=baruch@ev-en.org \
--cc=imcdnzl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@kame.net \
/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).