Hi, I once saw an example of port forwarding using netcat and inetd, i think it involved setting up a listening netcat as the application, using inetd to bind it to a specific port and then forwarding the connection onwards to the ip and/or port where you want it to go, something like this:
service geofwd { flags = REUSE socket_type = stream wait = no user = root server = /usr/bin/nc server_args = 192.168.124.38 1005 log_on_failure += USERID } not sure if this is what you want :-) Craig >Hello, > >ML>If you absolutely need to be in port 80, either setup a simple >ML>lightweight apache on port 80 as a reverse proxy (see the mod_perl >ML>guide) or, even simpler, do some port forwarding from port 80 to your >ML>high port of choice. > >Has anybody had very good experiences using a simple port forwarder in a >production setup? We had a somewhat bad experience with using portfwd >under Solaris (images and other binary data got randomly corrupted, and we >never got around to figuring out why), and I'm wondering what others use >instead. It seems like the port forwarder involved would also be important >performance wise. > >The applications I am typically interested in are forwarding ports on the >same interface (like the port 80 example here) as well as between >interfaces (or between external interfaces and loopback). > >Humbly, > >Andrew > >---------------------------------------------------------------------- >Andrew Ho http://www.tellme.com/ [EMAIL PROTECTED] >Engineer 1-800-555-TELL Voice 650-930-9062 >Tellme Networks, Inc. Fax 650-930-9101 >----------------------------------------------------------------------