Hide Forgot
Description of problem: If interface name is long, pifconfig doesn't display whole name. Version-Release number of selected component (if applicable): python-ethtool-0.8-5.el7 Steps to Reproduce: 1. pifconfig 2. 3. Actual results: <snip> enccw0.0. HWaddr 02:de:ad:be:ef:1e inet addr:10.16.66.221 Bcast:10.16.71.255 Mask:255.255.248.0 inet6 addr: fe80::de:adff:febe:ef1e/64 Scope: link inet6 addr: 2620:52:0:1040:de:adff:febe:ef1e/64 Scope: universe UP BROADCAST RUNNING MULTICAST Expected results: enccw0.0.8000 HWaddr 02:de:ad:be:ef:1e <------- "8000" in interface name inet addr:10.16.66.221 Bcast:10.16.71.255 Mask:255.255.248.0 inet6 addr: fe80::de:adff:febe:ef1e/64 Scope: link inet6 addr: 2620:52:0:1040:de:adff:febe:ef1e/64 Scope: universe UP BROADCAST RUNNING MULTICAST Additional info: ifconfig displays whole name: # ifconfig enccw0.0.8000: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.16.66.221 netmask 255.255.248.0 broadcast 10.16.71.255 inet6 fe80::de:adff:febe:ef1e prefixlen 64 scopeid 0x20<link> inet6 2620:52:0:1040:de:adff:febe:ef1e prefixlen 64 scopeid 0x0<global> ether 02:de:ad:be:ef:1e txqueuelen 1000 (Ethernet) RX packets 14145 bytes 861290 (841.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1303 bytes 549551 (536.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 <snip>
Hello. In the previous versions of python-ethtool there is a 9 chars limit for device name. In the newest version, we have a newline between device name and HW address so the limit is useless here. I've created a simple patch. Github PR: https://github.com/fedora-python/python-ethtool/pull/31 Have a nice day. Lumír
This looks like a low-priority bug, but it's probably an easy fix engineering-wise. python-ethtool is not on the ACL, so it probably won't get fixed in RHEL 7.5. Let me know if that's a problem.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3039