Date: Thu, 14 Oct 2021 10:48:11 +0200 From: Rocky Hotas <rockyhotas@post.com> To: pete@nomadlogic.org Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: FreeBSD equivalent of ethtool Message-ID: <trinity-49ded3f0-5c01-4da5-bccc-570e05d7fb6b-1634201291896@3c-app-mailcom-lxa08> In-Reply-To: <3d5a21ba-9502-0362-05ef-349dd57d3bf6@nomadlogic.org> References: <trinity-b425372b-1c26-488b-aeda-273d25479c91-1634167749699@3c-app-mailcom-lxa09> <3d5a21ba-9502-0362-05ef-349dd57d3bf6@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Sent: Thursday, October 14, 2021 at 2:00 AM > From: "Pete Wright via freebsd-questions" <freebsd-questions@freebsd.org= > > To: "Rocky Hotas" <rockyhotas@post.com>, "FreeBSD Questions" <freebsd-qu= estions@freebsd.org> > Subject: Re: FreeBSD equivalent of ethtool [...] > I think it really depends on what your specific use-case is. Sorry, I didn't specify it explicitly. In particular, `ethtool -d <network_interface>', that is: dumping all the values in the internal registers of the NIC. > I find that BSD ifconfig(8) covers most use cases for configuring > interfaces (both physical and virtual), and the sysctl interface is also > useful for pulling and setting device specific information. the latter > is usually well documented in the man page for the interface (see > if_em(4) for example). So, maybe I can look in sysctl or ifconfig(8), if they also allow the register dumping. > it should be noted that ifconfig(8) on bsd's tends to do much more than > the old linux ifconfig and probably the new "ip" command as well. Yes, the BSD one is a very different and complex tool. Rocky
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-49ded3f0-5c01-4da5-bccc-570e05d7fb6b-1634201291896>