From: Filip Sneppe <filip.sneppe@gmail.com>
To: Peter Lenci <peterlenci@yahoo.ca>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Iptables Match on Direction (IP_CT_IS_REPLY)
Date: Sun, 27 Feb 2005 21:37:38 +0100 [thread overview]
Message-ID: <9151ac2a05022712376c099fb4@mail.gmail.com> (raw)
In-Reply-To: <20050226124304.13105.qmail@web90010.mail.scd.yahoo.com>
Hi Peter,
On Sat, 26 Feb 2005 07:43:03 -0500 (EST), Peter Lenci
<peterlenci@yahoo.ca> wrote:
> Hi there
>
> Is there a possibility to access flag IP_CT_IS_REPLY from an iptables
> command?
>
> I have only spotted the "--direction original|reply|both" option from
> the connbytes patch
> (http://www.netfilter.org/patch-o-matic/pom-extra.html#pom-extra-connbytes)
> but then I would prefer not to waste memory by counting bytes.
>
The "conntrack" match should do what you are looking for. From the help
option:
conntrack match v1.2.11 options:
[!] --ctstate [INVALID|ESTABLISHED|NEW|RELATED|UNTRACKED|SNAT|DNAT][,...]
State(s) to match
[!] --ctproto proto Protocol to match; by number or name, eg. `tcp'
--ctorigsrc [!] address[/mask]
Original source specification
--ctorigdst [!] address[/mask]
Original destination specification
--ctreplsrc [!] address[/mask]
Reply source specification
--ctrepldst [!] address[/mask]
Reply destination specification
[!] --ctstatus [NONE|EXPECTED|SEEN_REPLY|ASSURED|CONFIRMED][,...]
Status(es) to match
[!] --ctexpire time[:time] Match remaining lifetime in seconds against
value or range of values (inclusive)
Regards,
Filip
next prev parent reply other threads:[~2005-02-27 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 12:43 Iptables Match on Direction (IP_CT_IS_REPLY) Peter Lenci
2005-02-27 20:37 ` Filip Sneppe [this message]
2005-03-04 9:35 ` Peter Lenci
2005-03-04 23:27 ` Patrick McHardy
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=9151ac2a05022712376c099fb4@mail.gmail.com \
--to=filip.sneppe@gmail.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=peterlenci@yahoo.ca \
/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.