Bug 1315109 - ifconfig -a returns incorrect statistics
Summary: ifconfig -a returns incorrect statistics
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: net-tools
Version: 22
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jiri Popelka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-06 20:50 UTC by Chris Dotson
Modified: 2016-07-25 12:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 20:16:40 UTC
Type: Bug


Attachments (Terms of Use)

Description Chris Dotson 2016-03-06 20:50:59 UTC
Description of problem:

ifconfig -a shows incorrect statistics for an Apple iPhone USB Ethernet device, but ifconfig devicename shows the correct statistics.  The statistics ifconfig -a reports appear to be the statistics of the previous device.  On my system the apple device was right after the docker0 interface, but I can't tell if that's relevant.

/sys/class/net/enp0s19f2u4c4i2/statistics shows that the output from "ifconfig enp0s19f2u4c4i2" is correct, and the statistics in "ifconfig -a" are incorrect.

How reproducible:
Compare device statistics between ifconfig -a and ifconfig devicename

Steps to Reproduce:
1. Plug in an iPhone with tethering turned on and note its devicename
2. ifconfig -a | grep -A 5 devicename; ifconfig devicename

Actual results:
# ifconfig -a | grep -A 5 enp0s19f2u4c4i2; ifconfig enp0s19f2u4c4i2
enp0s19f2u4c4i2: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 72:3e:ac:58:4a:ad  txqueuelen 1000  (Ethernet)
        RX packets 22379978  bytes 1134859474 (1.0 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8180268  bytes 473625334 (451.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
enp0s19f2u4c4i2: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 72:3e:ac:58:4a:ad  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# ifconfig -a 
...
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.42.1  netmask 255.255.0.0  broadcast 0.0.0.0
        inet6 fe80::42:d2ff:fe47:c9a7  prefixlen 64  scopeid 0x20<link>
        ether 02:42:d2:47:c9:a7  txqueuelen 0  (Ethernet)
        RX packets 22379992  bytes 1134861606 (1.0 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8180767  bytes 473667149 (451.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        
enp0s19f2u4c4i2: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 72:3e:ac:58:4a:ad  txqueuelen 1000  (Ethernet)
        RX packets 22379992  bytes 1134861606 (1.0 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8180767  bytes 473667149 (451.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Expected results:
ifconfig -a statistics would be correct

Additional info:

Comment 1 cap.filip.dev 2016-05-16 13:35:38 UTC
Please send me the content of the file located at "/proc/net/dev" as an attachment. At first plug in an iPhone with tethering turned on and then send the file. Thanks

Comment 2 Fedora End Of Life 2016-07-19 20:16:40 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Chris Dotson 2016-07-25 12:47:29 UTC
Apologies that I missed the notifications on this but now that Fedora 22 is EOL I'll see if it happens on Fedora 24.


Note You need to log in before you can comment on or make changes to this bug.