[pf4freebsd] pf errors meaning

[Bruno Afonso]

Hello, 

I'm sorry to disturb the ML silence ;) but I am gettin' some odd panics with a 
machine since I upgraded to 1.66. They may be totally unrelated, but it has 
been two in two days! First crash was due to dnscache, then, last night I 
disabled and replace it with bind. Today morning, it crashed again. So, it's 
either hardware, pf or god playing with me :>

I must say that the machine has been routing ~1megbyte/sec for 24h+. Can this 
be too much of a stress ? :>

btw, Fbsd 5.1, pf 1.66, no altq.

Here are some pf errors while booting the machine with pf enabled on boot.

Oct  2 10:34:09 deq kernel: pflog: $Name: VERSION_1_66 $
Oct  2 10:34:09 deq kernel: pfsync: $Name: VERSION_1_66 $
Oct  2 10:34:09 deq kernel: in6_ifattach: pflog0 is not multicast capable, IPv6 
not enabled
Oct  2 10:34:09 deq kernel: in6_ifattach: pfsync0 is not multicast capable, 
IPv6 not enabled
Oct  2 10:34:09 deq kernel: pflog0: promiscuous mode enabled
Oct  2 10:34:09 deq kernel: pf: $Name: VERSION_1_66 $

Oct  2 10:34:34 deq kernel: Zone pfrktable was not empty (18 items).  Lost 2 
pages of memory.
Oct  2 10:34:34 deq kernel: Zone pfrkentry was not empty (34 items).  Lost 4 
pages of memory.
Oct  2 10:34:34 deq kernel: pflog0: promiscuous mode disabled
Oct  2 10:34:34 deq pflogd[481]: read: Device not configured
Oct  2 10:34:34 deq pflogd[481]: Exiting due to signal
Oct  2 10:34:34 deq pflogd[481]: 0 packets received, 0 dropped

The box was going up from a bad crash, so it was probably fsckin', but should 
that be a problem?

I'm now back to ipfilter for the time being...  (using pf or ipfilter as a 
module, but not both at the same time)

thoughts?

-- 
BA


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/