From: Marek Kierdelewicz <marek@piasta.pl>
To: Patrick Chemla <patrick.chemla@perfaction.net>
Cc: netfilter@vger.kernel.org
Subject: Re: iptables NATed or not NATed
Date: Thu, 11 Mar 2010 09:21:01 +0100 [thread overview]
Message-ID: <20100311092101.63e64dbc@catlap> (raw)
In-Reply-To: <4B989616.7000904@perfaction.net>
>Hi,
Hi,
>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.
>Again: a small percentage of packets issued by the same server, to the
>same destination port, maybe not the same public server are routed
>without NATing, while most of the packets from the same computer are
>well routed and NATed.
Try using "ip ro sh cache" to see what's in there. If you see "stale"
cache entries "ip ro flush cache" should fix the problem.
Best regards,
Marek
next prev parent reply other threads:[~2010-03-11 8:21 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 [this message]
2010-03-11 20:39 ` Pascal Hambourg
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=20100311092101.63e64dbc@catlap \
--to=marek@piasta.pl \
--cc=netfilter@vger.kernel.org \
--cc=patrick.chemla@perfaction.net \
/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