So one of my clients configured one of their switches and the resulting configuration resulted in a duplex mismatch between the switch and a Linux host.

We have fixed the duplex mismatch, but is there an easy way to clear the error counters on the interface without restarting the system?

eth0      Link encap:Ethernet  HWaddr 00:nn:nn:nn:nn:nn
          inet addr:  Bcast:  Mask:
          RX packets:630331763 errors:1 dropped:0 overruns:0 frame:0
          TX packets:676081436 errors:1971815 dropped:0 overruns:68637 carrier:1903180
          collisions:7649984 txqueuelen:1000 
          RX bytes:2067682611 (1.9 GiB)  TX bytes:1942809411 (1.8 GiB)

this is not intended, or think to be done. You may unload and load again the network driver if it's loaded as a module:

ifconfig ethX down; rmmod ethX; insmod ethX; ifconfig ethX

There will be a network outage anyway, and a risk if you can't get your hand back on it.

You may reset the switch port stats and check for new errors. Or save this current number and compare against them instead of zero

  • +1. Counters are, by their nature, supposed to be compared against their previous value, regardless of what that value was. – womble Jun 10 '09 at 22:19
  • Note that the kernel modules are rarely called ethX, if ever. They're called according to the actual hardware, such as ne2k, tulip, or whatever. So the rmmod and insmod commands should be changed according to your NICs. – jcoppens Sep 13 '14 at 18:16
  • As said on this AskUbuntu answer you should get the NIC driver, for example with ethtool -i eth0. Also you might be able to just unbind/bind the driver. – Pablo A Dec 30 '18 at 3:22

Have you seen this article?


It suggests that unloading the network driver module and loading it back will reset the counters, and that if you have the module statically linked in the kernel, there's no other way than to reboot it.

The article offers justification.


Resize the ring buffers and the statistics will get reset without downtime.

ethtool -G eth1 rx 511
ethtool -G eth1 rx 4096
  • Interesting take. Seems not to work for vmxnet and wireless interfaces. – Rui F Ribeiro Oct 24 '18 at 10:32
  • 1
    It also doesn't work on Ethernet. ;) (Ubuntu 14.04) – Tomislav Nakic-Alfirevic Jul 16 at 13:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.