From owner-freebsd-security Thu Apr 4 15:25:39 2002 Delivered-To: freebsd-security@freebsd.org Received: from www.kpi.com.au (www.kpi.com.au [203.39.132.210]) by hub.freebsd.org (Postfix) with ESMTP id 32B3037B423 for ; Thu, 4 Apr 2002 15:24:54 -0800 (PST) Received: from kpi.com.au (localhost.kpi.com.au [127.0.0.1]) by www.kpi.com.au (8.9.3/8.9.3) with ESMTP id JAA44780; Fri, 5 Apr 2002 09:24:55 +1000 (EST) (envelope-from johnsa@kpi.com.au) Message-ID: <3CACE0AD.90403@kpi.com.au> Date: Fri, 05 Apr 2002 09:24:29 +1000 From: Andrew Johns User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-gb MIME-Version: 1.0 To: FreeBSD Cc: freebsd-security@FreeBSD.ORG Subject: Re: IpFilter / IpFireWall References: <001f01c1dc2c$23f86e40$0225d7c8@broilo> Content-Type: text/plain; charset=us-ascii; format=flowed 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 FreeBSD wrote: > to use ipfw&ipf use this in your kernel! :) > > options IPFIREWALL > options IPDIVERT > options IPFIREWALL_FORWARD > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=100 > options IPFIREWALL_DEFAULT_TO_ACCEPT > options IPFILTER > options IPFILTER_LOG > options TCPDEBUG > options TCP_DROP_SYNFIN > options ICMP_BANDLIM > options DUMMYNET > options IPSTEALTH > > > ----- Original Message ----- > From: "ozkan_kirik" > To: > Sent: Thursday, April 04, 2002 6:57 PM > Subject: IpFilter / IpFireWall > > > >>i am new to FreeBSD. >>i use freebsd v4.5 Release #0. >> >>i am trying to setup an firewall. >>but i couldnt block or pass any IP. >>i think i have a mistake about my IPF&IPFW settings. >> >>in my kernel: >>options IPFILTER >>options IPFILTER_LOG >>options IPFIREWALL >>options IPFIREWALL_VERBOSE >>options IPFIREWALL_VERBOSE_LIMIT=10 >> >>but my rules doesnt work. >>for example: >># ipfw add deny tcp from 193.255.128.250 to any >>**answer is: >>ipfw: getsockopt(IP_FW_ADD): Protocol not available >> >>when i saw this error i get crazy >> Actually I believe that the "Protocol not available" means that either: a) he's not actually built the new kernel after editing the config file; or b) he hasn't rebooted with the new kernel. That message only appears (AFAIK) when IPFIREWALL is not in the _currently running_ kernel. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message