Just get -su-2.05b# ipnat -M /var/crash/vmcore.0 -N /var/crash/kernel.0 -s mapped in 0 out 0 added 0 expired 0 no memory 0 bad nat 0 inuse 0 rules 0 wilds 0
And the -l comes back with a ton of stuff (8463 lines to be exact, the breakdown being (8342 BIMAP lines, 1 MAP line (a dns query from an internal dns server), and the rest is the active MAP/Redirect filters). Which is interesting, as I would expect there to be 8343 inuse above, not 0. Greg * Darren Reed ([EMAIL PROTECTED]) [030527 15:56]: > In some email I received from Greg Rumple, sie wrote: > > Okay, I've built a FreeBSD 4.8 box (4.8-RELEASE) to be a firewall for a > > very large internet site. The box is a Celeron 466 (Pentium 3 based) > > with 256MB of ram (yeah I know, thrifty aren't I?). I'm using a very > > complex setup (as this was built to replace a PIX, and therefore it was > > configured to be a direct drop in replacement (hence the extremely > > complex configuration)), and have it working fine short of 1 problem. > > Every 12 hours now I experience a kernel panic. I built a debug kernel > > and here is the backtrace (the relevant part at least) of the crash. > [...] > > Can you do: > > ipnat -M /var/crash/vmcore.X -N /var/crash/kernel.X -s > > and try -l, see if it comes across any stray pointers. > > Darren > -- Greg Rumple [EMAIL PROTECTED]
