From owner-freebsd-pf@freebsd.org Fri Apr 14 08:07:21 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 A9A01D3C03E for ; Fri, 14 Apr 2017 08:07:21 +0000 (UTC) (envelope-from maximos@als.nnov.ru) Received: from mx.als.nnov.ru (mx.als.nnov.ru [95.79.102.161]) (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 6B2281199 for ; Fri, 14 Apr 2017 08:07:20 +0000 (UTC) (envelope-from maximos@als.nnov.ru) Received: from [10.4.1.100] by mx.als.nnov.ru with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cywGC-00075m-Ot for freebsd-pf@freebsd.org; Fri, 14 Apr 2017 11:07:16 +0300 Subject: Re: pfctl -ss -a anchorName uinterruptable wait To: freebsd-pf@freebsd.org References: From: Max Message-ID: <88ec7695-e4c2-d4d0-d4aa-25733bd00c71@als.nnov.ru> Date: Fri, 14 Apr 2017 11:07:16 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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: Fri, 14 Apr 2017 08:07:21 -0000 After a quick look it seems that "show states" doesn't care about anchors (-a option). "pfctl -vss" should print anchor reference. Can you post a sample ruleset and FreeBSD version? 11.04.2017 12:45, Özkan KIRIK пишет: > Hello, > > I'm trying to get states belongs to an anchor. > but pfctl -ss -a anchorName command waits, Ctrl+C and Ctrl+Z doesnt work. > ps ax gives D+ state. and kill -9 doesnt work. > > When pfctl is in D+ state, I run pfctl -d. pf becomes disabled but the > process has D+ state still in same state. > > This is a repeatable problem. I think there is lock in kernel. > > Regards > _______________________________________________ > freebsd-pf@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pf > To unsubscribe, send any mail to "freebsd-pf-unsubscribe@freebsd.org"