|
With NAT your private machines on the 192.168.1.X network would each be translated to one of the public addresses. All of this happens through the public side ether address of your Linux NAT system. So on the fly, inbound packets get translated over from a public address to a private address and routed to the assigned machine. Outbound packets are translated on the way out and the effect is as though you actually connected those machines out on the public side. However, they are still on the private net and protected by the Linux Firewall capability as well as your ability to limit the ports they can send and receive packets on. (It is frigging magic man!) Unless you get into Michaels Virtual Server stuff you will need a specific public IP for each private IP you are going to translate. This is a LOT different from Proxy where all the private nodes come through one box and appear out on the public net as all from the same machine. Hope this helps. if not, give us a bit more insight into what you want to accomplish. Bill Harris |
Messages
Outline:
problem with ipnatadm compiling under 2.0.33 by Roberto Favaro, 12/31/97
I don't know... as usual ;-) by Michael Hasenstein, 12/31/97
(correction of message text) by Michael Hasenstein, 1/13/98
Compiling IP NAT in RedHat 5.1 distribution by Francis Baud, 9/23/98
Compiling IP NAT in RedHat 5.1 distribution by Francis Baud, 9/23/98
patch by Michael J. Maravillo, 1/13/98
here is my solution, hope it works for you too by Jim M. Poon, 2/01/98
ipnatadm Binary for glibc-2 by Michael Hasenstein, 2/07/98
I can use your binary but still cannot compile! by Joseph Kwok, 5/01/98
(answer to ping-problem) by Michael Hasenstein, 5/04/98
But what about aliasing? by Ennio Porro, 1/01/98
Read Michael Hasenstein's HTML DOC by Bill Harris, 1/04/98
My problem by Ennio Porro, 1/06/98
Not implemented (yet?) by Michael Hasenstein, 1/09/98
NAT and ICA by jim, 1/30/98