What do the server logs tell you? /var/log/auth
It looks like you are getting into the remote server, but then it hangs on something. Denis -------------------------------------- sik vis paw kem, para bellum -------------------------------------- oderint dum metuant -------------------------------------- "Our Country won't go on forever, if we stay soft as we are now. There won't be any AMERICA because some foreign soldiery will invade us and take our women and breed a hardier race!" -LT. GEN. LEWIS "CHESTY" PULLER, USMC On Wed, Feb 11, 2009 at 4:41 PM, Martin Collins <mae...@mkcollins.org>wrote: > I've purged and reinstalled openssh but no change. I had the same > problem with dropbear too. > > Here's the debug from the server, from the point I try to connect: > > Connection from 192.168.0.7 port 56747 > debug1: Client protocol version 2.0; client software version > OpenSSH_4.7p1 Debian-12.maemo2 > debug1: match: OpenSSH_4.7p1 Debian-12.maemo2 pat OpenSSH* > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-3 > debug1: list_hostkey_types: ssh-rsa,ssh-dss > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug1: kex: client->server aes128-cbc hmac-md5 none > debug1: kex: server->client aes128-cbc hmac-md5 none > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received > debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent > debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT > debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug1: SSH2_MSG_NEWKEYS received > debug1: KEX done > debug1: userauth-request for user martin service ssh-connection method none > debug1: attempt 0 failures 0 > debug1: PAM: initializing for "martin" > debug1: PAM: setting PAM_RHOST to "192.168.0.7" > debug1: PAM: setting PAM_TTY to "ssh" > Failed none for martin from 192.168.0.7 port 56747 ssh2 > debug1: userauth-request for user martin service ssh-connection method > keyboard-interactive > debug1: attempt 1 failures 0 > debug1: keyboard-interactive devs > debug1: auth2_challenge: user=martin devs= > debug1: kbdint_alloc: devices 'pam' > debug1: auth2_challenge_start: trying authentication method 'pam' > Postponed keyboard-interactive for martin from 192.168.0.7 port 56747 ssh2 > debug1: do_pam_account: called > debug1: PAM: num PAM env strings 0 > Postponed keyboard-interactive/pam for martin from 192.168.0.7 port 56747 > ssh2 > debug1: do_pam_account: called > Accepted keyboard-interactive/pam for martin from 192.168.0.7 port 56747 > ssh2 > debug1: PAM: establishing credentials > debug1: Entering interactive session for SSH2. > debug1: server_init_dispatch_20 > debug1: server_input_channel_open: ctype session rchan 0 win 1048576 max > 16384 > debug1: input_session_request > debug1: channel 0: new [server-session] > debug1: session_new: session 0 > debug1: session_open: channel 0 > debug1: session_open: session 0: link with channel 0 > debug1: server_input_channel_open: confirm session > > <long wait here> > > Read error from remote host 192.168.0.7: Connection timed out > debug1: do_cleanup > debug1: PAM: cleanup > debug1: PAM: deleting credentials > debug1: PAM: closing session > > No clues for me there. It's connecting and authenticating but then > it's like both machines are waiting for something from the other. > I can connect to all machines from all machines (including my 770) > except the N800 so I don't think signal strength can be the problem. > I'm using IP addresses so DNS is not involved. > > Can anyone point me to a newer version of ssh for maemo? Maybe using > the same version at both ends will help. > > Martin > _______________________________________________ > maemo-users mailing list > maemo-users@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-users >
_______________________________________________ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
