From owner-freebsd-current@FreeBSD.ORG Sat Jan 31 08:58:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EEA416A4CE; Sat, 31 Jan 2004 08:58:32 -0800 (PST) Received: from sarevok.webteckies.org (node123e0.a2000.nl [24.132.35.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id C404343D2F; Sat, 31 Jan 2004 08:58:24 -0800 (PST) (envelope-from mdev@sarevok.webteckies.org) Received: by sarevok.webteckies.org (Postfix, from userid 100) id 2CD1AB82A; Sat, 31 Jan 2004 17:58:21 +0100 (CET) From: Melvyn Sopacua Organization: WebTeckies.org To: current@FreeBSD.org Date: Sat, 31 Jan 2004 17:58:20 +0100 User-Agent: KMail/1.5.94 References: <20040130170931.GB5100@ack.Berkeley.EDU> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_t69GAJfXyzCi21v"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200401311758.21034.freebsd-current@webteckies.org> cc: Randy Bush cc: Mike Hunter cc: FreeBSD Current Subject: Re: ssh hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2004 16:58:32 -0000 --Boundary-02=_t69GAJfXyzCi21v Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 31 January 2004 05:38, Randy Bush wrote: > > I experienced this *same* hang from a 5.2-RELEASE (Thu Jan 22 04:51:45 > > PST 2004) box acting as the ssh server. I experienced the problem with > > clients from FBSD 5.1, redhat linux (?) and knoppix linux 3.3. The hang > > was at the exact same spot when running "ssh -v -v -v". > > > > Sorry to make the picture more confusing :| > > you want confusion? i give you confusion. > > today, with all configurations the same, but on a different wireless > provider here in NL, the problem goes away. Does looking up the hostname experience the same and do you have inet6 in y= our=20 kernel? It could be, that the nameserver of your provider has a broken loadbalancer= ,=20 which doesn't know what to do with ipv6 lookups. =2D-=20 Melvyn =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =46reeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Ja= n 28=20 18:01:18 CET 2004 =20 root@sarevok.lan.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG = =20 i386 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D --Boundary-02=_t69GAJfXyzCi21v Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAG96tOv9JNmfFN5URAvMBAJ993uN/763aRhQvDieTiAQw8J7lswCgs55y jn3u7lvFNPacBjbYLcCGGL0= =LCmx -----END PGP SIGNATURE----- --Boundary-02=_t69GAJfXyzCi21v--