From: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
To: Juha-Matti Tapio <jmtapio@verkkotelakka.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] [IPV6]: Fix source address selection for ORCHID addresses
Date: Sun, 2 Mar 2008 20:11:48 +0200 [thread overview]
Message-ID: <200803022011.48294.rdenis@simphalempin.com> (raw)
In-Reply-To: <20080221100842.GA24905@verkkotelakka.net>
Moi,
Le Thursday 21 February 2008 12:08:42 Juha-Matti Tapio, vous avez écrit :
> Skip the prefix length matching in source address selection for
> orchid -> non-orchid addresses.
>
> Overlay Routable Cryptographic Hash IDentifiers (RFC 4843,
> 2001:10::/28) are currenty not globally reachable. Without this
> check a host with an ORCHID address can end up preferring those over
> regular addresses when talking to other regular hosts in the 2001::/16
> range thus breaking non-orchid connections.
This is not really a "kernel" issue, but did you consider fixing glibc as
well, as it needs to replicate source address selection as well in
getaddrinfo()? There you will not only have problems with Rule 8, but
possibly also with Rule 2 as you will have to take IPv4 addresses into
account: e.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468801
--
Rémi Denis-Courmont
http://www.remlab.net/
prev parent reply other threads:[~2008-03-02 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 10:08 [PATCH 2/2] [IPV6]: Fix source address selection for ORCHID addresses Juha-Matti Tapio
2008-02-29 4:55 ` David Miller
2008-03-02 12:39 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-02 16:54 ` Juha-Matti Tapio
2008-03-02 18:02 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-02 21:59 ` Juha-Matti Tapio
2008-03-03 10:19 ` [PATCH 2/2] [IPV6]: Fix source address selection for ORCHIDaddresses Remi Denis-Courmont
2008-03-03 11:19 ` Juha-Matti Tapio
2008-03-02 18:11 ` Rémi Denis-Courmont [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=200803022011.48294.rdenis@simphalempin.com \
--to=rdenis@simphalempin.com \
--cc=jmtapio@verkkotelakka.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).