From owner-freebsd-bugs@freebsd.org Tue Apr 27 09:48:03 2021 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 017E3627E42 for ; Tue, 27 Apr 2021 09:48:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4FTxlQ6NQVz3l4F for ; Tue, 27 Apr 2021 09:48:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id DAFC45E0019; Tue, 27 Apr 2021 09:48:02 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DAC546279FB for ; Tue, 27 Apr 2021 09:48:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FTxlQ5brQz3l6J for ; Tue, 27 Apr 2021 09:48:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B1876185EB for ; Tue, 27 Apr 2021 09:48:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 13R9m2Ra012619 for ; Tue, 27 Apr 2021 09:48:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 13R9m2Ni012618 for bugs@FreeBSD.org; Tue, 27 Apr 2021 09:48:02 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255438] ipfw: long running TCP connections get terminated Date: Tue, 27 Apr 2021 09:48:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: topical@gmx.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2021 09:48:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255438 Bug ID: 255438 Summary: ipfw: long running TCP connections get terminated Product: Base System Version: 13.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: topical@gmx.net Since 13.0-RELEASE long running idle TCP connections are silently terminated without notice. So, the endpoints encounter transmission timeouts later on = and bad things happen. It seems that net.inet.ip.fw.dyn_keepalive doesn't work anymore. Due to the nature of the problem (_long running_ and _idle_), it's hard to = pin down. Further, I have the following rule for egress packets: allow ip from any to any out keep-state So, if ipfw really forgets a connection, it gets recreated automatically if= the next packet is egress. A simple verification is to compare TCP connection known to tcp stack and states known to ipfw, e.g. # sockstat -6 | grep 636 postfix smtpd 96270 19 tcp6 XXX:15743 YYY:636 postfix smtpd 95918 19 tcp6 XXX:41957 YYY:636 root saslauthd 91056 8 tcp6 XXX:43828 YYY:636 root saslauthd 91055 8 tcp6 XXX:43830 YYY:636 root saslauthd 91054 8 tcp6 XXX:43826 YYY:636 root saslauthd 91053 8 tcp6 XXX:43825 YYY:636 root saslauthd 91052 8 tcp6 XXX:17216 YYY:636 versus: ipfw -d show | grep 636 61005 81 26938 (169s) STATE tcp XXX::13 41957 <-> YYY::10 636 :default 61005 58 19762 (113s) STATE tcp XXX::13 15743 <-> YYY::10 636 :default You see that all connections of saslauthd got lost.=20 Normally, ipfw should send keepalive packets some seconds before removing dynamic states, but when doing a packet capture, no keepalives of affected connections could be found. --=20 You are receiving this mail because: You are the assignee for the bug.=