netdev - Re: ethtool NFC/ntuple API questions

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: <569FDC04.9090509@solarflare.com>
Date:	Wed, 20 Jan 2016 19:12:04 +0000
From:	Edward Cree <ecree@...arflare.com>
To:	Ben Hutchings <ben@...adent.org.uk>,
	Alexander Duyck <alexander.duyck@...il.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: ethtool NFC/ntuple API questions

Thanks both, it's making more sense now.
One thing I'm still unclear about: why does struct ethtool_usrip4_spechave
the ip_ver field?  The struct can't be extended to cover ipv6, because the
address fields aren't big enough.  So what's it for?

Also, would it be appropriate to use struct in6_addr for IPv6 addresses, or
should I use __be32[4]?

-Ed