netdev - Re: [RFC:] struct net_device_ops: Add function pointer to fill device specific ndisc information

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: <50FCE228.3090801@gmail.com>
Date:	Mon, 21 Jan 2013 07:37:28 +0100
From:	Stephan Gatzka <stephan.gatzka@...il.com>
To:	YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
CC:	linux1394-devel@...ts.sourceforge.net,
	netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>
Subject: Re: [RFC:] struct net_device_ops: Add function pointer to fill device
 specific ndisc information

> [ARP and NDISC]
> - both can be handled in more natural way.
> -- You will not need to mangle those packets when
>     sending/receiving.

This is also true if we introduce a function pointer. My last 
implementation does not mangle packets in the driver.

> -- You do not need to inspect ARP/NDISC packet.
>     By using netevent notification mechanism, you can
>     learn peer parameters.

That is worth to investigate. Will I get notifications when a ARP/NDISC 
will be send or only if the stack received ARP/NDISC packets? However, I 
can't see how this will help to get the firewire specific information 
into the ARP/NDISC packet. This has to be done either via the suggested 
function pointer or your extension of the mac address.
--
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