Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Dec 2016 11:07:19 -0500
From:      Michael Butler <imb@protected-networks.net>
To:        Eric van Gyzen <vangyzen@FreeBSD.org>, FreeBSD Current <freebsd-current@FreeBSD.org>, glebius@FreeBSD.org, rrs@FreeBSD.org, jtl@FreeBSD.org
Subject:   Re: Log spam: Limiting * response from 1 to 200 packets/sec
Message-ID:  <3dbb632b-e095-1d34-d97f-132bbf54245a@protected-networks.net>
In-Reply-To: <689f6fbe-c59f-2e3a-44d6-bc9d19d31bf9@FreeBSD.org>
References:  <630314dc-e14f-02e7-aa48-4456b0feeef9@protected-networks.net> <689f6fbe-c59f-2e3a-44d6-bc9d19d31bf9@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 12/13/16 10:48, Eric van Gyzen wrote:
> 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.

That's consistent with my observations. I was in Australia for a couple 
of weeks and have just updated from SVN r309056 to r309852,

	Michael





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3dbb632b-e095-1d34-d97f-132bbf54245a>