Lets say you want to reset all of the counters to 0.

Given this, we need this:

You want this:


– have ethtool:  apt-get install ethtool – Have a physical connection to the device:
If you only have a network connection to a device this will be impossible, unless you have another means of connection to the device such as via


There are 2 situations, one in which you can reset the counters and one in which you cant.

The current way to reset the counters is to just disable the driver and then renable it. Not all drivers can be disables. Here are the 2 situations.


Lets find out if your in 1st or 2nd situation.

Look at the counters and identify the interface name:

In this case its eth0, lets get the driver name:

Here the driver name showed me the interface is e1000e (this is an Intel driver)

We will run “# modprobe -D DRIVERNAME” and based on the output find out if you can reset them or not.

The above output shows that the driver is dependent on other drivers, and mainly it doesnt say that its kernel built-in driver. Thus this is situation 1 and you can reset the counters.

Another example of situation 1 is very similar output, but take the Atheros atl1c driver on my PC (the driver in this case is also not kernel built-in).

The above is also module driver (even though it doesnt list any dependencies but only lists it self). Thus this falls into the case that you can reset the counters.


Below is the other type of output from modprobe -D

The above is situation 2, the driver is kernel-built in. Thus you cant reset the counters

Here is the summary of both cases:

If your driver is not kernel-built in but it is a module that is added in via “insmod” or “modprobe”. Therefore you can see it with “lsmod”.

First run ifconfig to get the interface name:

Now run ethtool to get the driver name (or however you want to get the driver name). Lets imagine its eth0.

In this case lets pretend the driver name DRIVERNAME. Now check that the driver is not a kernel built-in driver with modprobe.

If it doesnt say “kernel built-in” then you can proceed with resetting the counters (By first removing/disabling the driver). If it says the driver is “kernel built-in” then you cannot proceed with resetting the counters (read …2… below).

Remove the driver (This doesnt really remove the driver, it just disables it):

At this point if you were sshed/telneted in or connected via network protocol, you will lose connection and you will need to reconnect physically to the PC/device via console or physical acccess (keyboard/monitor)

Now you can enable the driver:

Now look at the counters they should be all 0:


If your drive is kernel built-in, then there is no way currently to reset the driver. As you cant turn off the driver and reenable it. Currently that is the only way to reset those counters.

Why cant we reset drivers that are kernel built-in? Check out this link

Author says:

  • ” module built-in the kernel: in this case there is no way to reset the counters (of course without rebooting the system) if the particular network module driver has not a way to reset them using some code written inside the driver. From what I have seen in the source code of the modules I had used, none of them had such a software hook. But there might be other modules that offer this functionality just that I have not personally seen it on the common NIC drivers I have used.”


4 thoughts on “Resetting the RX/TX and Error Counters on ifconfig

    1. Wow! Cool stuff, I love kernelling – im a noob at it, but I love it.


      Well I tried “crash”, but it seems that it doesnt work for every kernel. Here is my troubles with using “crash” a couple of minutes: If we are going to be “crash”ing a live machine we need the kernel vmlinuz file & /dev/mem (luckily your article explains what to do if its locked, and for it wasnt). The problem is the vmlinuz file, not all OS provide kernels vmlinuz files (such as containers from openvz), and if they are provided they might be hidden (such as on a NAS device from certain vendors), and if you were to somehow unhide it, you could still face the next problem & another problem after that. The next problem being if you were to get the kernel it could be compressed – lucky for us thats easy fix: decompress with
      Check this link out

      For “crash” you need an extracted kernel/vmlinuz file – Here is how I got it extracted (vmlinux can be extracted via below script, which sits in scritps folder of kernel source code tree):

      I did mention there might be another problem – here it was for me, lets say we get it extracted (first problem solved), the next problem is the kernel could be compiled without the right module? Im not sure but from my reading it look like the bug im getting here means i dont have the right module:

      Note I ran crash like this:

      Note: My /dev/mem didnt seem to be locked, so I didnt need to unlock at as per your 2nd link.

      Here is the error I got:

      I dont have an idea how I can just insert the correct modules (mentioned here into my current running kernel without doing a full on recompile and telling my bootloader to use this new kernel (the problem is sometimes we cant get access to the bootloader, or at least its a very lengthy process)

      Do you by chance know the fix to .gnu_debuglink, without recompiling the kernel?

  1. damn, you’re right. I’m so used to redhat at the office I forgot to test at home on my funtoo.

    Long story short, the “debuginfo” are debugging information in a separate file instead of built in the binary. This allows debugging of a production image without the overhead of debug information. GDB (on which crash is built) works like this.
    To manipulate binary data, we have a few (very useful) tools : strip, objdump, objcopy, ar…
    The idea for the kernel (and its modules) is to compile them with debugging, copy these debug detail to another file (objcopy) and remove them from the bin (strip).

    As long as you are able to compile a kernel with the same options used to get your running one, you don’t need to reboot or change the kernel. We’ll only extract the debug information.

    Sooo, 2 ways to get these debuginfo :
    – If you are using a kernel published by your distribution, most of the time they may provide the debuginfo package (or in another name, like dbgsym for debian).
    If they don’t, you may check for their tutorial on how to compile the kernel, and add a flag they omitted (it’s really distro dependant, just check the help).
    – If you are making your own kernel (like I do on Gentoo) you’ll need to do it by yourself. It may be worth checking the configuration

    “Kernel Hacking => Compile the kernel with debug info”

    A stackoverflow thread looks correct but you’ll need to do it for every kernel module.
    If you want to save some time, you may just do this for the modules loaded :
    for i in $(lsmod|awk 'NR>1{print $1}'); do
    file="$(modinfo -F filename $i)"
    echo ${file#/lib/modules/*/}

    If I got some time, I’ll try to script these steps also…

    Have fun.

    1. Yes, please provide that script! all info is appreciated.

      My XMAS wishes:

      (1) I wish there was a guide on how to get “debug” and “crash” running for a live debian system – for a live system thats running a common kernel (which anyone can download via apt-get). this way anyone can debug a common system

      (2) And also if there was a guide on how to get “debug” and “crash” running for a live debian system – for a live system thats running a non-common kernel (a user compiled kernel), and where, of course, the whole kernel source tree is available. this way anyone can debug a non-common system

Leave a Reply

Your email address will not be published. Required fields are marked *