From: Uwe Eisner <Uwe.Eisner@globit.com>
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: netfilter@lists.samba.org
Subject: Re: SNAT does not work
Date: Thu, 06 Jun 2002 16:45:42 +0200 [thread overview]
Message-ID: <3CFF7596.4090300@globit.com> (raw)
In-Reply-To: 200206061357.g56DvOA31162@vulcan.rissington.net
[-- Attachment #1: Type: text/plain, Size: 2613 bytes --]
Antony Stone schrieb:
>On Thursday 06 June 2002 2:27 pm, Uwe Eisner wrote:
>
>Hi.
>
>Having read your email again, I realise that I do not understand what problem
>you're having...
>
>
>
>>I'm using a internal ip-range, wherefor I need NAT to connecting to the
>>internet..
>>
>>
>
>Okay, yes - I understand that.
>
>
>
>>My problem is, that this rule does not work. When I start a Perl-code at
>>the www, witch shows me my ip-address, it showes me the IP-address of
>>the external interface of the router/firewall.
>>
>>
>
>Surely that means that your address translation *is* working ?
>
But why is the external ip-address from the firewall showen at the www?
I specifyed the IP-address 141.12.218.99 not 141.12.129.9 (ext.
Router-IP-Address)
>
>1. If it were not, the remote web server would not be able to establish a
>connection.
>
>2. The external address of the firewall is the address you would expect to be
>coming from when yu use the SNAT rule.
>
>3. If you are running a Perl script, I assume that means that a TCP 3-way
>handshake has been completed, which means the web server has successfully
>been able to send packets back to your client.
>
>
>
>>I can not find the problem.
>>
>>
>
>What *is* the problem ?
>
>
>
>>If I set no POSTROUTING rule, it is the same game...
>>
>>
>
>I do not understand what you mean by this. Surely you do not mean that if
>you remove the POSTROUTING rule, you can still connect to a remote web server
>and have a Perl script tell you your source address ???
>
Yes, that is it! I removed every POSTROUTING rule, but I could still
connect to the web.
>
>Maybe you can explain a little more for me ?
>
Of cause. :-)
First I configured the Firewall, with a MASQUERADE rule, which shows the
www the external ip-address of the router/firewall.
I removed the statement from the configuration script and add the new role:
iptables -A POSTROUTING -t nat -s 192.168.0.0/16 -j SNAT --to-source
141.12.218.1
Afterwards I typed the flash command 'iptables -F'. Now ALL rules should
be removed, souldn't it?
I started my configuration script with the new rule (see above), but
nothing has changed.
First I tought, that iptables -F does not delete the POSTROUTING rules,
so I did it by hand:
iptables -D POSROUTING -t nat -s 192.168.0.0/16 -j MASQUERADE.
The same procedure, as discribed above and nothing has changed.
My plan is, that our network showes to the www just 1 ip-address, namely
141.12.218.99 and not the router-ip-address 141.12.129.9
Hope that is more information for you.
Thx
Uwe Eisner
>
>
>Antony.
>
>
[-- Attachment #2: Type: text/html, Size: 3694 bytes --]
next prev parent reply other threads:[~2002-06-06 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 13:27 SNAT does not work Uwe Eisner
2002-06-06 13:40 ` Antony Stone
2002-06-06 13:57 ` Antony Stone
2002-06-06 14:45 ` Uwe Eisner [this message]
2002-06-06 14:55 ` Antony Stone
2002-06-07 10:50 ` Uwe Eisner
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=3CFF7596.4090300@globit.com \
--to=uwe.eisner@globit.com \
--cc=Antony@Soft-Solutions.co.uk \
--cc=netfilter@lists.samba.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