All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Newkirk <netfilter@newkirk.us>
To: strenuus <strenuus@sezampro.yu>, netfilter@lists.netfilter.org
Subject: Re: Packets passing trough...
Date: Thu, 14 Nov 2002 20:00:41 -0500	[thread overview]
Message-ID: <200211142000.42011.netfilter@newkirk.us> (raw)
In-Reply-To: <3DD2A913.9030100@sezampro.yu>

On Wednesday 13 November 2002 02:33 pm, strenuus wrote:
> Output from iptables -L -nvx
>
> ---
> Chain FORWARD (policy ACCEPT 161696 packets, 47270419 bytes)
>      pkts      bytes target     prot opt in     out     source             
>  destination 61547  6434012             all  --  *       eth1   
> 192.168.0.0/24       !192.168.1.0/24 59305 36440468             all  -- 
> eth1    *       !192.168.1.0/24       192.168.0.0/24 20358  1239485        
>     all  --  *       eth1    192.168.1.0/24       !192.168.0.0/24 20322 
> 3148918             all  --  eth1    *      !192.168.0.0/24       
> 192.168.1.0/24 3241   561174             all  --  *       *      
> 194.106.188.0/28      192.168.0.0/24 42     5260             all  --  *    
>   *       194.106.188.0/28      192.168.1.0/24 ---
>
> How is this possible, wouldn't all packets match first 4 rules and never
> get to 6 and 7? Interface eth1 goes to internet (snat is on) and eth0 and
> eth2 are LAN (192.168.0.0 and 192.168.1.0)

What's to stop them?  You don't have any targets, so the rules are just 
counters.  Your FORWARD policy is ACCEPT, so they get through anyway, and at 
a quick glance it looks like you have nearly the same number of packets that 
hit policy as your rules counted, all together.

j


      parent reply	other threads:[~2002-11-15  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 19:33 Packets passing trough strenuus
2002-11-14  6:22 ` Jet
2002-11-15  1:00 ` Joel Newkirk [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=200211142000.42011.netfilter@newkirk.us \
    --to=netfilter@newkirk.us \
    --cc=netfilter@lists.netfilter.org \
    --cc=strenuus@sezampro.yu \
    /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.