Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Nov 1997 16:35:30 -0600 (CST)
From:      Alex Nash <nash@Mcs.Net>
To:        Studded <Studded@dal.net>
Cc:        FreeBSD Stable List <FreeBSD-Stable@FreeBSD.ORG>
Subject:   Re: Serious problem with ipfw in 11/10 Snap
Message-ID:  <Pine.BSF.3.95.971115161937.13520A-100000@Jupiter.Mcs.Net>
In-Reply-To: <199711152131.NAA01650@mail.san.rr.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 15 Nov 1997, Studded wrote:

> >If
> >not, it may indicate that ipfw's rules were damaged by a memory overwrite.
> 
> 	I'm not sure what that means.

Basically, some piece of ipfw or other kernel code unknowingly stomped on
the two bytes of RAM which contained the rule number.  The rule should
have contained 65535 (as a short), or 0xFFFF, but instead had 0x0000.

Another mystery is why a flush would not have eliminated this rule.  The
flush code removes everything but rule #65535.

Do you still have the problem SNAP kernel?  If it's configured with 2940
or 53c810 support I'd like to give it a try here.

Alex




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.971115161937.13520A-100000>