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

[Gleb Smirnoff]

On Tue, Dec 13, 2016 at 11:07:19AM -0500, Michael Butler wrote:
M> >> Any hints as to why all of my -current equipment is complaining like below. Is
M> >> there a sysctl to moderate/turn this off?
M> >>
M> >> Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200
M> >> packets/sec
M> >> Dec 13 10:00:21 archive last message repeated 13 times
M> >> Dec 13 10:02:21 archive last message repeated 18 times
M> >> Dec 13 10:06:21 archive last message repeated 36 times
M> >> Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200
M> >> packets/sec
M> >> Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to 200
M> >> packets/sec
M> >> Dec 13 10:08:21 archive last message repeated 17 times
M> >> Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 to 200
M> >> packets/sec
M> >> Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to 200
M> >> packets/sec
M> >> Dec 13 10:10:21 archive last message repeated 17 times
M> >> Dec 13 10:12:21 archive last message repeated 18 times
M> >> Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to 200
M> >> packets/sec
M> >> Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to 200
M> >> packets/sec
M> >
M> > What Subversion revision are you running?  Did this start happening after a
M> > recent update?  I ask because r309745 was committed a few days ago and might
M> > have changed the behavior.
M> 
M> That's consistent with my observations. I was in Australia for a couple 
M> of weeks and have just updated from SVN r309056 to r309852,

The r310032 should fix it. I'm sorry for the problem.

-- 
Totus tuus, Glebius.