If you're using 2.2 or earlier see note at end 
Plugdaemon  is a tool that is inspired by, but not based on, the plug-gw from Trusted Information Systems. It was originally a simpler wannabe, but the connection balancing code and other features makes it a lot more useful (it's also a feature-complete replacement for plug-gw).
Plugdaemon is released for any use, commercial or otherwise, so long as attribution is retained. If you do anything interesting with it, let me know. If you feel generous, tip me through Sourceforge.
The 1.2 code is missing some functionality, but is simpler code and will compile on K&R compilers for SunOS 4 and Xenix fans.
I'm going to completely redo the command line syntax in 3.0 (Real Soon Now), because it's gotten rather cruddy. Suggestions will be appreciated... also ideas for new features would be timely.
Documentation: (the version an option was added is indicated like this)
PLUG(1) PLUG(1) NAME plug -- Plug proxy daemon. SYNOPSIS plug -V plug [-nflkd...] [-i addr] [-p addr] [-t seconds] [-r seconds] [-a net[/bits]]... [-h addr:port] port addr[:port] [addr[:port]]... DESCRIPTION Plugdaemon acts as a "dumb proxy", forwarding a TCP/IP stream from a port on one host to a possibly different port on a separate host. It runs as a daemon to reduce latency in setting up a connection, and optionally logs every connection via syslog. OPTIONS -f Forces a given client address to continue to connect to the same host on subsequent attempts, for proxying HTTP connections so that subse- quent hits will be on the same mirror. -k Turns on SO_KEEPALIVE on the plug. You want to use this on frequent short term connections like HTTP requests where response time is more important than reliability on flakey links, and leave it off on long- term connections that may go a long time without transferring data. -l turns on connection logging. (2.5) -P pidfile (2.2) maintains a file that contains the process ID of the master plug dae- mon, followed by the process IDs of all the active children. This can be used for cleanup or monitoring. The file is deleted when the parent process exits. -d turns on debugging output and stops plug from logging errors to syslog. Errors in this mode are displayed on standard error. Additional -d options add more output. (implies -n) -i interface Bind the plug to the named interface, for use on dual-homed hosts. -p interface (2.0.2) Bind the source port of the proxied connection to the named interface, likewise. -a accept_rule (2.3) Accept connections that match the rule. Currently, the rule is an ip address and an optional subnet, e.g. -a 192.168.2.0/24 to accept connections from the Class-C subnet 192.168.2. All 4 octets of the address must be provided. If no rules are specified connections are allowed from any address. -t timeout (2.4) Timeout for forced connections, after no attempts in this period it will connect to a new (pseudo-)randomly selected server. The default is 1 hour. -o (2.4) Direct all connections to the first valid server instead of load- balancing. -r retry (2.4) Timeout for downed servers; if specified, then a dead server is retried after this many seconds. If not specified, then a dead server stays out of the pool until all have failed or plugdaemon is res- tarted, then all are retried again. -V (1.1.3) Display version and exit. -n (2.5) Don't detach, run in the foreground. -S filename (2.5) log sessions to the named file. If the file is "-", log to standard output (which implies -n). -h address:port (2.5) Use HTTPS proxy at address:port to make connections, rather than connecting directly. EXAMPLES To proxy an NNTP connection through a firewall to a host at 10.0.3.15: plug -i 192.168.0.14 119 10.0.3.15 BUGS Plugdaemon only accepts numeric IP addresses and services. The syntax is rather clumsy, but I'm deferring cleanup until version 3.0. The main thing I'd like to do is get rid of the -i option and allow any of the following forms for the source: port, :port, *:port, address:port, or source/interface (to specify the outgoing interface). As well as regularise the various flags other people have added that I've kept to keep from breaking their scripts. SECURITY FEATURES Plugdaemon only accepts numeric IP addresses and services. I don't call gethostbyname anywhere to keep someone from managing to fake it out by spoofing the firewall's DNS lookups, but I think that should be an option so 3.0 will probably disable it unless selected at compile time. LICENSE Plugdaemon is released under a "Berkeley" style license. See the file LICENSE for details. AUTHOR Peter da Silva.
1) There is a bug in 2.2 and earlier versions of 2.x that can cause a corrupted internal process table under extremely high load conditions, leading to a process table leak and a possible denial of service.
2) By the way, that's not Invisible Chuck. The invisible daemon is something I started doodling back in the mid '70s when I was in high school, before I'd ever heard of UNIX.