From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: Patrick McHardy <kaber@trash.net>, netfilter@vger.kernel.org
Subject: NAT packets leaking out with source address
Date: Wed, 5 Mar 2008 16:52:31 -0800 [thread overview]
Message-ID: <20080305165231.505bdd44@speedy> (raw)
QA is seeing some (not all packets) going through a NAT router with the
original source address. Is this a known problem? or a configuration issue?
The packets are ICMP echo requests coming in at almost line rate, so some
table could be getting overloaded?
next reply other threads:[~2008-03-06 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 0:52 Stephen Hemminger [this message]
2008-03-06 2:01 ` NAT packets leaking out with source address Philip Craig
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=20080305165231.505bdd44@speedy \
--to=stephen.hemminger@vyatta.com \
--cc=kaber@trash.net \
--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.