This is the README for proxyd.1.0.NIHS.bs.tar.gz [Download] [Browse] [Up]
17 Dev 1997 Author: Carl Harris (ceharris@vt.edu) Compiler: TjL <luomat@peak.org> Compiled by: cc -O2 -object -s \ -arch m68k -arch i386 -arch hppa -arch sparc \ proxyd.c -o proxyd This is a little daemon I felt was useful and was able to compile, so I thought I would make it available. I did not write this! I am just compiling and distributing. The source code had no restrictions on doing so. All I know as far as how to use it is what it says: usage: proxyd <proxy-port> <host> <service-name|port-number> Which means: proxyd localport-on-this-machine the-host-this-is-to port-or-name EXAMPLE: Say you have a machine named MYHOST want to bind your port #777 to the TELNET port of the host REMOTEHOST. Use: proxyd 777 REMOTEHOST telnet Then if you did 'telnet MYHOST 777' you would actually connect to the TELNET port of the host REMOTEHOST. As far as the 'service-name/port-number' goes: services can be referred to either by a number or a name. For example, NNTP requests are usually on port 119, so if you wanted to connect directly to a machine to do NNTP you could do either: telnet REMOTEHOST nntp or telnet REMOTEHOST 119 NOTE/WARNING: Make sure to use an unused port on your machine! If you are not sure, do this: nidump services . to see a listing of all the services known on your machine. This program does NOT always have to be run as root... Some ports are available even to regular users, it appears.
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.