Date: Wed, 21 Aug 2019 08:52:48 -0700 From: Rudy <crapsh@monkeybrains.net> To: freebsd-net@freebsd.org Subject: Re: packets per second tool for CLI - and question about checksum_errs Message-ID: <56df7dfb-e652-f493-a679-9801960a274a@monkeybrains.net> In-Reply-To: <7d61f797-1674-8c4a-d303-1b057ddf309f@mm.st> References: <380fff29-8df3-2671-69c3-ef47131aaf58@monkeybrains.net> <7d61f797-1674-8c4a-d303-1b057ddf309f@mm.st>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/20/19 10:43 PM, moridin wrote: > systat -ifstat -pps Awesome, that was the command I needed for PPS. Chalk it up to Another re-inventing the wheel! The script does spotlight Checksum Errors on the Intel ethernet ports - should I be concerned with those errors? #sysctl dev.ix. | grep checksum dev.ix.3.mac_stats.checksum_errs: 26 dev.ix.2.mac_stats.checksum_errs: 20844466 dev.ix.1.mac_stats.checksum_errs: 16621802 dev.ix.0.mac_stats.checksum_errs: 8562140 netstat -i" doesn't show any errors. I am reading up on tuning for a router here: https://people.freebsd.org/~olivier/talks/2018_AsiaBSDCon_Tuning_FreeBSD_for_routing_and_firewalling-Paper.pdf and here: https://calomel.org/freebsd_network_tuning.html Adding in " -tso4 -tso6 -lro" flags as well as adjusting the kern.random.harvest.mask - I keep hoping one of them will help with the +Checksum Errors, but I guess if the packets are bad getting to the box, then the errors are what they are: errors. Rudy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56df7dfb-e652-f493-a679-9801960a274a>