Hi, On Mon, Jun 5, 2023 at 10:14 AM Roger Heflin <rogerhef...@gmail.com> wrote:
> The earlier mentioned fact you have that using tcpdump causes the > drops to disappear indicates that whatever the packets are the nic > believes they aren't destined for your host. > > Use this to see all packets not going to your local node. > tcpdump -i <yournetinterface> ! host <youripaddress> > > If those packets are close to the number of the drops/min those are > likely the drops. > > The issue with "drops" is they aren't what most people think are drops > (ie packets my host does not care about) most of the time. I about > the only time real drops happen involve the nic interface running > > 25% rated and/or the host being under extreme cpu or paging stress. > I was really hoping (wanting) this to also be the solution, but it's not :-( Excluding the host itself and any other related traffic shows a ton of IPv6 and ARP traffic produced by the default gateway in a very consistent pattern. The dropped packets are relatively consistent, but update at a slower interval, like once every other time the RX/TX packet counters are updated. Also, I have another host on the same cable modem that does not have any dropped packets ever. The only difference is that it's running shorewall and is a gateway to the internal LAN. There's something that host is doing to address these packets so they're not counted. >
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
