From: "Paul Rice" <paul.rice@boomerang-networks.com>
To: netfilter@vger.kernel.org
Subject: NATed internal IP leaking
Date: Mon, 13 Apr 2009 11:49:13 -0500 [thread overview]
Message-ID: <76F066FACCF040F783FA28B9230036C9@PaulPC> (raw)
Hi Guys,
I'm using kernel version 2.6.25.16 and attempted this on 2.6.29 as well.
I'm using ppp0 to connect to verizon wireless and when using Masquerade
NAT, I'm being told by verizon that my client IP's are coming across the
ppp0 interface and they are terminating the connection. I have used 2.4
kernel doing the same thing with no issue like this.
iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE is what I've used
with success in the past.
My question is: Is there a way to keep internal ip's from leaking? I've
experimented with dropping everything 192.168.0.0/24 on ppp0 interface but
no joy.
Thanks,
Paul Rice
reply other threads:[~2009-04-13 16:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=76F066FACCF040F783FA28B9230036C9@PaulPC \
--to=paul.rice@boomerang-networks.com \
--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