netdev - Re: ixgbe: How to do this without a module parameter?

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]

Date:   Tue, 26 Oct 2021 01:47:57 +0200
From:   Robert Schlabbach <Robert.Schlabbach@....net>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     netdev@...r.kernel.org
Subject: Re: ixgbe: How to do this without a module parameter?

From: "Andrew Lunn" <andrew@...n.ch>
> What is also useful is that you can put ethtool settings into
> /etc/network/interfaces.

Thank you very much, that was very helpful! I tried it, and indeed, I only had
to add one line to /etc/network/interfaces (the first three lines below were
already there):

# The primary network interface
allow-hotplug eno3
iface eno3 inet dhcp
     pre-up ethtool -s eno3 advertise 0x1800000001028 || true

And I found this to work just as well as the module parameter - the link came
right up at NBASE-T speed after boot.

This was on a Debian 11.1 setup. I suppose this may not work on all distros,
but it works well enough for me.

So I realize using ethtool is a viable solution after all and the module
parameter is not needed. I'd still wish the ixgbe driver would default to full
functionality and require the users with the "bad" switches in their networks
to employ ethtool to cripple its function, but I suppose that'd be tough to
sell to Intel...

Best regards,
-Robert Schlabbach