Re: DMZ to DMT through ROUTER problem !

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 20 May 2004 16:45, Antony Stone wrote:
> Yes, but that destination address has already been changed by your
> PREROUTING rule, and is now 192.168.0.0/24 - that's the whole point.   If
> the destination address had not been changed (ie: if the client had
> contacted the server's real IP address instead of a pretend one), you
> wouldn't need to change the source address as well.

As you say, the problem was when a server with 192.168.0.x, passing through 
192.168.0.1 (that is the ROUTER), and try to connect to 151.8.47.x (the real 
server's PUBLIC IP). This is the desidered flow:

192.168.0.2-->151.8.47.A-->192.168.0.3

So i think that i need additiona rules to MASQ/DNAT connection to 151.8.47.x !

Oz

- -- 
There is a theory which states that if ever anyone discovers exactly what
the Universe is for and why it is here, it will instantly disappear and be
replaced by something even more bizarre and inexplicable.  There is another
theory which states that this has already happened.
		-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFArMexYuBSFbgkEysRAgoOAKCxjUX/lXCX30GUUaCkQTSHaklXXQCdHS6A
faOLbQvIfdm6e7coMhWm/9w=
=ddMI
-----END PGP SIGNATURE-----




[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux