Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm looking to move ssh off port 22, and had tried out sslh;

sslh ssl/ssh multiplexer - accepts HTTPS, SSH, OpenVPN, tinc and XMPP connections on the same port. This makes it possible to connect to any of these servers on port 443 (e.g. from inside a corporate firewall, which almost never block port 443) while still serving HTTPS on that port.

However those services then see traffic originate from, instead of the external host making the request - for authentication/logging/identification purposes I've had to disable sslh.

Recommendations for alternative options?

Should I investigate using stunnel to proxy ssh through nginx?

share|improve this question
If you are using a tunnel or proxy then the source IP address will always be the endpoint rather than the origin. It has be this way for reply packets to get sent to the endpoint rather than the origin. – Paul Jan 18 '12 at 2:15
yes but with proxying you can add headers, to trace the source ip – Thermionix Jan 18 '12 at 2:56
For web services certainly. What about vpn and ssh and tinc and xmpp? – Paul Jan 18 '12 at 3:12
I was curious if this was possible on a lower layer than the Application Layer – Thermionix Jan 23 '12 at 0:25

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.