From owner-freebsd-net@freebsd.org Thu Nov 8 22:10:32 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F0061108AC8 for ; Thu, 8 Nov 2018 22:10:32 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 682CA7042E for ; Thu, 8 Nov 2018 22:10:31 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 0495C8D4A241; Thu, 8 Nov 2018 22:10:28 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 1C533D1F872; Thu, 8 Nov 2018 22:10:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 81doasFyiiHY; Thu, 8 Nov 2018 22:10:26 +0000 (UTC) Received: from [192.168.1.88] (fresh-ayiya.sbone.de [IPv6:fde9:577b:c1a9:f001::2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 89170D1F851; Thu, 8 Nov 2018 22:10:26 +0000 (UTC) From: "Bjoern A. Zeeb" To: Yuri Cc: freebsd-net@freebsd.org Subject: Re: Long-lived connections over WiFi get stuck Date: Thu, 08 Nov 2018 22:10:34 +0000 X-Mailer: MailMate (2.0BETAr6126) Message-ID: <4CCFF35B-5F09-41AC-A96E-8A9CD294C0BA@lists.zabbadoz.net> In-Reply-To: <8825ef4b-575a-f20b-3282-0bbeabe83bd9@rawbw.com> References: <8825ef4b-575a-f20b-3282-0bbeabe83bd9@rawbw.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 682CA7042E X-Spamd-Result: default: False [-3.47 / 200.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zabbadoz.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: cross.sbone.de]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.57)[-0.569,0]; IP_SCORE(-0.59)[asn: 24940(-2.95), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2018 22:10:32 -0000 On 8 Nov 2018, at 19:14, Yuri wrote: > I have the problem that vnc-over-ssh connection from the laptop on > WiFi gets stuck regularly, while the local browser on the laptop still > works fine. > > Eventually vnc-over-ssh either disconnects, or can be revived by > pulling the WiFi card out and putting it back in. > > The only difference between the browser and vnc-over-ssh is that > browser connections are supposedly shorter, and can supposedly get > reset by the browser when they aren't responsive, while ssh > connections are long-lived and probably intense because vnc regularly > needs to transfer large screen portions, and ssh doesn't reconnect > when stuck. > > > What could be a problem with long connections getting stuck? How can > this be troubleshooted? My initial thought was MTU issues. You might want to run tcpdump/wireshark and see what’s going on. Wireshark might help you with the analysis. /bz