Strange fork-related problem: acutally, virus-related
Alex Povolotsky
tarkhil at webmail.sub.ru
Thu Aug 21 03:03:48 PDT 2003
On Wed, 20 Aug 2003 22:07:43 +0200
"Oldach, Helge" <Helge.Oldach at atosorigin.com> wrote:
OH> >
OH> > Anyway, it should not behave that way.
OH>
OH> Should it? Worms are known to be a NAT killer on dedicated routing
OH> platforms. I am
OH> facing customers every other day complaining about their Cisco
OH> router performance
OH> which usually turns out to be caused by virii. (In particular these
OH> days.)
It, speaking RFC-like, MUST NOT hang the computer. It MUST issue diagnostics like "NAT state table overflow, disabling NAT for 192.168.0.104", or just "NAT state table overflow" before hanging. I've spend about a workday fighting that problem...
But I SHOULD ask about it in ipfilter's mailing list...
--
Alex.
More information about the freebsd-stable
mailing list