-
"TCP Wrapper and SSH Port Forwarding for 1000 Alex" -RoadClosed
There's your fix...
If it is using some form of filtering higher up in the OSI model, your going to have to "wrap" the SSH negotiations in some form that is permitted thru the router. At this point if your still wanting to continue, you'll go grab the help wanted section of the newspaper, and then probe the border perimeter to determine it's characteristics ( Supported protocols, allowed ports, QOS, ...ect)
It probally would be a better idea to just ask the admin, though....
-
Thanks for the ideas everybody.
I'll post back with some results shortly.
Regards
-
i cannot believe noone mentioned netcat...
-
Quote:
Originally posted here by unhappy
i cannot believe noone mentioned netcat...
Quote:
Originally posted here by zENGER
22 is SSH...
What you can do, is find a port that is open. Then setup a relay somewhere that listens on that port and forwards to port 22 on that host. Netcat can be used to do this.
This does require a host to do it on though.
-
VPN into home and then SSH from there??? ORRRRRR Remote Destkop into home then VPN from home...
Just a couple of thoughts
-
Quote:
Originally posted here by Spyrus
VPN into home and then SSH from there??? ORRRRRR Remote Destkop into home then VPN from home...
Just a couple of thoughts
Nice ideas! :D What's a big deal! :rolleyes:
If they block your 22 port, why they let other port open?
-
Some ports are required for everyday things. Examples are port 80 for web servers, port 25 for smtp or ports 20 and 21 for ftp. If you block these ports then you lose the service that uses that port.
