a nice feature to future versions would be rinetd daemon…
i copy from somewhere in the internet:
Rinetd is a simple, but effective tool for redirecting TCP connections.
“Rinetd is a single-process server which handles any number of connections to the address/port pairs specified in the configuration file etc/rinetd.conf. Since rinetd runs as a single process using nonblocking I/O, it is able to redirect a large number of connections without putting much additional load to the machine.”
rinetd is pretty much unecessary because of the nat and filtering features in MT. Furthermore, rinetd is less desirable because the destination server thinks everything is coming from the rinetd box instead of the originating host, preventing access control by IP at the destination server. I use it on a SuSe linux box and it works fine with this limitation.
Sorry to warm up such an old tread, but I have to object:
rinetd’s unique feature for several applications is, that it DOES open a new TCP connection. If you have a local (NATed) device which has no default gateway or some gateway, that does not point back to your router (NAT engine), you may not reach it with portforwarding. your packets are indeed transmitted to the device, but its answers are being lost (or not reNATed back). rinetd is THE simple solution for that.
off course it has downsides. but which technique doesn’t?
