upgrading from 5.2.1 to 5.3 broke my ipfw

[Martes Wigglesworth]

That is really a problem. I have seen more broken stuff with 5.3, than
with 5.2.1, than I care to complain about. 

The way that the default-accept option is supposed to work, is that your
default 65535 rule is allow ip from any to any.  Your experience is not
normal.  You rules should apply to something.
Have you tried doing a /etc/netstart?  I used to get ignored
functionality, when my routing table was querky, due to dhcp or
something else.  The main issue is that your rule is saying one thing,
and not doing the displayed functionality.  That is something that you
may want to put to the Current list.

I am not an expert, however, I have bumped into erronious-user land many
a time, with BSD, and I have experienced such functionality, with the
exception of the ficticious default rule.(Please excuse spelling)  You
may want to fetch the newest CVSUP'd src and recompile the kernel, with
a new version of the config file, and all. I have found that an
unreliable source can cause this wierdness, aswell.
-- 
Respectfully,


M.G.W.

System:
Asus M6N 
Intel Dothan 1.7
512MB RAM
40GB HD
10/100/1000 NIC
Wireless b/g (not working yet)
BSD-5.2.1
GCC-3.3.5/3.3.3(until I replace indigenous gcc)
IFORT-for linux(Intell Fortran)
gfortran
python-2.3
Perl-5.6.1/5.8.5
Java-sdk-1.4.2_5
KDE-3.1.4
-------------- next part --------------
An embedded message was scrubbed...
From: "David Roberts" <dtrobert at pacbell.net>
Subject: upgrading from 5.2.1 to 5.3 broke my ipfw
Date: Thu, 11 Nov 2004 22:57:12 -0800
Size: 5088
Url: http://lists.freebsd.org/pipermail/freebsd-ipfw/attachments/20041112/856e2b2c/attachment.mht