Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Apr 2012 12:26:41 -0700
From:      JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isc.org>
To:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc:        freebsd-net@FreeBSD.org, Andrew Thompson <thompsa@FreeBSD.org>, Hajimu UMEMOTO <ume@FreeBSD.org>, Rainer Bredehorn <Bredehorn@gmx.de>
Subject:   Re: getifaddrs & ipv6 scope
Message-ID:  <m2bomrqxzi.wl%jinmei@isc.org>
In-Reply-To: <7153D609-0E71-435A-B076-27BD6C3AEA04@lists.zabbadoz.net>
References:  <20120413064142.10640@gmx.net> <CAFAOGNRLcadCMCZ8WjaFi3XYhzV55Tp0v=%2BoMGyLOv666bFHkA@mail.gmail.com> <yged37becg7.wl%ume@mahoroba.org> <7153D609-0E71-435A-B076-27BD6C3AEA04@lists.zabbadoz.net>

next in thread | previous in thread | raw e-mail | index | archive | help
At Sat, 14 Apr 2012 16:41:52 +0000,
"Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> wrote:

> > The issue you mentioned comes from an implementation decision of the
> > KAME IPv6 stack.
> > The attached patch should address it.  However, it may break the
> > applications which expect that getifaddrs() returns a link-local
> > address with KAME's embeded scopeid representation.  I'm not sure
> > there are such applications, for now.
> 
> There should be none.  If we have some we should fix them.  I wonder if this should actually be done in the kernel to limit the scope of the embedded scopeid to our kernel for now?   Do we have other interfaces (ignoring kvm) that export the embedded scopeid?

I suspect most of routing related implementations (most notably,
route6d and quagga) still rely on the embedded scope (zone) ID for the
data exchanged over a routing socket.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2bomrqxzi.wl%jinmei>