Date: Wed, 17 Oct 2001 09:37:18 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: David Malone <dwmalone@maths.tcd.ie> Cc: Zhihui Zhang <zzhang@cs.binghamton.edu>, freebsd-hackers@freebsd.org Subject: Re: Limiting closed port RST response Message-ID: <3BCDB3BE.1B2E6AC6@mindspring.com> References: <Pine.SOL.4.21.0110171141520.608-100000@onyx> <20011017171016.A66131@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
David Malone wrote: > > I was using FreeBSD a while ago, suddenly a lot of messages show up: > > > > Limiting closed port RST responses from 224 to 200 packets per seconds. > > > > These messages persist even after reboot. What happened? What should I do? > > Could someone be port scanning you? Another possibility is that you > alot of machines are trying to contact a TCP service on the machine > in question, which isn't running. I've seen this while doing load testing. In general, you want the limit threshold to be higher than the connections per second rate, or you will get this message. I have modified my code locally to crank it up to twice the listen queue depth. Frequently, you are just better off by turning of the limiting entirely (there's s sysctl; look at the code in netinet that emits the message, or grep sysctl -A for "lim"). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BCDB3BE.1B2E6AC6>