Date: Fri, 4 Mar 2011 19:39:58 -0800 From: Patrick Gibson <gibblertron@gmail.com> To: Outback Dingo <outbackdingo@gmail.com> Cc: Jorge Biquez <jbiquez@intranet.com.mx>, Gary Gatten <Ggatten@waddell.com>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Simplest way to deny access to a class C Message-ID: <AANLkTimg3mi_tc0RkXqQUwjV1XnfFvUSQr6eDQqXVs53@mail.gmail.com> In-Reply-To: <AANLkTi=UVGXoRg310mZMa-kU3gVThPzXxOTz-RhBfdes@mail.gmail.com> References: <3382016411-764985335@intranet.com.mx> <AANLkTi=Fb_CiA76g79ZkP8o_yWsQcN6iuPD7w=dBxztQ@mail.gmail.com> <11805_1299196962_4D702C22_11805_70_1_D9B37353831173459FDAA836D3B43499BD354A48@WADPMBXV0.waddell.com> <AANLkTi=619ih7aP8ic_rTqFWVmk_P2Zrob=XJUsvLfHL@mail.gmail.com> <AANLkTi=UVGXoRg310mZMa-kU3gVThPzXxOTz-RhBfdes@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The original question had to do with requests to a web server, and it would not be practical nor typical to route all http traffic through inetd. As well, tcpwrappers require manual work; mod_security and fail2ban are both ban automatically based on specified criteria and patterns. While mod_security only works for Apache, fail2ban works for any service that writes out to a log file. We have it watching our instances of Apache, Postfix, Cyrus IMAP, and sshd services for repeated login failure within a short period of time. It has done wonders. Patrick On Fri, Mar 4, 2011 at 4:30 PM, Outback Dingo <outbackdingo@gmail.com> wrot= e: > > > On Fri, Mar 4, 2011 at 7:14 PM, Patrick Gibson <gibblertron@gmail.com> > wrote: >> >> fail2ban by default only bans an IP for 10 minutes, and that's >> configurable. It can also email you anytime it imposes a ban, so one >> can keep an eye on things at least in the beginning to see if it's >> causing a problem for legitimate users. >> >> On Thu, Mar 3, 2011 at 4:02 PM, Gary Gatten <Ggatten@waddell.com> wrote: >> > Be careful of automated responses. =A0What if someone spoofs IP's of l= egit >> > users / customers / whatever and your automated response blocks them? = =A0Not >> > good. >> > >> > I thought about blocking....well, never mind - might pi$$ someone off >> > and attract unwanted attention... >> > >> > -----Original Message----- >> > From: owner-freebsd-questions@freebsd.org >> > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Patrick Gibs= on >> > Sent: Thursday, March 03, 2011 5:58 PM >> > To: Jorge Biquez >> > Cc: freebsd-questions@freebsd.org >> > Subject: Re: Simplest way to deny access to a class C >> > >> > You might consider mod_security (/usr/ports/www/mod_security) which >> > can be set up to ban hosts based on behaviour or characteristics. >> > >> > Or fail2ban (/usr/ports/security/py-fail2ban) is really great, too, in >> > that it scans whatever logs you want, and can trigger a block in your >> > firewall if enough violating log entries are found within a particular >> > period of time. Everything is totally configurable, and there are >> > plenty of examples that come with it. >> > >> > Patrick >> > >> > >> > On Thu, Mar 3, 2011 at 8:59 AM, Jorge Biquez <jbiquez@intranet.com.mx> >> > wrote: >> >> Hello all. >> >> >> >> I am sorry in advance if this question sounds too stupid. >> >> >> >> I have a small server for personal use of webpages running: >> >> >> >> 7.3-PRERELEASE FreeBSD 7.3-PRERELEASE #0 >> >> >> >> it is working fine , no problem very stable. >> >> >> >> I just need to block some IP class C address that are always trying t= o >> >> "discover" directories or applications under the web server. They do >> >> not do >> >> and can not do anything since this server has nothing installed but i >> >> am >> >> tired of seeing in the logs all the intents they do every 2-3 seconds= . >> >> >> >> I have not installed any kind of firewall yet. >> >> What do you think is the best way to accomplish this task? If possibl= e >> >> the >> >> easiest one. I do not want to do anything else but just bloc IP's, at >> >> this >> >> moment at least. > > I wonder why nobodies mentioned a quite simple method with tcpwrappers an= d > hosts.allow / hosts.deny also > > >> >> >> >> >> Thanks in advance. >> >> >> >> Jorge Biquez >> >> >> >> _______________________________________________ >> >> freebsd-questions@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> >> To unsubscribe, send any mail to >> >> "freebsd-questions-unsubscribe@freebsd.org" >> >> >> > _______________________________________________ >> > freebsd-questions@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > To unsubscribe, send any mail to >> > "freebsd-questions-unsubscribe@freebsd.org" >> > >> > >> > >> > >> > >> > <font size=3D"1"> >> > <div style=3D'border:none;border-bottom:double windowtext >> > 2.25pt;padding:0in 0in 1.0pt 0in'> >> > </div> >> > "This email is intended to be reviewed by only the intended recipient >> > =A0and may contain information that is privileged and/or confidential. >> > =A0If you are not the intended recipient, you are hereby notified that >> > =A0any review, use, dissemination, disclosure or copying of this email >> > =A0and its attachments, if any, is strictly prohibited. =A0If you have >> > =A0received this email in error, please immediately notify the sender = by >> > =A0return email and delete this email from your system." >> > </font> >> > >> > >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimg3mi_tc0RkXqQUwjV1XnfFvUSQr6eDQqXVs53>