From owner-freebsd-hackers Tue Jun 9 01:12:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23015 for freebsd-hackers-outgoing; Tue, 9 Jun 1998 01:12:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23003 for ; Tue, 9 Jun 1998 01:12:22 -0700 (PDT) (envelope-from freebsd@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0yjJW2-00087JC; Tue, 9 Jun 1998 04:12:22 -0400 (EDT) Message-Id: From: freebsd@tomqnx.com (Tom Torrance) Subject: IPFW problem? To: hackers@FreeBSD.ORG Date: Tue, 9 Jun 1998 04:12:22 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The sample file to the contrary, it appears that ipfw will not allow the "established" keyword for the "allow icmp" case. Is this a misunderstanding on my part or a genuine fault"? Is there another way to allow ICMP only as part of the TCP protocol? TIA Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message