stuck at ssh?
 

i get stuck here, any ideas?

i have changed port to 9999, to see if it works, same result as 22

by the way i have access to kloxo, this way i managed to allow port 9999 on server side for ssh

not a networking question. moved to Software.

What is the serverside saying in all of this? client output is deliberately less useful than the servers view of things. run sshd in foreground mode with debugging if need be, but i expect you'll see plenty there. I can't remember exactly when it occurs, but the most frequent issue causing a delay on ssh is reverse DNS lookups on the server.

oh sorry i was in doubt if it was networking question or not

server is 'as it was' a month ago, it recently stopped working, i dont have access to run ssh deamon in debuging mode

by the way, ssh terminal of kloxo says:
i could never use it...

and, kloxo access connection log shows dozens of ssh attempts from an ip i dont know who's it is, which seems not to be in my country at all, all failed, though i have tried maybe...6,or 7 times, so i guess it's not me being 'failed', my ip is just not shown in the log

i cant remember much, but the DNS issue you mention caused the whole thing to fail with a message, not like me being stuck? or just delays in running commands,
i'm totally unable to access ssh

figured it out, the evil ISP is blocking ssh
if changing my ISP is not an option, is there any workaround?
how can they manage to realize it's ssh? it's supposed to be encrypted? maybe i'm using ssl, how can they know?!?!

They dont need to know what the traffic is, in order to block ports..
They just block everything aside from the ones they want to allow, such as http/s, smtp, imap, pop, etc etc.

SSH is recognisable during the setup phase. For example, just telnet to am ssh port and you'll get a string back like "OpenSSH_4.5" from the server in plain text, before the security kicks in. You then have a standard recognisable handshake, not SSL, which has to occur to make the connection secure, which can be acted upon.

fuwaki: it's the case sometimes, but most of the times they use more complicated methods than just whitelisting some protocols

acid:yes exactly, it get's stuck during authentication!!!
is there any workaround?
maybe telling ssh daemon not to send anything at all, just to check my ip, i can enter my ip manually in a config file if necessary since i can use VPN, my ip is not static but always in this range: xx.yyy.zz.0/200
there MUST be something i can do, i thought about compiling my own ssh server+client from openssh source, but it's just too much, can somebody tell me which part of it i should be editing? plus i dont know much about sockets,networking,protocols, etc... , but i'll learn as much as i need to.

you know what i miss? freedom...

you could look at using tor to tunnel connectiosn over an http network, but I do find it very unliekly that the ISP is blocking SSH, unless you're in China or North Korea or something, that does seem quite excessive and very unusual.

dear acid, i live in someplace worse which i'm not gonna name, i'm afraid you're gonna abandon and hate me just by hearing the name
and yes, they have blocked it...
slowed down https and vpn to something near 5kb/s
tor is painfully slow
as (was) is ssh, but usable at least

just to know:i saw a picture showing an ssh packet, in the packet's header was port number, and also,the name ssh