Re: ipfwadm problem

["B. James Phillippe" <bryan terran org>]

On Mon, 30 Nov 1998, Rich Payne wrote:

> Check your .config file after running make xconfig. Many people
> have told me that make xconfig and make menuconfig will produce
> 'broken' .config files. Maybe you could try just a regular make
> config.

Yes, make menuconfig and xconfig should be removed from the kernel (IMO);
they are broken and/or unmaintained and will produce bogus .config files.
I've never been burned with:

   make config dep clean boot modules{,_install}

> Ken Marin wrote:
> > 
> > >I'm running or trying to run an AS200 4/233 with RH5.1.  Everything is
> > >working well except when I try to run any ipfwadm command I get this
> > same
> > >error.  (new user)
> > >
> > >[root@home /root]# ipfwadm -F -p deny
> > >ipfwadm: setsockopt failed: Protocol not available
> > >[root@home /root]#
> > 
> > I tried the old ipfwadm from 5.0 and the new fixed one.  It still won't
> > work.  Could it be that  it is not configured in the kernel?  I don't know

This problem is not related to the RedHat-shipped-a-busted-ipfwadm problem;
in that case, you will get -EINVAL ("Invalid argument") as a errno for
setsockopt() because the struct used to pass the ipfwadm command is broken
(too small) in glibc.  The error you are getting indicates that forwarding
was not compiled into your kernel.  Make sure you rebuild your kernel with
IP firewalling and forwarding, and then enable the forwarding by doing an:

   echo 1 > /proc/sys/net/ipv4/ip_forward

To make the change permanent, you edit your /etc/sysconfig/network and
change the line that says FORWARD_IPV4= to FORWARD_IPV4=yes.

cheers,
-bp
--
B. James Phillippe	. bryan@terran.org
Linux Engineer/Admin	. http://www.terran.org/~bryan
Member since 1.1.59	. finger:bryan@earth.terran.org