From owner-freebsd-pf@freebsd.org Tue Sep 26 12:05:29 2017 Return-Path: Delivered-To: freebsd-pf@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 804CEE08AC7 for ; Tue, 26 Sep 2017 12:05:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 6935D3E96 for ; Tue, 26 Sep 2017 12:05:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v8QC5Q78063027 for ; Tue, 26 Sep 2017 12:05:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-pf@FreeBSD.org Subject: [Bug 222126] pf is not clearing expired states Date: Tue, 26 Sep 2017 12:05:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hlh@restart.be X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-pf@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 12:05:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222126 --- Comment #22 from hlh@restart.be --- The problem crop up: [root@norquay ~]# pfctl -si Status: Enabled for 1 days 08:09:42 Debug: Urgent Interface Stats for ng0 IPv4 IPv6 Bytes In 3355637698 0 Bytes Out 236586554 0 Packets In Passed 2587532 0 Blocked 3290 0 Packets Out Passed 2395320 0 Blocked 109 0 State Table Total Rate current entries 31=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 searches 10992548 94.9/s inserts 77585 0.7/s removals 77052 0.7/s Counters match 86805 0.7/s bad-offset 0 0.0/s fragment 0 0.0/s short 0 0.0/s normalize 0 0.0/s memory 0 0.0/s bad-timestamp 0 0.0/s congestion 0 0.0/s ip-option 0 0.0/s proto-cksum 0 0.0/s state-mismatch 9 0.0/s state-insert 2 0.0/s state-limit 0 0.0/s src-limit 8 0.0/s synproxy 105 0.0/s map-failed 0 0.0/s [root@norquay ~]# pfctl -ss|wc -l 533 [root@norquay ~]# procstat -kk 7 PID TID COMM TDNAME KSTACK=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 7 100084 pf purge - mi_switch+0x118 sleepq_timedwait+0x40 _sleep+0x268 pf_purge_thread+0xec fork_exit+0x94=20 [root@norquay dtrace]# ./pf.dtrace=20 dtrace: script './pf.dtrace' matched 4 probes dtrace: buffer size lowered to 2m after: [root@norquay ~]# echo "set timeout interval 5" | pfctl -mf - CPU ID FUNCTION:NAME 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 3 2257 pf_purge_expired_states:entry=20 3 2258 pf_purge_expired_states:return=20 3 2258 pf_purge_expired_states:return=20 3 2257 pf_purge_expired_states:entry=20 3 2258 pf_purge_expired_states:return=20 3 2258 pf_purge_expired_states:return=20 3 2257 pf_purge_expired_states:entry=20 3 2258 pf_purge_expired_states:return=20 3 2258 pf_purge_expired_states:return=20 3 2257 pf_purge_expired_states:entry=20 3 2258 pf_purge_expired_states:return=20 3 2258 pf_purge_expired_states:return=20 3 2257 pf_purge_expired_states:entry=20 3 2258 pf_purge_expired_states:return=20 3 2258 pf_purge_expired_states:return=20 3 2258 pf_purge_expired_states:return=20 3 2257 pf_purge_expired_states:entry=20 3 2258 pf_purge_expired_states:return=20 3 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 1 2258 pf_purge_expired_states:return=20 1 2258 pf_purge_expired_states:return=20 1 2257 pf_purge_expired_states:entry=20 .... [root@norquay ~]# echo "set timeout interval 10" | pfctl -mf - And then no new state are created! [root@norquay ~]# nohup service pf restart resume the normal work of pf. --=20 You are receiving this mail because: You are the assignee for the bug.=