From: Andreas Henriksson <andreas@fatal.se>
To: Brian Haley <brian.haley@hp.com>
Cc: netdev@vger.kernel.org,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Jedasothi <sotheme@nphiuu.mine.nu>,
Bug 487745 <487745@bugs.launchpad.net>
Subject: Re: [PATCH/RFC] Adding IP(v6) address with scope link creates global address
Date: Mon, 07 Dec 2009 20:30:05 +0100 [thread overview]
Message-ID: <1260214205.9431.53.camel@amd64.fatal.se> (raw)
In-Reply-To: <4B1D38CE.1060001@hp.com>
Adding submitter and launchpad bug to CC.
On mån, 2009-12-07 at 12:18 -0500, Brian Haley wrote:
> Hi Andreas,
>
> Andreas Henriksson wrote:
> > Hello again!
> >
> > Replying to myself (see http://www.spinics.net/lists/netdev/msg113943.html)
> > and attaching an untested patch to see if this sparks more interest.
> >
> > On Wed, Nov 25, 2009 at 02:59:45PM +0100, Andreas Henriksson wrote:
> >> "Jedasothi" reported problems setting scope with iproute on newly added
> >> ipv6 addresses in:
> >> https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/487745
> >>
> >>> To reproduce bug run
> >>> ip addr add '::4/64' scope link dev eth0
> >>>
> >>> This results in a line seen with
> >>> ip addr show eth0
> >>> inet6 ::4/64 scope global tentative
> >>>
> >>> The label "global" is seen instead of "link".
> >
> > I'd appreciate if someone could review and test this:
>
> I tried the patch quickly since I was curious why this is a problem, but
> it didn't work exactly right. I could post an update, but I'm not sure
> this is the right thing to do - ::4 isn't a link-local address, and other
> parts of the network stack (and other systems) aren't going to treat it as
> such.
>
> Maybe the submitter can explain exactly how this is breaking something?
>
> Thanks,
>
> -Brian
prev parent reply other threads:[~2009-12-07 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 13:59 Adding IP(v6) address with scope link creates global address Andreas Henriksson
2009-12-07 13:41 ` [PATCH/RFC] " Andreas Henriksson
2009-12-07 17:18 ` Brian Haley
2009-12-07 19:30 ` Andreas Henriksson [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=1260214205.9431.53.camel@amd64.fatal.se \
--to=andreas@fatal.se \
--cc=487745@bugs.launchpad.net \
--cc=brian.haley@hp.com \
--cc=netdev@vger.kernel.org \
--cc=sotheme@nphiuu.mine.nu \
--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).