From owner-freebsd-security Thu Feb 21 2:32:50 2002 Delivered-To: freebsd-security@freebsd.org Received: from caligula.anu.edu.au (caligula.anu.edu.au [150.203.224.42]) by hub.freebsd.org (Postfix) with ESMTP id E677B37B402 for ; Thu, 21 Feb 2002 02:32:47 -0800 (PST) Received: (from avalon@localhost) by caligula.anu.edu.au (8.9.3/8.9.3) id VAA11118; Thu, 21 Feb 2002 21:32:28 +1100 (EST) From: Darren Reed Message-Id: <200202211032.VAA11118@caligula.anu.edu.au> Subject: Re: ipf and IPFILTER_DEFAULT_BLOCK To: jay@musubi.org (jay) Date: Thu, 21 Feb 2002 21:32:28 +1100 (Australia/ACT) Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <20020221021005.H27119-100000@spam.musubi.org> from "jay" at Feb 21, 2002 02:26:40 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In some mail from jay, sie said: > > i built a 4.5 kernel with the IPFILTER_DEFAULT_BLOCK option and after > rebooting found that i had full access in and out of the server (ssh and > other services worked), but could not ping or otherwise connect to > localhost/127.0.0.1. (got a "sendto: no route to host" error). > > after my initial rules didn't work (they work on my openbsd firewall), > i tried it with these rules... > > pass out quick on fxp0 proto icmp all > pass in quick on fxp0 proto icmp all > etc, etc... > > but still no luck. this happened with udp and tcp as well. > ifconfig and netstat -rn showed everything as being normal... > ipmon logged no packets being blocked (i had the log option in my rules) > > i rebuilt the kernel without IPFILTER_DEFAULT_BLOCK and i could ping > localhost again. so... am i on crack or can anyone reproduce this? Did you do build from scratch each time? I don't know if IPFILTER_DEFAULT_BLOCK ends up in a .h file and if it doesn't, you need to either remove the right .o files or do a "make clean" each time. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message