From nobody@FreeBSD.org  Fri Apr 21 19:53:07 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6801D16A404
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 21 Apr 2006 19:53:07 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0C7D043D45
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 21 Apr 2006 19:53:07 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k3LJr60i089080
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 21 Apr 2006 19:53:06 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k3LJr655089079;
	Fri, 21 Apr 2006 19:53:06 GMT
	(envelope-from nobody)
Message-Id: <200604211953.k3LJr655089079@www.freebsd.org>
Date: Fri, 21 Apr 2006 19:53:06 GMT
From: "James L. Lauser" <james@jlauser.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: pfctl -k non-functional
X-Send-Pr-Version: www-2.3

>Number:         96150
>Category:       bin
>Synopsis:       pfctl(8) -k non-functional
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-pf
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr 21 20:00:28 GMT 2006
>Closed-Date:    Thu Jul 27 11:57:39 GMT 2006
>Last-Modified:  Thu Jul 27 11:57:39 GMT 2006
>Originator:     James L. Lauser
>Release:        6.1-RC/sparc64
>Organization:
>Environment:
FreeBSD Pancake.jlauser.net 6.1-RC FreeBSD 6.1-RC #2: Sun Apr 16 19:29:20 EDT 2006     root@Pancake.jlauser.net:/usr/obj/usr/src/sys/GENERIC  sparc64
>Description:
The -k (kill) functionality of pfctl does not appear to work correctly (or at all).  As root, if I run "pfctl -k 1.2.3.4", regardless of how many states are curretnly open from that host, all it returns is "killed 0 states from 1 destination and 0 hosts" and does not affect the state table.

I don't have another FreeBSD machine running pf to verify against, but running this on OpenBSD 3.6/i386 does work.
>How-To-Repeat:
Run pfctl -k <host> as root.
>Fix:

>Release-Note:
>Audit-Trail:

From: James Lauser <james@jlauser.net>
To: bug-followup@FreeBSD.org, James Lauser <james@jlauser.net>
Cc:  
Subject: Re: misc/96150: pfctl -k non-functional
Date: Fri, 21 Apr 2006 18:06:36 -0400

 I have verified this with a friend.  His system is running 6.0- 
 release on i386, and exhibits the same behavior.
 
 
 --  James L. Lauser
      james@jlauser.net
 
 
 

From: Cheng-Lung Sung <clsung@tw.FreeBSD.org>
To: james@jlauser.net (James Lauser), bug-followup@FreeBSD.org
Cc:  
Subject: Re: misc/96150: pfctl -k non-functional
Date: Sat, 22 Apr 2006 11:08:06 +0800 (CST)

 I just tested on  6.1-PRE on i386, and I don't have such problem.
 
 % sudo pfctl -k 127.0.1.80
 killed 33 states from 1 sources and 0 destinations
 
 Can you provide more information about that? 
 
 Thanks
 You've <e2bl91$93h$1@FreeBSD.csie.nctu.edu.tw> mentioned about:
 > The following reply was made to PR misc/96150; it has been noted by GNATS.
 > 
 > From: James Lauser <james@jlauser.net>
 > To: bug-followup@FreeBSD.org, James Lauser <james@jlauser.net>
 > Cc:  
 > Subject: Re: misc/96150: pfctl -k non-functional
 > Date: Fri, 21 Apr 2006 18:06:36 -0400
 > 
 > I have verified this with a friend.  His system is running 6.0- 
 > release on i386, and exhibits the same behavior.
 > 
 > 
 > --  James L. Lauser
 >      james@jlauser.net
 
Responsible-Changed-From-To: freebsd-bugs->freebsd-pf 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Mon Apr 24 02:04:55 UTC 2006 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=96150 

From: Maciej Wierzbicki <voovoos@kis.p.lodz.pl>
To: bug-followup@FreeBSD.org,  james@jlauser.net
Cc:  
Subject: Re: bin/96150: pfctl(8) -k non-functional
Date: Tue, 20 Jun 2006 13:00:19 +0200

 pfctl -k works without any problem on either 6.1-RELEASE-p1 or several 
 5.4/5.5 machines.
 
 Most probably the originator tried to use -k with "external" hosts, not 
 local ones. In that case he should use pfctl -k host -k host as 
 described in manpage:
 
 /*
               To kill all of the state entries from host1 to host2:
 
                     # pfctl -k host1 -k host2
 */
 
 So, in case there are two states:
 self tcp A.B.C.D:22 <- A1.B1.C.D:60361 ESTABLISHED:ESTABLISHED
 self tcp A.B.C.D:22 <- A2.B2.C.D:50120       ESTABLISHED:ESTABLISHED
 
 pfctl -k A.B.C.D will kill both, while
 pfctl -k A.B.C.D -k A1.B1.C.D will kill first one only.
 
 -- 
 *   Maciej Wierzbicki * At paranoia's poison door  *
 *   VOO1-RIPE   *
State-Changed-From-To: open->closed 
State-Changed-By: mlaier 
State-Changed-When: Thu Jul 27 11:56:45 UTC 2006 
State-Changed-Why:  
As described above, this seems to be a misunderstanding.  Thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=96150 
>Unformatted:
