All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jet" <yenjet.chan@eglobal.com.my>
To: strenuus <strenuus@sezampro.yu>, netfilter@lists.netfilter.org
Subject: Re: Packets passing trough...
Date: Thu, 14 Nov 2002 14:22:16 +0800	[thread overview]
Message-ID: <003101c28ba6$2ec9bc00$0bc8c80a@dolphin> (raw)
In-Reply-To: 3DD2A913.9030100@sezampro.yu

Hi strenuus,

It is possible. what if the packets are:
Packet=1     interface=eth0                src=194.106.188.1
dst=192.168.0.1
Packet=2    interface=eth0                src=194.106.188.1
dst=192.168.1.1

Packet 1 go into rule 6 and packet 2 go into rule 7.

By the way, have you done this?

for interface in /proc/sys/net/ipv4/conf/*/rp_filter; do
  echo 1 > ${interface}
done

Maybe you want to try this first first and reset the counter. And see if it
still happening.

Good luck.

.//Jet

> 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)
>
>



  reply	other threads:[~2002-11-14  6:22 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 [this message]
2002-11-15  1:00 ` Joel Newkirk

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='003101c28ba6$2ec9bc00$0bc8c80a@dolphin' \
    --to=yenjet.chan@eglobal.com.my \
    --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.