Andrei Borzenkov wrote:
"dropped" also includes packets with the wrong MAC address so it could be due to e.g. switch packet flooding (or maybe the switch is actually a hub in disguise). In any case, it counts good packets (without error) received by interface but ignored. So it does not necessarily indicate host, rather overall network configuration issues.
I have no idea what "missed" means.
--><-- Counts number of packets dropped by the device due to lack of buffer space. This usually indicates that the host interface is slower than the network interface, or host is not keeping up with the receive packet rate. --><--
Ah, thanks, I swapped the meaning of the two.
Well, if it were me, I would investigate - those numbers seem way too high.
That's about 0.1% of all received packets and we do not know for which period. Are those numbers increasing?
For comparison, I took a look at a couple of my machines. (I just wanted to get a feel for the general situation). "alumni" - uptime 645 days, 4.6E9 packets, 0 dropped, 0 overrun on all interfaces. (lvs frontend, nameserver). "tattoo16" - uptime 343 days, 800E6 packets, 0 dropped, 0 overrun on all interfaces. (mail server). "dresden" - uptime 313 days, 2.6E9 packets, 0 dropped, 0 overrun on all interfaces. (main dhcp, dns, ntp, tftp server). "janeway" - uptime 43min - 100k packets, 1 dropped. (leap 15.5 test machine) Not sure why my stats don't list any 'missed' number, I'm guessing 'overrun' is the same. Maybe my 'ip' is old. Of course, now I am curious to know what that one dropped packet was :-) -- Per Jessen, Zürich (11.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes