From: Athan <netfilter@miggy.org>
To: Ian Batterbee <ian.batterbee@aut.ac.nz>
Cc: netfilter@lists.netfilter.org
Subject: Re: Newbie question about having multiple destination addresses in a chain entry
Date: Sun, 5 Jan 2003 12:45:31 +0000 [thread overview]
Message-ID: <20030105124531.GJ16581@miggy.org> (raw)
In-Reply-To: <3E181977.4020204@aut.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On Mon, Jan 06, 2003 at 12:39:35AM +1300, Ian Batterbee wrote:
> Chain PREROUTING (policy ACCEPT 16 packets, 1278 bytes)
> pkts bytes target prot opt in out source
> destination
> 26 1248 NOTHING tcp -- eth0 any anywhere
> 192.168.0.0/24 tcp dpt:www
> 28 1344 REDIRECT tcp -- eth0 any anywhere
> !x.x.0.0/16 tcp dpt:www redir ports 3128
>
> Chain POSTROUTING (policy ACCEPT 29 packets, 1892 bytes)
> pkts bytes target prot opt in out source
> destination
>
> Chain OUTPUT (policy ACCEPT 24 packets, 1638 bytes)
> pkts bytes target prot opt in out source
> destination
>
> Chain NOTHING (1 references)
> pkts bytes target prot opt in out source
> destination
I *think* your problem is that the NOTHING chain is empty, so at the
end of it it just returns to the calling chain. Why not just simply -j
ACCEPT on the rule in PREROUTING? That should stop it processing any
further down the PREROUTING for packets with that destination.
-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-01-05 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 11:39 Newbie question about having multiple destination addresses in a chain entry Ian Batterbee
2003-01-05 12:45 ` Athan [this message]
2003-01-05 13:13 ` Anders Fugmann
[not found] ` <3E183111.8090504@aut.ac.nz>
2003-01-05 13:28 ` Anders Fugmann
2003-01-05 12:54 ` Ian Batterbee
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=20030105124531.GJ16581@miggy.org \
--to=netfilter@miggy.org \
--cc=ian.batterbee@aut.ac.nz \
--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.