maemo.org - Talk - slow connect to n800 with ssh?

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - slow connect to n800 with ssh? (https://talk.maemo.org/showthread.php?t=43696)

slow connect to n800 with ssh?

for a while now, trying to ssh into my n800 has been unbelievably slow; it may take 60 seconds for my commands to show up on my home computer terminal, basically making it unusable. i've purged and reinstalled both openssh and dropbear, and neither seems to make a difference. it used to be reasonably responsive. any ideas of where to start troubleshooting?

Re: slow connect to n800 with ssh?

Maybe it's trying to resolve the ip address and that's what takes a long time.

There's an option "UseDNS Specifies whether sshd should look up the remote host name and check that the resolved host name for the remote IP address maps back to the very same IP address. The default is ``yes''.

You could try setting it to "no" (in /etc/ssh/sshd_config)

Re: slow connect to n800 with ssh?

Quote:

Originally Posted by luca (Post 516617)

Maybe it's trying to resolve the ip address and that's what takes a long time.

Would this affect any packages being transmitted after the initial connection-handling?

I wish i could help, but apart from the usual tips without a clue, I fear I can't. I suspect you have already taken care of them, but just in case ;)

check top/process viewer for processes eating your cpu
see if your wireless network got overpowered on its channel or something (using wifiinfo?)
check if all network traffic has become slower (see 2.)
check if somehow the terminal is working that slow as well. I don't think this happens, ever (without 1.) ;)

My N800's power supply is busted atm, so I'm less help than I'd hope for, sorry...

Re: slow connect to n800 with ssh?

Quote:

Originally Posted by velox (Post 516646)

Would this affect any packages being transmitted after the initial connection-handling?

No, sorry, I just thought that the 60 seconds was referring to the initial connection. If it's a dns problem, once the connection is established it should work without delays (provided the network is working).

Re: slow connect to n800 with ssh?

no, it isn't just the initial connection. i actually tried this on a "spare" n800 that i had (it had a busted screen, but magically fixed itself). this one i haven't touched in a while, and used to be able to ssh without a problem. but now it has a slow connection as well. which tells me it's a problem on the client side. both computers that i'm using are running ubuntu karmic. i can ssh between them without a problem...
strange. this is really annoying.

Re: slow connect to n800 with ssh?

huh. just tried using putty on my wife's windows box--same problem. so now i'm back at square 1. i guess the only thing left is a network problem? i changed ISPs a while back and now have a verizon router--anything there that could do it? again, no problems with other computers on the network

Re: slow connect to n800 with ssh?

well, this is interesting. first ping is to my laptop. second is to the n800.

Code:

PING 192.168.1.7 (192.168.1.7) 56(84) bytes of data.

64 bytes from 192.168.1.7: icmp_seq=1 ttl=64 time=1.31 ms

64 bytes from 192.168.1.7: icmp_seq=2 ttl=64 time=1.30 ms

64 bytes from 192.168.1.7: icmp_seq=3 ttl=64 time=1.94 ms

64 bytes from 192.168.1.7: icmp_seq=4 ttl=64 time=1.29 ms

64 bytes from 192.168.1.7: icmp_seq=5 ttl=64 time=1.73 ms

^C

--- 192.168.1.7 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 4009ms

rtt min/avg/max/mdev = 1.299/1.517/1.940/0.270 ms

desktop:~$ ping 192.168.1.4

PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.

64 bytes from 192.168.1.4: icmp_seq=1 ttl=64 time=96.7 ms

64 bytes from 192.168.1.4: icmp_seq=5 ttl=64 time=1079 ms

64 bytes from 192.168.1.4: icmp_seq=2 ttl=64 time=4098 ms

64 bytes from 192.168.1.4: icmp_seq=3 ttl=64 time=3098 ms

64 bytes from 192.168.1.4: icmp_seq=6 ttl=64 time=85.1 ms

64 bytes from 192.168.1.4: icmp_seq=4 ttl=64 time=2101 ms

64 bytes from 192.168.1.4: icmp_seq=8 ttl=64 time=3087 ms

64 bytes from 192.168.1.4: icmp_seq=10 ttl=64 time=1082 ms

64 bytes from 192.168.1.4: icmp_seq=9 ttl=64 time=2098 ms

64 bytes from 192.168.1.4: icmp_seq=11 ttl=64 time=98.1 ms

64 bytes from 192.168.1.4: icmp_seq=7 ttl=64 time=4108 ms

^C

--- 192.168.1.4 ping statistics ---

11 packets transmitted, 11 received, 0% packet loss, time 10038ms

rtt min/avg/max/mdev = 85.184/1912.110/4108.043/1469.843 ms, pipe 5

any ideas?

Re: slow connect to n800 with ssh?

well, figured it out. turns out it was the power saving on the n800. if i turn the power saving off of the connection, all is well.