All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Schulman <andrex-cmaem7PIVQQM4YKboWzA4l6hYfS7NtTn@public.gmane.org>
To: netfilter-wool9L35kiczKOhml7GhPkB+6BGkLq7r@public.gmane.org
Subject: Re: Iptables don't block traffic
Date: Thu, 22 Apr 2004 10:47:46 -0400	[thread overview]
Message-ID: <MPG.1af1a519745c740e9896b6@localhost> (raw)
In-Reply-To: 4087CE5F.5030503@riafinancial.com

> Hi all, this is my first message to the list, so excuse me if it is 
too
> trivial...
> 
>     I have a Red Hat box running as a firewall in my network. It's
> working fine, but now I'm doing tests in order to block certain Internet
> traffic. I've added the following rules which should drop packets from
> my PC to a known public IP (a web server):
> 
> iptables -A FORWARD -s 192.138.35.110 -d 193.110.128.200 -j DROP
> 
>     But the packets are not droped because I still can connect to the
> web server.

Look at your whole FORWARD chain: 'iptables -v -L FORWARD'.  You have an 
earlier rule in the chain that's allowing those packets through.

If you want to be sure, try replacing '-A' by '-I'.  This will insert 
your rule at the front of the FORWARD chain, instead of at the end.  

>    The default rule for FORWARD chain is DROP

This confirms it.  If you didn't have an earlier rule that was letting 
the packets through, then with a DROP policy you wouldn't need the above 
rule at all.



      parent reply	other threads:[~2004-04-22 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 13:53 Iptables don't block traffic Oscar Arranz
2004-04-22 14:46 ` Antony Stone
2004-04-22 17:03   ` Oscar Arranz
2004-04-22 17:13     ` Rob Sterenborg
2004-04-22 14:47 ` Andrew Schulman [this message]

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=MPG.1af1a519745c740e9896b6@localhost \
    --to=andrex-cmaem7pivqqm4ykbowza4l6hyfs7nttn@public.gmane.org \
    --cc=netfilter-wool9L35kiczKOhml7GhPkB+6BGkLq7r@public.gmane.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.