John Krivitsky wrote:
>
> I am trying to route in-coming connections TO some of the private IPs
> on the internal masqueraded network. For example, an in-coming
> connection on port 25 may route to 10.25.25.33 on port 8123. In
> other words, to allow some of the machines to act as servers for
> certain services.
>
> jk
The situation you are describing is called "port forwarding"
http://www.linuxdoc.org/HOWTO/IPCHAINS-HOWTO.html says:
>
> The simplest approach is to run a "redirector", which is a poor-man's
> proxy which waits for a connection on a given port, and then open a
> connection a fixed internal
> host and port, and copies data between the two connections. An example of
> this is the "redir" program. From the Internet point of view, the
> connection is made to your firewall. From your internal server's point
> of view, the connection is made from the internal interface of the
> firewall to the server.
I have had satisfactory results using the "netpipes" package as well
> Another approach (which requires a 2.0 kernel patched for ipportfw,
> or a 2.1 or later kernel) is to use port forwarding in the kernel.
> This does the same job as "redir" in a different way: the kernel
> rewrites packets as they pass through, changing their destination
> address and ports to point them at an internal host and port. From the
> Internet's point of view, the connection is made to your firewall.
> From your internal server's point of view, a direct connection is made
> from the Internet host to the server.
________________________________________________________________________
David Nicol 816.235.1187 [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
