All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan G - Mailing List <email-lists@surestorm.com>
To: netfilter@lists.netfilter.org
Subject: Newbie :: Block IP Range seems not to work
Date: Sun, 05 Oct 2003 15:05:41 +0200	[thread overview]
Message-ID: <3F801725.6050207@surestorm.com> (raw)

Hi all,

i'm a newbie in iptables (i have only used commercial products but never 
tried to  write my own rules step by step).

I have read the iptables manual, and other related to server 
configuration but in my case it seems not to work. I'm sure i'm doing 
somrething wrong but i don't know what exactly.

I want to learn to do it fine to modify the default rules that comes 
with IPCop fireall to fit my needs at home.

What i need is to block an ip range completely. I have a internal web 
server. Over my firewall i make a port forward to send all traffic that 
arrives at the firewall to the web server. The firewall own the public 
ip address of my site.

I have used a syntax like this:

iptables -A CUSTOMINPUT -s <RANGE> -j DROP
iptables -A CUSTOMFORWARD -p tcp -s <RANGE> -d <WebSrvIp> --dport 80
iptables -A PORTFWACCESS -p tcp -s <RANGE> -d <WebSrvIp> --dport 80 -j DROP

CUSTOMINPUT is a chain of INPUT type
     - CUSTOMINPUT  all  --  0.0.0.0/0            0.0.0.0/0
CUSTOMFORWARD is a chain of FORWARD type
     - CUSTOMFORWARD  all  --  0.0.0.0/0          0.0.0.0/0
PORTFWACCESS is a chain of FORWARD type
     - PORTFWACCESS  all  --  0.0.0.0/0           0.0.0.0/0

TIA

jonathan

-- 
___________________________________________________________________
  Jonathan Gonzalez - SureStorm.com Security Site - Madrid/MA/SPAIN
  http://www.surestorm.com - GnuPG Key ID = 0xAA3EAC08

  /"\
  \ /  ASCII RIBBON CAMPAIGN
   X   Against HTML mail & Microsoft attachments
  / \



                 reply	other threads:[~2003-10-05 13:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F801725.6050207@surestorm.com \
    --to=email-lists@surestorm.com \
    --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.