I have a issue where I cannot connect to my server because the firewall
only allows ports 80 and 443 out.
I previously ran SSH on port 443 to overcome this, but I have had to
implement a HTTPS solution for users who wanted secure access, so that
is now gone.
This system has DNS records for
Michael Thompson ha scritto:
I have a issue where I cannot connect to my server because the
firewall only allows ports 80 and 443 out.
I previously ran SSH on port 443 to overcome this, but I have had to
implement a HTTPS solution for users who wanted secure access, so that
is now gone.
This
Michael Thompson wrote:
I have a issue where I cannot connect to my server because the
firewall only allows ports 80 and 443 out.
I previously ran SSH on port 443 to overcome this, but I have had to
implement a HTTPS solution for users who wanted secure access, so that
is now gone.
I've had a
so can I use IPTables or similar to recognise if it is being connected
to via ssh.server.co.uk on port 443 and forward the traffic to port
22? If www.server.co.uk:443 is used apache gets the traffic? Or is
this (As I suspect) Impossible?
You can look at
Friday 11 February 2005 11:07 - Michael Thompson
[EMAIL PROTECTED] wrote:
I have a issue where I cannot connect to my server because the
firewall only allows ports 80 and 443 out.
I previously ran SSH on port 443 to overcome this, but I have had
to implement a HTTPS solution for users who
Michael Thompson wrote:
This system has DNS records for ssh.server.co.uk and www.server.co.uk,
so can I use IPTables or similar to recognise if it is being connected
to via ssh.server.co.uk on port 443 and forward the traffic to port 22?
If www.server.co.uk:443 is used apache gets the traffic?
James Hiscock wrote:
That looks fantastic! And it appears to support SSH...so you could try
to match against SSH, and redirect to the appropriate port if it does
match. Otherwise, assume it's web traffic...
I agree. I didn't do any research, but I was a little doubtful that
someone else hadn't
