Since Xenial now uses "predictable" interface naming schemes, mii-tool's limit will affect most systems.
===== first example ===== # mii-tool no MII interfaces found # mii-tool $(cd /sys/class/net/; ls -d en*) enp4s0: negotiated 100baseTx-FD, link ok enp6s0: negotiated 1000baseT-FD flow-control, link ok enp8s0: negotiated 1000baseT-FD flow-control, link ok enp9s0: no link ===== second example ===== # mii-tool no MII interfaces found # mii-tool $(cd /sys/class/net/; ls -d en*) eno1: negotiated 1000baseT-FD flow-control, link ok SIOCGMIIPHY on 'eno2' failed: Resource temporarily unavailable ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/962616 Title: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument Status in net-tools package in Ubuntu: Confirmed Bug description: On a system with biosdevname enabled, which names NICs in the forms em* and p*p*, mii-tool will return the message "no MII interfaces found" if mii-tool is called without specifying an interface. The correct behavior would be to iterate through em* and p*p*. (More information on biosdevname can be found at http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/962616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
