Date: Mon, 22 Sep 2008 21:03:52 +0400 From: "Jeff Laine" <wtf.jlaine@gmail.com> To: "David Allen" <the.real.david.allen@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Dealing with portscans Message-ID: <2b98f2f70809221003k457b5117v774695e369536242@mail.gmail.com> In-Reply-To: <2daa8b4e0809220817v10c4a657l6ee76f853a62b246@mail.gmail.com> References: <2daa8b4e0809220817v10c4a657l6ee76f853a62b246@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/9/22 David Allen <the.real.david.allen@gmail.com>: > Over the last few weeks I've been getting numerous ports scans, each from > unique hosts. The situation is more of an annoyance than anything else, > but I would prefer not seeing or having to deal with an extra 20-30K > entries in my logs as was the case recently. > > I use pf for firewalling, and while it does offer different methods > (max-src-conn, max-src-conn-rate, etc.) for dealing with abusive hosts, it > doesn't seem to offer much in the way of dealing with repeated blocked > (non-stateful) connection attempts from a given host. > > Short of running something like snort, is there a suitable tool for > dealing with this? If not, I'll probably resort to running a cronjob to > parse the logfile and add the offending hosts manually. Give a try for portsentry from ports collection. -- --Jeff--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2b98f2f70809221003k457b5117v774695e369536242>