lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1260214205.9431.53.camel@amd64.fatal.se>
Date:	Mon, 07 Dec 2009 20:30:05 +0100
From:	Andreas Henriksson <andreas@...al.se>
To:	Brian Haley <brian.haley@...com>
Cc:	netdev@...r.kernel.org,
	Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
	Jedasothi <sotheme@...iuu.mine.nu>,
	Bug 487745 <487745@...s.launchpad.net>
Subject: Re: [PATCH/RFC] Adding IP(v6) address with scope link creates
 global address

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

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ