raptor pingd

["Dykema, Eric" <Eric.Dykema () webvangroup com>]

Hi all.  I have a Raptor firewall that is running pingd so that we can
monitor DMZ systems.  Roughly a couple of times a week, pingd either dies or
just stops proxying pings.  When this happens, I start getting the following
messages in the logfile:

Mar 28 10:11:17.223 xxxxxxxx pingd[2269]: 343 Interfaces Warning: Unable to
determine interface for destination address xx.xx.xx.xx - is the system
local and down? -- test connectivity with ping

I've noticed that the footprint of this process increases as if there is a
memory leak until it's sitting on about 16MB when it finally stops working.

Does anybody else have this problem or know what causes it?  Is it just a
memory leak, or do I need to throttle back the pings going through it?
Axent doesn't seem to have a fix for it.
_______________________________________________
firewall-wizards mailing list
firewall-wizards () nfr com
http://www.nfr.com/mailman/listinfo/firewall-wizards