We use port redirection/proxy often on our platforms. In the production setup, separate (Linux-based) servers take care of this, but for our development and testing environment, we need port redirection for Windows system. I generally use 2 command-line packages:
Typical use of stunnel:
stunnel -d smtps -r localhost:smtp
Typical use of rinetd:
server:8080 side effects
![]()
Meanwhile on the other screen: Claire Forlani in ‘Meet Joe Black’. Mediocre movie, lousy acting by most of the crew, but mmmmm, that face.
If you're new here, you may want to subscribe to my RSS feed or receive updates via email. Thanks for visiting!
Related posts:
- Fancy redirection on IIS 5 The task seemed easy enough: set up a new web...
- No life without CURLs If you’re a web server administrator – as I am...
- Stuff to install on a new Windows PC That is, the stuff I install on a new Windows...
- Converge already! (Struggling with WLBS) I hate when things don’t go my way. One server...




Port redirection is nifty but I have a very low level requirement and I am not sure if it can be fullfilled with the packages you mention.
When we teach students in labs about DHCP they always end up causing havoc with the other labs – unless they are behind a firewall. I have the idea of a port redirection, for the student client and server machines, that would cause the DHCP that they are playing with to take place over a non-standard port.
Do you have any thoughts?
Claire Forlani … Ding Dong