netdev - RE: [patch net-next] ipv6: allow userspace to create address with IFLA_F

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B73E2@saturn3.aculab.com>
Date:	Tue, 5 Nov 2013 17:12:46 -0000
From:	"David Laight" <David.Laight@...LAB.COM>
To:	<nicolas.dichtel@...nd.com>, "David Miller" <davem@...emloft.net>,
	<jiri@...nulli.us>, <vyasevich@...il.com>,
	<netdev@...r.kernel.org>, <kuznet@....inr.ac.ru>,
	<jmorris@...ei.org>, <yoshfuji@...ux-ipv6.org>, <kaber@...sh.net>,
	<thaller@...hat.com>, <stephen@...workplumber.org>
Subject: RE: [patch net-next] ipv6: allow userspace to create address with IFLA_F_TEMPORARY flag

> From: Nicolas Dichtel [mailto:nicolas.dichtel@...nd.com]
...
> If I remember well, another problem is to be able to send these packets with
> 0.0.0.0 when another IP address is available on the system:
> 
> RFC2131
> 4.1 Constructing and sending DHCP messages
> ...
>     DHCP messages broadcast by a client prior to that client obtaining
>     its IP address must have the source address field in the IP header
>     set to 0.
> 
> We made a patch (never proposed upstream) to add a socket option to keep
> this 0.0.0.0 address.
> If people are interested, I can try to port it on net-next.

Really, what dhcp does before the interface has an address doesn't
really matter - using bpf isn't a problem.

What it needs to do is switch to using a normal socket for the renewals.

Maybe I'll try asking Roy about it on the NetBSD lists.

	David