netdev - Re: [patch net-next v2] ipv6: addrconf: implement address generation modes

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: <20140711.150608.2139135205801597614.davem@davemloft.net>
Date:	Fri, 11 Jul 2014 15:06:08 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jiri@...nulli.us
Cc:	netdev@...r.kernel.org, kuznet@....inr.ac.ru, jmorris@...ei.org,
	yoshfuji@...ux-ipv6.org, kaber@...sh.net,
	sfeldma@...ulusnetworks.com, arvid.brodin@...en.se,
	sucheta.chakraborty@...gic.com, hannes@...essinduktion.org,
	stephen@...workplumber.org, dcbw@...hat.com
Subject: Re: [patch net-next v2] ipv6: addrconf: implement address
 generation modes

From: Jiri Pirko <jiri@...nulli.us>
Date: Fri, 11 Jul 2014 21:10:18 +0200

> This patch introduces a possibility for userspace to set various (so far
> two) modes of generating addresses. This is useful for example for
> NetworkManager because it can set the mode to NONE and take care of link
> local addresses itself. That allow it to have the interface up,
> monitoring carrier but still don't have any addresses on it.
> 
> One more use-case by Dan Williams:
> <quote>
> WWAN devices often have their LL address provided by the firmware of the
> device, which sometimes refuses to respond to incorrect LL addresses
> when doing DHCPv6 or IPv6 ND.  The kernel cannot generate the correct LL
> address for two reasons:
> 
> 1) WWAN pseudo-ethernet interfaces often construct a fake MAC address,
> or read a meaningless MAC address from the firmware.  Thus the EUI64 and
> the IPv6LL address the kernel assigns will be wrong.  The real LL
> address is often retrieved from the firmware with AT or proprietary
> commands.
> 
> 2) WWAN PPP interfaces receive their LL address from IPV6CP, not from
> kernel assignments.  Only after IPV6CP has completed do we know the LL
> address of the PPP interface and its peer.  But the kernel has already
> assigned an incorrect LL address to the interface.
> 
> So being able to suppress the kernel LL address generation and assign
> the one retrieved from the firmware is less complicated and more robust.
> </quote>
> 
> Signed-off-by: Jiri Pirko <jiri@...nulli.us>

Applied, thanks Jiri.
--
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