From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter-devel@vger.kernel.org
Subject: Re: Does Redirect/NAT change the destination port of reverse tuple ?
Date: Fri, 29 Feb 2008 12:52:23 +0100 [thread overview]
Message-ID: <47C7F1F7.9030406@plouf.fr.eu.org> (raw)
In-Reply-To: <005101c87ac0$c0d34580$4279d080$@com>
Hello,
Nishit Shah a écrit :
> I have following iptable rule in system.
>
> iptables -I PREROUTING -t nat -p tcp --dport 443 -j REDIRECT
> --to-ports 3128
> kernel - 2.6.16.13
>
> I am using following scenario for load testing
>
> 192.168.206.200 -----> 192.168.121.125 -----> 72.14.223.83
> Client iptables/proxy server server
>
> and I am getting following entry through conntrack binay as well as
> in /proc/net/ip_conntrack
>
> [NEW] tcp 6 120 NONE src=192.168.206.200 dst=72.14.223.83
> sport=63423 dport=443 packets=1 bytes=48 [UNREPLIED] src=192.168.121.125
> dst=192.168.206.200 sport=3128 dport=46873 packets=0 bytes=0 id=28187887
>
> Now here original and reverse tuples are -->
> Original tuple 192.168.206.200:63423->72.14.223.83:443
> Reply tuple 192.168.121.125:3128->192.168.206.200:46873
>
> So, here destination port of reverse tuple is 46873. Is it correct ?
Yes. NAT may implicitly change the original source port in order to
avoid a clash with an existing connection. However the original port
will be restored in reply packets before they leave the box, so the
client won't see anything. Remember that the tuples in ip_conntrack
contain the addresses and ports when packets enter the PREROUTING or
OUTPUT chains, not when they leave the POSTROUTING or INPUT chains.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-02-29 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 10:49 Does Redirect/NAT change the destination port of reverse tuple ? Nishit Shah
2008-02-29 11:29 ` Jan Engelhardt
2008-02-29 12:00 ` Nishit Shah
2008-02-29 12:04 ` Jan Engelhardt
2008-02-29 12:13 ` Nishit Shah
2008-02-29 11:52 ` Pascal Hambourg [this message]
2008-02-29 12:34 ` Nishit Shah
2008-03-01 12:22 ` Pascal Hambourg
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=47C7F1F7.9030406@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter-devel@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.