All of lore.kernel.org
 help / color / mirror / Atom feed
From: SaVaGE  <pc-secure@home.nl>
To: netfilter@lists.netfilter.org
Subject: Re: How to block a range of IPs?
Date: Mon, 28 Apr 2003 19:41:38 +0200	[thread overview]
Message-ID: <200304281941.38386.pc-secure@home.nl> (raw)
In-Reply-To: <1051546485.1427.7.camel@jasiiitosh.nexusmgmt.com>

Op maandag 28 april 2003 18:14, schreef John A. Sullivan III:
> You can  use the tool at http://subnetcreator.sourceforge.net/ to easily
> determine which subnets are contained in your IP address range.  The
> same logic is being built into the iptables+ management tool being
> developed in http://iscs.sourceforge.net/ .  However,even better,it
> appears there is a patch available in patch-o-matic that allows one to
> enter a range directly in iptables.  I haven't tried it yet but hope to
> do so soon to replace that logic in ISCS.  Good luck - John
>
> On Sun, 2003-04-27 at 10:06, netfilter-request@lists.netfilter.org
>
> wrote:
> > --__--__--
> >
> > Message: 4
> > From: "Afshin Lamei" <linux_st@hotmail.com>
> > To: netfilter@lists.netfilter.org
> > Subject: How to block a range of IPs?
> > Date: Sun, 27 Apr 2003 10:41:54 +0430
> >
> > Hi,
> > How can I write a rule for a custom range of IPs? for example, I want to
> > block every WWW packet incoming from eth1, which source is an IP between
> > 192.168.1.10 and 192.168.1.20.
> > please help me writing an example.
> > thank you
> > afshin
> >
> >
> >
> >
> >
> > _________________________________________________________________
> > Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> > http://join.msn.com/?page=features/junkmail


AT_HOME_RANGE="213.51.16.0/21 213.51.24.0/21
	 
 ${ECHO} -n "Drop and log @HOME_USERS in range: "
    for athomerange in ${AT_HOME_RANGE} ; do
           ${IPTABLES} -A INPUT -i ${EXT_INTERFACE} -s ${athomerange} -m limit 
\   
               -j LOG --log-prefix "@HOME_USER:DROP "
          ${IPTABLES} -A @HOME_CHK -i ${EXT_INTERFACE} -s ${athomerange} -j 
DROP
        ${ECHO} -n "${athomerange} "
  done
  
this is an example off a line i use  , if you wish to have more ranges, you 
have to make a new rule like this ,but another name like "AT_HOME_RANGE2" 

good luck

Pascal (PC-Secure)


  reply	other threads:[~2003-04-28 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030427140602.30833.28944.Mailman@kashyyyk>
2003-04-28 16:14 ` How to block a range of IPs? John A. Sullivan III
2003-04-28 17:41   ` SaVaGE [this message]
2003-04-28 17:52     ` SaVaGE
2003-04-28 18:06       ` SaVaGE
2003-04-29  7:55   ` Jozsef Kadlecsik
2003-04-27  6:11 Afshin Lamei
2003-04-27  7:25 ` Michael K
2003-04-27 10:42   ` Martin Josefsson
2003-04-27  9:26 ` Cedric Blancher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304281941.38386.pc-secure@home.nl \
    --to=pc-secure@home.nl \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.