From owner-freebsd-questions@FreeBSD.ORG Wed Mar 5 18:22:28 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 701DF26D for ; Wed, 5 Mar 2014 18:22:28 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3A87DBB7 for ; Wed, 5 Mar 2014 18:22:28 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.7/8.14.7) with ESMTP id s25IMRjG085976; Wed, 5 Mar 2014 13:22:28 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <53176B62.8080202@sentex.net> Date: Wed, 05 Mar 2014 13:22:26 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Brett Glass , questions@freebsd.org Subject: Re: SSH Protocol 2 between 9.x and 10.0 fails References: <201403050528.WAA21620@mail.lariat.net> <53174F3B.1080403@sentex.net> <201403051753.KAA27860@mail.lariat.net> In-Reply-To: <201403051753.KAA27860@mail.lariat.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.74 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2014 18:22:28 -0000 On 3/5/2014 12:51 PM, Brett Glass wrote: > At 09:22 AM 3/5/2014, Mike Tancsa wrote: > >> Are you sure its not something else ? Do you have pf on the remote box >> ? perhaps a missing keep state rule ? P-MTU issue ? Try a tcpdump to >> see if packets are being missed or re-transmitted ? > > Did try tcpdump. TCP session looked OK; handshake just stopped. Start sshd with -dddd on the server side and compare what a good session looks like and what the failing one looks like ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/