From: Peter Bieringer <pb@bieringer.de>
To: netdev@vger.kernel.org
Cc: "JINMEI Tatuya / 神明達哉" <jinmei@isl.rdc.toshiba.co.jp>,
usagi-users@linux-ipv6.org,
"YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Subject: (usagi-users 03690) Re: Bug in order of multiple IPv6 addresses per interface? Newest added one is preferred in difference to IPv4
Date: Mon, 21 Aug 2006 14:36:10 +0200 [thread overview]
Message-ID: <44E9A8BA.8010904@bieringer.de> (raw)
In-Reply-To: <y7vu046b8we.wl%jinmei@isl.rdc.toshiba.co.jp>
JINMEI Tatuya / 神明達哉 schrieb:
>>>>>> On Mon, 21 Aug 2006 12:47:36 +0200,
>>>>>> Peter Bieringer <pb@bieringer.de> said:
>
>>> I do not favor changing this so far.
>
>> Hmm, would it be possible to implement a primary flag in the future?
>
>> BTW: Does anyone know about the behavior of *BSD for this issue?
>
> As far as I know, BSD variants don't have the notion of *explicit*
> 'first/primary' or 'secondary' address. But if your main concern is
> to prefer particular addresses as the source address of outgoing
> packets, you'd be able to achieve the goal by configuring appropriate
> policy table entries (per RFC3484).
Hmm, can I do this on Linux, too for preferring a source address (out of
configured addresses from the *same subnet*)?
I only found:
http://people.redhat.com/drepper/linux-rfc3484.html
But this is more related to destination addresses.
Thank you very much.
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto:pb@bieringer.de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
OpenBC http://www.openbc.com/hp/Peter_Bieringer/
Personal invitation to OpenBC http://www.openbc.com/go/invita/3889
prev parent reply other threads:[~2006-08-21 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 5:36 Bug in order of multiple IPv6 addresses per interface? Newest added one is preferred in difference to IPv4 Peter Bieringer
2006-08-21 10:42 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-21 10:47 ` (usagi-users 03687) " Peter Bieringer
2006-08-21 11:55 ` JINMEI Tatuya / 神明達哉
2006-08-21 12:36 ` Peter Bieringer [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=44E9A8BA.8010904@bieringer.de \
--to=pb@bieringer.de \
--cc=jinmei@isl.rdc.toshiba.co.jp \
--cc=netdev@vger.kernel.org \
--cc=usagi-users@linux-ipv6.org \
--cc=yoshfuji@linux-ipv6.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).