Log spam: Limiting * response from 1 to 200 packets/sec

Eric van Gyzen vangyzen at FreeBSD.org
Tue Dec 13 15:49:10 UTC 2016


On 12/13/2016 09:24, Michael Butler wrote:
> Any hints as to why all of my -current equipment is complaining like below. Is
> there a sysctl to moderate/turn this off?
> 
> Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200
> packets/sec
> Dec 13 10:00:21 archive last message repeated 13 times
> Dec 13 10:02:21 archive last message repeated 18 times
> Dec 13 10:06:21 archive last message repeated 36 times
> Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200
> packets/sec
> Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to 200
> packets/sec
> Dec 13 10:08:21 archive last message repeated 17 times
> Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 to 200
> packets/sec
> Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to 200
> packets/sec
> Dec 13 10:10:21 archive last message repeated 17 times
> Dec 13 10:12:21 archive last message repeated 18 times
> Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to 200
> packets/sec
> Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to 200
> packets/sec

What Subversion revision are you running?  Did this start happening after a
recent update?  I ask because r309745 was committed a few days ago and might
have changed the behavior.

Eric


More information about the freebsd-current mailing list