$arr_19 ), array( 3, false, $arr_20, $arr_24 ), array( 2, false, "\" />", $arr_25 ) ) ); ?> $arr_27 ), array( 3, false, $arr_28, $arr_30 ), array( 2, false, "\" />\n\n", $arr_31 ) ) ); ?> array( 2, false, false, $arr_9 ), array( 4, $arr_10, "if", $arr_245, $arr_248 ), array( 2, false, "\n", $arr_249 ) ) ); ?> rr_466 ), array( 4, $arr_467, "if", $arr_482, $arr_484 ), array( 2, false, "\n", $arr_485 ) ) ); ?> Charly's Column » Linux Magazine
 

The Sysadmin’s Daily Grind: Portfwd

Charly's Column

Author(s):

Incoming TCP connections do not always end up where they are supposed to. A freely configurable redirector points digital debris in the direction of a new and better place.

Just a little while back we discussed Rinetd [1], a TCP redirector. Rinetd is lean, reliable, and easy to configure; on the downside, it lacks some advanced features. This month I’ll examine Portfwd, a tool that includes some of those features missing from Rinetd. Portfwd (Port Forwarding Daemon, [2]) takes the form of a 116K tarball, which you can build and install in the normal way: ./configure; make; make install or almost. The all-important binary went into hiding in the src directory after I typed make install. A symlink (ln -s /usr/local/portfwd-0.27/src/portfwd/usr/bin/portfwd) took care of that.

Read full article as PDF »

Charly_Column.pdf (112.92 kB)
comments powered by Disqus

Visit Our Shop

Trial Subscription

Digital Subscription

Subscribe

Direct Download

Read full article as PDF »

Charly_Column.pdf (112.92 kB)

Tag Cloud

Bruce Byfield Gnome KDE Kernel Linux Linux Pro Magazine Open Source Projects Red Hat Ubuntu events foss free software google

News