netdev - Re: parsing the output of ethtool programmatically

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

Message-ID: <8f53f1ee-ddc6-d7c2-075a-02cf4a529d70@unix-beratung.de>
Date:   Thu, 26 Oct 2017 02:21:57 +0200
From:   Robert Urban <urban@...x-beratung.de>
To:     roopa <roopa@...ulusnetworks.com>,
        Ben Hutchings <ben@...adent.org.uk>
Cc:     bwh@...nel.org, netdev@...r.kernel.org
Subject: Re: parsing the output of ethtool programmatically

may I also suggest being able to specify the offload parameters in the format in
which "ethtool -k <nic>" prints them? The user can only guess which -K
parameters correspond to the -k parameters.


On 09/08/2015 04:52 AM, roopa wrote:
> On 9/5/15, 2:53 AM, Ben Hutchings wrote:
>> On Thu, 2015-06-25 at 03:28 +0200, Robert Urban wrote:
>>> Hello,
>>>
>>> there doesn't seem to be any flag to request ethtool to present its output in a
>>> script-friendly form.  Things like:
>>>>          Link partner advertised link modes:  10baseT/Half 10baseT/Full
>>>>                                               100baseT/Half 100baseT/Full
>>>>                                               1000baseT/Full
>>> are kind of pain to parse.
>>>
>>> Something to consider?
>> Or write a library for using SIOCETHTOOL.  The interface is fairly well
>> documented now and there are other users besides the ethtool utility.
>
> one of the requests which we usually get is ethtool output in json format.
> since iproute2 tools are already getting
> an option to print in json format, would be nice if we considered an option to
> print in json for ethtool too.
>
>