From: Richard Hector <rhector@paradise.net.nz>
To: netfilter@lists.netfilter.org
Subject: detect original chain after jump?
Date: Sun, 28 Mar 2004 01:38:01 +1200 [thread overview]
Message-ID: <20040327133801.GA5251@fake> (raw)
Hi,
Mostly, people seem to write their filter chains splitting first by
interface and/or address, then by protocol/port.
I'm experimenting with doing it the other way round: I want to process
all the ssh traffic in one chain, then all the smtp in another etc.
This means that early on, I have something like:
iptables -A INPUT -j protocol
iptables -A FORWARD -j protocol
iptables -A protocol -p tcp --dport 22 -j ssh
But then I get a bit stuck. I need to then do different things depending
on the source and destination - which includes whether this packet is
arriving locally or being forwarded. Therefore it would be useful to
know whether this packet started out in the INPUT or FORWARD chain - but
that info seems to have been lost with the jump.
Is there any way to regain that?
Many thanks,
Richard
next reply other threads:[~2004-03-27 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 13:38 Richard Hector [this message]
2004-03-27 13:51 ` detect original chain after jump? Antony Stone
2004-03-27 14:20 ` Richard Hector
2004-03-27 14:28 ` Antony Stone
2004-03-27 15:07 ` rrecaba
2004-03-27 15:14 ` Antony Stone
2004-03-29 1:27 ` Double Match or jump (was Re: detect original chain after jump?) rrecaba
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=20040327133801.GA5251@fake \
--to=rhector@paradise.net.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox