netdev - Re: netlink NETLINK_ROUTE failure & Can the kernel really handle IPv6 properly

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: <1412199032.2532289.174101717.2D6510D0@webmail.messagingengine.com>
Date:	Wed, 01 Oct 2014 23:30:32 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Ulf Samuelsson <netdev@...gii.com>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: netlink NETLINK_ROUTE  failure & Can the kernel really handle IPv6
 properly

Hello,

On Wed, Oct 1, 2014, at 22:28, Ulf Samuelsson wrote:
> BTW, the problem I am trying to solve is how to connect to an I/F with 
> an IPv6 link-local address.
> 
> An existing kernel module waits for a NETDEV_UP event, and then tries to 
> communicate
> with the link-local address.
> 
> This will fail, because (according to a colleague) the I/F enters a 
> "tentative" state,
> where it is trying to decide if it is unique or not.
> It will remain in that state for 1-2 seconds, and only afterwards is the 
> link-local address
> available for normal use.
> 
> The guys writing the module, claim that the kernel is using NETDEV_UP.
> There is very little code in the kernel using NETLINK_ROUTE, even in 
> latest stable.
> It is using NETDEV_UP.
> 
> If my colleague is right, the kernel really cannot handle IPv6 
> link-local addresses properly.

Sorry, I cannot really follow you, can you send example code or be a bit
more precise?

Thanks,
Hannes
--
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