From owner-freebsd-questions@FreeBSD.ORG Thu Jul 7 01:35:00 2005 Return-Path: X-Original-To: freebsd-questions@FreeBSD.ORG Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D28F16A41C for ; Thu, 7 Jul 2005 01:35:00 +0000 (GMT) (envelope-from fbsd_user@a1poweruser.com) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id A78DC43D4C for ; Thu, 7 Jul 2005 01:34:55 +0000 (GMT) (envelope-from fbsd_user@a1poweruser.com) Received: from barbish ([69.172.31.81]) by mta9.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with SMTP id <20050707013454.QPKN29002.mta9.adelphia.net@barbish> for ; Wed, 6 Jul 2005 21:34:54 -0400 From: "fbsd_user" To: "freebsd-questions@FreeBSD. ORG" Date: Wed, 6 Jul 2005 21:34:53 -0400 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Does PF firewall have stateless rules X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd_user@a1poweruser.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2005 01:35:00 -0000 Does the OpenBSD Packet Filter firewall have stateless rules? Meaning, if I coded a rule to pass in for port 23 without any of the different state options coded, do I also have to code the same kind of rule to allow that port 23 packet back out like in IPFW. Or is there no stateless rules in PF? Meaning that coding a rule to pass in for port 23 without any of the different state options coded, it defaults to standard state processing and the resulting outbound packet will be allowed out because it belongs to the same session.