From: Ian Batterbee <ian.batterbee@aut.ac.nz>
To: Athan <netfilter@miggy.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Newbie question about having multiple destination addresses in a chain entry
Date: Mon, 06 Jan 2003 01:54:44 +1300 [thread overview]
Message-ID: <3E182B14.6010402@aut.ac.nz> (raw)
In-Reply-To: <3E181977.4020204@aut.ac.nz>
>
>
> 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.
>
>
>
arghagh! I *KNEW* it would be something simple like that. I don't know
how I managed to miss the target ACCEPT for so long!
yes.. that does it nicely :) Thanks!
prev parent reply other threads:[~2003-01-05 12:54 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
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 [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=3E182B14.6010402@aut.ac.nz \
--to=ian.batterbee@aut.ac.nz \
--cc=netfilter@lists.netfilter.org \
--cc=netfilter@miggy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox