From owner-freebsd-current@freebsd.org Tue Dec 13 18:04:25 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEBB1C764FE for ; Tue, 13 Dec 2016 18:04:25 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2F62E2E for ; Tue, 13 Dec 2016 18:04:25 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 75D38BD87 for ; Tue, 13 Dec 2016 18:04:18 +0000 (UTC) Subject: Re: Log spam: Limiting * response from 1 to 200 packets/sec To: freebsd-current@freebsd.org References: <630314dc-e14f-02e7-aa48-4456b0feeef9@protected-networks.net> From: Allan Jude Message-ID: <9412c59f-f2d9-4bda-470e-78f41e11e7f5@freebsd.org> Date: Tue, 13 Dec 2016 13:04:17 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <630314dc-e14f-02e7-aa48-4456b0feeef9@protected-networks.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2016 18:04:25 -0000 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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@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