Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 13 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 15 hrs ago -
Maemo repository (3)
to Community by torsen - 2 days, 6 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 4 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 10 hrs ago - more...
nola mike |
2010-02-07
, 22:42
|
|
Posts: 77 |
Thanked: 11 times |
Joined on May 2008
|
#1
|
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?
 |
|
2010-02-08
, 18:36
|
|
Posts: 1,137 |
Thanked: 402 times |
Joined on Sep 2007
@ Catalunya
|
#2
|
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)
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)
 |
|
2010-02-08
, 19:00
|
|
Posts: 394 |
Thanked: 1,341 times |
Joined on Dec 2009
|
#3
|
Originally Posted by luca
Would this affect any packages being transmitted after the initial connection-handling?
Maybe it's trying to resolve the ip address and that's what takes a long time.
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...
Last edited by velox; 2010-02-09 at 07:16. Reason: typo
|
|
2010-02-08
, 22:56
|
|
Posts: 1,137 |
Thanked: 402 times |
Joined on Sep 2007
@ Catalunya
|
#4
|
Originally Posted by velox
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).
Would this affect any packages being transmitted after the initial connection-handling?
|
|
2010-02-20
, 18:54
|
|
Posts: 77 |
Thanked: 11 times |
Joined on May 2008
|
#5
|
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.
strange. this is really annoying.
|
|
2010-02-20
, 19:06
|
|
Posts: 77 |
Thanked: 11 times |
Joined on May 2008
|
#6
|
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
|
|
2010-02-20
, 19:11
|
|
Posts: 77 |
Thanked: 11 times |
Joined on May 2008
|
#7
|
well, this is interesting. first ping is to my laptop. second is to the n800.
any ideas?
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
|
|
2010-02-21
, 03:59
|
|
Posts: 77 |
Thanked: 11 times |
Joined on May 2008
|
#8
|
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.