At 11:11 PM +0100 1/23/09, Bill Eldridge wrote:
Tom Shaw wrote:
At 7:46 PM +0100 1/23/09, Bill Eldridge wrote:
Michael Renner wrote:
On Friday 23 January 2009, Bill Eldridge wrote:
I was interested in whether there's a simple way to have stunnel redirect traffic from a public Web browser/port to my home Web browser behind my DSL firewall (no ports opened/forwarded for incoming connections on the router, only outgoing-initiated)
Moin,
it is not clear to what you want to do. From a public web browser to your home web browser?
Can you clarify your setup?
As an example if I run Apache on my home machine, I'd like it to start the tunnel when I turn it on, have it automatically set up stunnel to a Linux box I have on the public net, and have anything to port 8090 on the Linux box get passed to my home machine 8080.
Easier to use ssh to port forward in this instance, IMHO. But why? Seems like just port mapping on the NAT router would work just as well and with no different effect on security.
Because I won't be able to add ssh or access the router in a number of cases where I need this, but I believe I'll have access to stunnel in many/most cases. Necessity is the mother of invention.
Maybe I am all wet but is seems to me that a) if you can put stunnel at both ends you can put ssh at both ends - saying that you would have access to stunnel and not ssh doesn't make any sense, b) why wouldn't you have access to your own router?
Tom