Date: Fri, 05 Apr 2002 09:24:29 +1000 From: Andrew Johns <johnsa@kpi.com.au> To: FreeBSD <freebsd@icablenet.com.br> Cc: freebsd-security@FreeBSD.ORG Subject: Re: IpFilter / IpFireWall Message-ID: <3CACE0AD.90403@kpi.com.au> References: <a8ii7f%2B9qbc@eGroups.com> <001f01c1dc2c$23f86e40$0225d7c8@broilo>
next in thread | previous in thread | raw e-mail | index | archive | help
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" <ozkan_kirik@yahoo.com> > To: <freebsd-security@FreeBSD.ORG> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CACE0AD.90403>