On Fri, Mar 20, 2009 at 08:13:43PM +0100, Manuel Bouyer wrote:
On Fri, Mar 20, 2009 at 03:08:18PM -0400, peter wrote:
On Fri, 2009-03-20 at 10:43 +0100, Manuel Bouyer wrote:
No because it's a ethernet bridge; it can carry packets which are
not IP.
No, it's in this state because it used to work fine, and the issue has
just been discovered.
No, see above. A bridge is not a IP device.
What broke it from 4 to 5? Something added to ipf?
I don't know. A lot of things have changed between 4 and 5, in almost all
parts of the kernel.
Without looking at the code, it's possible that it worked most of the time
in 4.0 but not all of the time (i.e. by luck, no KASSERT).