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: <20141003.114949.826855678619123407.davem@davemloft.net>
Date:	Fri, 03 Oct 2014 11:49:49 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ulf.samuelsson@...csson.com
Cc:	dcbw@...hat.com, netdev@...gii.com, hannes@...essinduktion.org,
	netdev@...r.kernel.org
Subject: Re: netlink NETLINK_ROUTE failure & Can the kernel really handle
 IPv6 properly

From: Ulf Samuelsson <ulf.samuelsson@...csson.com>
Date: Fri, 3 Oct 2014 09:59:39 +0200

> The kernel module is a control module which collects information
> both from the kernel and from H/W, and talks to a userspace interface
> manager.
> 
> There is a proprietary management application which is used to
> configure the stack.
> This talks to the interface manager to handle different operations for
> IPv6.
> 
> The kernel module needs to know when interfaces are ready to use,
> I.E: know when it exits "tentative" mode to do its job properly,
> so the kernel module has to listen for RTM_NEWADDR.
> 
> In a simpler system, your approach would be OK.

Sorry, we're not going to help you with a proprietary driver
of this kind.

They should really just follow our upstream efforts to design
a usable kernel framework for bridge and routing hardware offloads.
--
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