> > Another bug seems to be related to the firewall packet logging when
> > the machine can't write the log fast enough. Flood ping the machine
> > from a local Ethernet (luckily a 64kbit/s BRI doesn't seem to be
> > fast enough) crashes the machine reliably. Aside of the the way
>
> Thats odd. I test that by flood pinging and otherwise bombing 2.0.x boxes
> over 10baseT. 2.1 cleans this up with a netlink device that allows you
> to receive the packets that the firewall bounces
>
> > the kernel accounting of packets is implemented is more or less
> > a bad joke performancewise.
>
> Its designed for up to about 100 entries. I'd measure its performance
> before assuming its a joke BTW. It works fine
please accept my excuse for this posting. I didn't intend to critizise
your firewall code which works as you say. The problem I've mentioned
seem to be related to the packet logging feature (CONFIG_IP_FIREWALL_VERBOSE)
of the firewall. When I flood ping an address for which packets will
be logged via syslog the machine crashes. And you won't call the
packet logging via printk & syslog hyper optimized, don't you?
Ralf