Re: blocking I.P. addresses/ranges

From: Garrett Wollman (wollman@khavrinen.lcs.mit.edu)
Date: 07/19/01 

Date: Thu, 19 Jul 2001 12:13:19 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To: Walter Hop <walter@binity.com>

<<On Thu, 19 Jul 2001 14:53:35 +0200, Walter Hop <walter@binity.com> said:

> [in reply to default013subscriptions@hotmail.com, 19-07-2001]
>> I know there is a way to block I.P. addresses/I.P. ranges in Linux by using
>> something like 'route add 24.198.54.0 deny' etc... I assume that there must
>> be a similar way to do this in FreeBSD...

> In FreeBSD, you can do this for instance with the ``ipfw'' tool.

Or, without recourse to the packet-filtering code, using:

        route add -net aa.bb.cc.dd -netmask (some mask) -interface lo0 -reject

However, there is an important caveat to doing this: adding such a
route does not prevent the other party from sending packets to you; it
only prevents your machine from responding. Thus, it does not help
against those attacks which do not require a response.

-GAWollman

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

Relevant Pages

  • FreeBSD Security Survey
    ... While the FreeBSD Security Team has traditionally been very good at ... investigating and responding to security issues in FreeBSD, ... The Security Team has been concerned for some time by anecdotal reports ...
    (FreeBSD-Security)
  • FreeBSD Security Survey
    ... While the FreeBSD Security Team has traditionally been very good at ... investigating and responding to security issues in FreeBSD, ... The Security Team has been concerned for some time by anecdotal reports ...
    (freebsd-stable)
  • FreeBSD Security Survey
    ... While the FreeBSD Security Team has traditionally been very good at ... investigating and responding to security issues in FreeBSD, ... The Security Team has been concerned for some time by anecdotal reports ...
    (freebsd-questions)
  • Re: Files in C.
    ... thanks to all by responding me, I will have present each one of its mail ... I thank to the community of FreeBSD by facilitating me its aid. ...
    (freebsd-hackers)
  • Re: XFree86-4 installation from ports issue (error code 1) on a sparc system
    ... > FreeBSD 5.2. ... Sorry for not responding sooner, ... tightvnc is indeed currently broken on sparc64; ...
    (comp.unix.bsd.freebsd.misc)
Quantcast