From owner-freebsd-current@freebsd.org Fri May 20 14:08:39 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A6B6B42292 for ; Fri, 20 May 2016 14:08:39 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D0D71143B for ; Fri, 20 May 2016 14:08:38 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1b3l6S-001M5R-Dq>; Fri, 20 May 2016 16:08:36 +0200 Received: from x4e3482fd.dyn.telefonica.de ([78.52.130.253] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (envelope-from ) id <1b3l6S-002F9v-4Q>; Fri, 20 May 2016 16:08:36 +0200 Date: Fri, 20 May 2016 16:10:35 +0200 From: "O. Hartmann" To: Jan Bramkamp Cc: freebsd-current@freebsd.org Subject: Re: CURRENT: ipfw: problems with timeouts and worse network performance Message-ID: <20160520161035.52118058.ohartman@zedat.fu-berlin.de> In-Reply-To: <38888426-4d91-56ed-9ab3-0d516b0b8d46@rlwinm.de> References: <20160520140152.3ab6fe44@hermann> <20160520125401.GC2371@vzakharov> <38888426-4d91-56ed-9ab3-0d516b0b8d46@rlwinm.de> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/i1RG==SKrtB/deGYB5TrV4y"; protocol="application/pgp-signature" X-Originating-IP: 78.52.130.253 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Fri, 20 May 2016 14:08:39 -0000 --Sig_/i1RG==SKrtB/deGYB5TrV4y Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Fri, 20 May 2016 15:28:35 +0200 Jan Bramkamp schrieb: > On 20/05/16 14:54, Vladimir Zakharov wrote: > > Hello > > > > On Fri, May 20, 2016, O. Hartmann wrote: =20 > >> I reported earlier about broken pipes in ssh sessions to remote hosts, > >> which occur on an erratic basis. i'm investigating this problem now and > >> it seems that it is also ipfw-related, but I'm not sure. This problem > >> is present since a couple of weeks now. =20 > > > > Maybe this could help... > > > > I've also experienced problems with broken pipes in ssh sessions some > > time ago. Setting in sysctl.conf > > > > net.inet.ip.fw.dyn_ack_lifetime=3D3600 > > > > fixed problem for me. I didn't experiment with the value though. So, > > possibly, changing default value (300s) to 1 hour is overkill :). =20 >=20 > By default the OpenSSH SSH client is configured to use TCP keepalives.=20 > Those should produce enough packets at a short enough interval to keep=20 > the dynamic IPFW state established. >=20 > Does your traffic pass through libalias? YES and NO. My private setup at home/home office uses NAT/libalias (kernel = NAT), but at work and department its straight forward. --Sig_/i1RG==SKrtB/deGYB5TrV4y Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXPxrbAAoJEOgBcD7A/5N8pXoIAJdM+SyjaKjTgM2BGg4l2Ey8 60LAoFCGz3DMDMeZTo4fAzbgcLydRHa4csdF0PJ+thPZKv8jxeO7ULSm59lVFfSx jAPDQQfNDTX7krOzTFSi8c6V6SROIxMQuEI07wty0SGqglDq60OUGMNtKTkfnuwC QogbbI2gYUpxEgzGxnWw9oWR5SnI6zcHc8v6gLrhqgJ6V7ULXElrVR3cbBFinnY7 txqAJeClgAzdLakC8hzW/TPPQ6EkK6ij2nap+Z0wx6MgcRNypfrIhlUgSY4lj2fj iNJy/+DoEtyWHyCh5lT2VHFx024bvknBS7JC0rvRLt4sNDgDa6N5lVz08dUMVI8= =K1kB -----END PGP SIGNATURE----- --Sig_/i1RG==SKrtB/deGYB5TrV4y--