From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: iptables NATed or not NATed
Date: Thu, 11 Mar 2010 21:39:26 +0100 [thread overview]
Message-ID: <4B9954FE.5030904@plouf.fr.eu.org> (raw)
In-Reply-To: <4B989616.7000904@perfaction.net>
Patrick Chemla a écrit :
>
> It works, but with tcpdump I have recorded packets on outgoing
> interfaces where addresses are NOT NATed, means, packets issued from
> internal servers on eth0, are routed to default route eth2 with there
> internal address 10.0.0.xx.
>
> It is very strange because it is a small percentage of packets, not all
> the packets from a specific server, directed to the same port than
> others who are routed and NATed the right way, at the same time.
Check the state of those packets. Usually, packets which skip NAT are
those classified in the INVALID state by the connection tracking.
next prev parent reply other threads:[~2010-03-11 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 7:04 iptables NATed or not NATed Patrick Chemla
2010-03-11 8:21 ` Marek Kierdelewicz
2010-03-11 20:39 ` Pascal Hambourg [this message]
2010-03-12 9:19 ` ratheesh k
2010-03-12 20:24 ` 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=4B9954FE.5030904@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.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