netdev - Port attributes configuration

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-next>] [day] [month] [year] [list]

Message-ID: <CACWm-Bc4=4We1AfnZpL7O5VkUSKjKBZ-NK6edXW2fE5b_u-e7g@mail.gmail.com>
Date:	Tue, 29 Jul 2014 10:15:10 +0100
From:	Marco Varlese <marco.varlese@...il.com>
To:	netdev@...r.kernel.org
Subject: Port attributes configuration

I'm working on a new platform and the network interfaces will have
quite few new options (roughly 50) to configure. What I definitely
want to achieve is to use the common tools available on Linux to let
users configure the port attributes from user-space without writing a
brand new ad-hoc tool.

Considered my requirements I think I've a choice of configuring these
port attributes via:
1) ethtool: this I guess will require patches to the tool itself plus
patches to the kernel to extend the IOCTL calls performed by it;
2) sysfs: adding new files under /sys/class/net/DEVICE/ and handle the
sysfs extensions in my kernel driver;
3) netlink: I understand this seems to be the path most people prefer
but I think it will require a new tool to be written?

What would you suggest as the best approach here to have a good
solution accepted by most?

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