[EMAIL PROTECTED] wrote:
State-Changed-When: Tue Dec 25 14:14:45 UTC 2007
State-Changed-Why:
Oops, it was actually a recursive panic and the first one is indeed
ipfw-related. The ipfw ruleset would still help though.
I'm not sure that Maxim (a person who got the problem) can
publish his rules. But as i know there is a typical firewall-script
(`ipfw -f flush` and a lot of other rules).
As i see in the code, panic is in the line 2538:
if (set_disable & (1 << f->set) )
continue;
I think panic here can be only when "f" is invalid. I'm right?
But it seems protected with IPFW_RLOCK...
--
WBR, Andrey V. Elsukov
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw
To unsubscribe, send any mail to "[EMAIL PROTECTED]"