Jun 6 2010, 04:14 PM
QUOTE(socratesman @ Jun 6 2010, 03:41 PM)
Not sure what's going on, seems TM put a temporary stop-gap measure in place by blocking connections on port 22(SSH) heading for 110.159.* IPs.
I had someone enable remote SSH on his DIR-615.
Using the default port 22, I wasn't able to connect from my Streamyx to his Unifi. (connection closed at remote end)
Then I asked him to change the SSH port to a random 5-digit number, and voila I managed to login to router using putty.
Like rizvan said, I was able to use his connection as a SOCKS proxy (ssh dynamic forwarding).
By blocking ports, won't really help much, tho it probably will cause some troubles for users who ssh alot to their servers. Who knows, some of the unifi users does host a personal web server?I had someone enable remote SSH on his DIR-615.
Using the default port 22, I wasn't able to connect from my Streamyx to his Unifi. (connection closed at remote end)
Then I asked him to change the SSH port to a random 5-digit number, and voila I managed to login to router using putty.
Like rizvan said, I was able to use his connection as a SOCKS proxy (ssh dynamic forwarding).
Thanks for the headup, riz, will keep that in mind =)
Quote
1.0287sec
0.62
7 queries
GZIP Disabled