On Wed, 24 Nov 2010 20:13:18 -0600, Stan Hoeppner wrote: > Camaleón put forth on 11/24/2010 8:29 AM: > >> If you know a better tool for this then just tell and take our "poor >> minds" from our big ignorance but let me to complain about something I >> consider it should be warned or better yet, corrected. > > There is no "better" tool. There is no tool, period. You are > attempting to query a virtual device for an MII interface. Again, the > MII interface is a piece of SILICON HARDWARE on a NIC. You simply > cannot query a virtual NIC for hardware parameters. > > Now, what I would recommend is that you file a feature request against > mii-tool and ethtool asking that for any query to a bonded virtual NIC > that the physical parameters of each physical NIC be output, along with > the bonding status. However, given how long bonding has been available, > if the devs were going to do this they'd probably have done it by now. > > Maybe someone else wrote a tool with said functionality that superseded > mii-tool and ethtool. If so I am unaware of it. Time for you and the > OP to Google. > > -- > Stan
When I did Google, I see others expressing the same ignorance based on the output of this tool. I appreciate the enlightenment and education you have provided that this tool is not for virtual interfaces. I did not realize that distinction based on the many blogs and other postings peppered across the Internet that include mii-tool as part of setting and troubleshooting interface functions, including bridges and aggregates. Having said that, my opinion is that a software tool, any software tool, would properly renounce incorrect usage at run-time rather than produce misleading output. I rely on how a tool responds, whether it be to my ignorance or proficiency, in order to make as intelligent decisions I am capable of, for what to do next. If that makes me ignorant, well then there's nothing further I can say since this is my opinion; for I am a dumb end-user and developers smarter than me anticipate end-user stupidity and code for these discrepancies. Going forward, I like your suggestion to contact the developers and/or submit feature requests to resolve the situation. But I think the reality is, as you pointed out, doing so is not likely to result in the software changing. It appears to me that the tool has been static for quite some time. I've also read at least one post stating ethtool has replaced mii-tool but I don't know if that claim has validity. Thanks to all who replied, this thread was helpful to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/93e43fd36994fae43b6852f27321c...@192.168.0.66
