Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Jun 1996 18:52:20 -0500 (CDT)
From:      Alex Nash <alex@zen.nash.org>
To:        nate@sri.MT.net
Cc:        gpalmer@FreeBSD.ORG, stable@FreeBSD.ORG
Subject:   IPFW (was Re: miscfs/devfs)
Message-ID:  <199606062352.SAA04206@zen.nash.org>

next in thread | raw e-mail | index | archive | help
> And, the IPFW stuff is still in limbo with me.  Some of the
> documentation/hooks and such were brought into -stable, but others
> weren't.  Poul or someone else should finish the job he started.  Me,
> I'm still using the old version with the 'bug you could drive a tank
> through', but I'm not worried since my box hasn't went down in over 3
> months, so the bug won't affect me until I manually reboot my box and/or
> the power goes out.  If the latter happens I'm not worried either since
> my ISP (across the street) takes about twice as long form my link to
> come up, which means my entries will be in place long before the
> internet comes a knocking. :)

I believe IPFW is synchronized between -stable and -current (minus
some compiler warning cleanup by Gary).  The documentation on the
other hand, is either not complete (the ipfw man page), or somewhat
invalid (the handbook -- Gary's writeup is excellent, but the syntax
has changed and new features have been added).  

If there's anyone to blame for this, it would be me.  I've agreed to
take the ipfw torch from Poul, but I've only just recently gotten
commit privileges.  If anyone is interested, I've placed my proposed
changes (that I'd originally submitted as PRs) at:

   http://www.freebsd.org/~alex

If anyone wants to take a look at it and give me some feedback, I'd
really appreciate it (please keep in mind that it's not complete
yet!).  I'll probably check this into -current, cleanup the documentation
issues, wait a while, and then merge it into -stable.

Alex



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606062352.SAA04206>