From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: netfilter@vger.kernel.org
Subject: Re: iptables - external IP address on internal interface?
Date: Tue, 12 Apr 2011 15:31:11 -0500 [thread overview]
Message-ID: <io2cqf$lba$1@dough.gmane.org> (raw)
In-Reply-To: <1302636361.4938.9.camel@andybev-desktop>
On 04/12/2011 02:26 PM, Andrew Beverley wrote:
>
>>> Can you post the iptables rules that you are using, in particular the
>>> NAT part? What IP address range are you using on the internal network?
>>
>> As requested - output of "iptables -nL"
>>
>
> Having scanned the list of rules (which were pretty difficult to read
> due to line wrapping) I cannot see any SNAT/MASQUERADE targets? If so, I
> would have thought that the behaviour you are seeing is to be expected.
The command "iptables -nL" will show only the "filter" table, so of course
there are no NAT rules shown.
The output from "iptables-save" will be all-inclusive.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
next prev parent reply other threads:[~2011-04-12 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 14:04 iptables - external IP address on internal interface? Tony Rogers
2011-04-11 14:42 ` Usuário do Sistema
2011-04-11 14:53 ` Jan Engelhardt
2011-04-11 17:52 ` Andrew Beverley
2011-04-12 9:20 ` Tony Rogers
2011-04-12 19:26 ` Andrew Beverley
2011-04-12 20:31 ` Robert Nichols [this message]
[not found] ` <1302626146.4938.1.camel@andybev-desktop>
[not found] ` <054F5B1BB94BD943B243C3B39B4F568D0161B8F7@victory.Erudine.local>
[not found] ` <1302636161.4938.5.camel@andybev-desktop>
2011-04-12 21:37 ` Tony Rogers
2011-04-14 20:24 ` Andrew Beverley
2011-04-15 13:21 ` Tony Rogers
2011-04-15 15:29 ` Andrew Beverley
2011-04-20 12:19 ` Tony Rogers
2011-04-20 19:41 ` Andrew Beverley
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='io2cqf$lba$1@dough.gmane.org' \
--to=rnicholsnospam@comcast.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox