From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [HELP] why the string match does not work in nat tables?
Date: Mon, 31 Jan 2011 11:33:43 +0100 [thread overview]
Message-ID: <4D469007.7080606@plouf.fr.eu.org> (raw)
In-Reply-To: <4D46824B.2010706@netfilter.org>
Hello,
Pablo Neira Ayuso a écrit :
> On 31/01/11 03:47, JeHo Park wrote:
>> anyway, i wonder why there is no TCP payload in the skb of the string
>> or wurl match.
>
> Because you only see the first packet of the flow in the NAT table.
And the first packet of a TCP connection usually carries no data.
If you what you want to achieve is NAT a TCP connection based on the
payload, I am afraid this is not possible because the definitive NAT
mapping is defined from the first packet only.
next prev parent reply other threads:[~2011-01-31 10:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 1:53 [HELP] why the string match does not work in nat tables? JeHo Park
2011-01-31 2:09 ` Jan Engelhardt
[not found] ` <AANLkTik02D=agfFrc8VX+Wh4WAg_odm6cEcpbXvbgtqM@mail.gmail.com>
2011-01-31 2:38 ` Jan Engelhardt
2011-01-31 2:47 ` JeHo Park
2011-01-31 2:47 ` JeHo Park
2011-01-31 2:51 ` Jan Engelhardt
2011-01-31 2:51 ` Jan Engelhardt
2011-01-31 2:59 ` JeHo Park
2011-01-31 3:34 ` netfilter - u32 module Sridhar Kumar
2011-01-31 3:34 ` Sridhar Kumar
2011-01-31 9:36 ` Pablo Neira Ayuso
2011-01-31 15:31 ` Sridhar Kumar
2011-01-31 9:35 ` [HELP] why the string match does not work in nat tables? Pablo Neira Ayuso
2011-01-31 10:33 ` Pascal Hambourg [this message]
2011-01-31 11:17 ` JeHo Park
2011-02-01 1:50 ` JeHo Park
2011-02-01 11:51 ` Jan Engelhardt
2011-02-01 12:01 ` Gáspár Lajos
2011-02-01 12:32 ` Pablo Neira Ayuso
2011-02-01 12:35 ` Jan Engelhardt
2011-02-01 12:41 ` Pablo Neira Ayuso
2011-02-01 12:47 ` Jan Engelhardt
2011-02-01 12:57 ` Pablo Neira Ayuso
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=4D469007.7080606@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.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.