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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 11 Aug 2014 00:05:13 +0000 From: Roy Marples <roy@...ples.name> To: Hannes Frederic Sowa <hannes@...hat.com> Cc: netdev@...r.kernel.org, "\"David S. Miller\\" <davem@...emloft.net>, Alexey Kuznetsov "\"\"" <kuznet@....inr.ac.ru>, Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>, "\"Patrick"@marples.name, McHardy@...ples.name, " <kaber@...sh.net>"@marples.name Subject: Re: [PATCH] ipv6: do not add link-local address if one already exists Hi On 2014-08-10 20:37, Hannes Frederic Sowa wrote: > On So, 2014-08-10 at 19:56 +0000, Roy Marples wrote: >> Currently the kernel will always add an IPv6 link-local address >> based on the hardware address when the interface is brought up. >> This is probably based on the assumption that userland would >> never add one before the interface is brought up. >> >> However, one at least one userland application (dhcpcd) does this so >> it can implement RFC7217 which can be used for link-local addresses >> as well. >> >> Attached is a patch which checks to see if a link-local address exists >> before indiscriminately adding one. > > Please have a look at: > https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=bc91b0f07ada5535427373a4e2050877bcc12218 > > This was recently implemented just for this specific case. Is that tunable available in /proc or /sys? I'm not overly keen on adding a netlink call just for that in dhcpcd, it would be a lot of bloat compared to the kernel patch. Roy -- 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