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

[Allan Jude]

On 2016-12-13 10: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
> Dec 13 10:14:21 archive last message repeated 17 times
> Dec 13 10:16:21 archive last message repeated 18 times
> 
>     Michael
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"

Yeah, this is a bug. When working as intended, the message would read:

kernel: Limiting closed port RST response from 201 to 200 packets/sec

The first value would be higher than the 2nd value
(net.inet.icmp.icmplim). It should only alert if it is actually limiting
the response rate.

You can mute it by setting: net.inet.icmp.icmplim_output=0

-- 
Allan Jude