Confirmed on Feisty and Gutsy. Dapper works great.
This is NOT an OpenSSH problem. See below. I have played with MTU on the NICs and NAT router (1500 on all). Dapper's ssh works fine no matter what MTU is set on its NIC or the (same) router. Here's the -vv from a Gutsy machine: OpenSSH_4.6p1 Debian-5build1, OpenSSL 0.9.8e 23 Feb 2007 debug1: Reading configuration data /home/XXXX/.ssh/config debug1: Applying options for fs-dev debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to work-dev [XXX.XXX.XXX.XXX] port XXXXX. debug1: Connection established. debug2: key_type_from_name: unknown key type '-----BEGIN' debug2: key_type_from_name: unknown key type '-----END' debug1: identity file /home/XXXX/.ssh/identity type -1 debug1: identity file /home/XXXX/.ssh/id_rsa type -1 debug2: key_type_from_name: unknown key type '-----BEGIN' debug2: key_type_from_name: unknown key type '-----END' debug1: identity file /home/XXXX/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_3.7.1p2 debug1: match: OpenSSH_3.7.1p2 pat OpenSSH_3.* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.6p1 Debian-5build1 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent It will hang there forever. I built 4.3p2 on Gutsy (same as Dapper). Same problem as 4.6p1. This eliminates OpenSSH... OpenSSL? Libc? Kernel? Fix it and I promise I will name my next child whatever you say. -- ssh client does not connect to ssh servers https://bugs.launchpad.net/bugs/120176 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
