netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: JeHo Park <linuxpark@gmail.com>
To: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: [HELP] why the string match does not work in nat tables?
Date: Mon, 31 Jan 2011 10:53:33 +0900	[thread overview]
Message-ID: <AANLkTinoBfMTDNVLHuBhMFJHHSrMmP0gwYTz2AX3f_ew@mail.gmail.com> (raw)

hi there

i have been trying to apply the string match or external wurlmatch to
my NAT environment.
but the matches was not valid in NAT or tproxy
so i tried to verify TCP payload with debugging code in the string
match during runtime, and then i found there is no TCP data in skbuff

the string match works well in filter table, but it does not work in NAT.
i want to know why the string match does not work in NAT.
if you know that reason, please let me know


i used following iptables rules
#  iptables -A PREROUTING -t nat -p tcp --dport 80 -m string --string
"goole.com" --algo bm -j DNAT --to-destination 10.10.10.125:80

10.10.10.125 is IP address of my linux router and there is HTTP proxy server

             reply	other threads:[~2011-01-31  1:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31  1:53 JeHo Park [this message]
2011-01-31  2:09 ` [HELP] why the string match does not work in nat tables? Jan Engelhardt
     [not found]   ` <AANLkTik02D=agfFrc8VX+Wh4WAg_odm6cEcpbXvbgtqM@mail.gmail.com>
     [not found]     ` <alpine.LNX.2.01.1101310337270.19252@obet.zrqbmnf.qr>
2011-01-31  2:47       ` JeHo Park
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  9:36           ` Pablo Neira Ayuso
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
2011-01-31 11:17             ` JeHo Park
2011-02-01  1:50           ` JeHo Park
2011-02-01 11:51             ` Jan Engelhardt

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=AANLkTinoBfMTDNVLHuBhMFJHHSrMmP0gwYTz2AX3f_ew@mail.gmail.com \
    --to=linuxpark@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).