It is most likely a bad ICMP message like the ping of death type thing.
I would assume that FreeBSD 4.11 was patched for this along time ago. I
don't really know the timelines for FreeBSD's version numbers.
If one knows its ICMP now its easier to tell TCPdump what to capture.
This way capture files are note becoming huge.
Andrew Kemp wrote:
> I do not believe that is the reason that m0n0wall locks up as I allow
> ICMP from one host to my m0n0wall box constantly for graphing in cacti.
> On Jul 4, 2006, at 9:32 AM, Soren Vanggaard Jensen wrote:
>> Hi all,
>> As i told you earlier I've blocked all ICMP traffic for all interfaces
>> on the problem installation. Right now i have an uptime of 4 days,
>> 07:02, which is beginning to give me hope. When i reach 21 days of
>> uptime I'll be 100% convinced that ICMP causes the problems. Has
>> anyone else tried the ICMP block trick and if so - what are your
>>> From: "Klaus Stock" <ks at stock dash consulting dot com>
>>> To: m0n0wall at lists dot m0n0 dot ch
>>> Subject: Re: [m0n0wall] Version 1.22 freeze
>>> Date: Tue, 04 Jul 2006 15:26:44 +0200
>>> > > Right now i have a monowall installation that freequently freezes
>>> > Maybe this is because it's summer at the moment
>>> > and the higher temperatures make some systems
>>> > unstable.
>>> Can't be, as it appears to happen on WRAPs as well. These platforms have
>>> temperature control hardware which will assert Reset on the CPU if it
>>> too hot. Reset gets deasserted as soon as the device cools down again.
>>> This circuit prevents instabilities which might be caused by excessive
>>> temperature. Yup, the device is temporarily shut down, but it won't
>>> do any
>>> funny things, and it will reboot automatically.
>>> However, noone who had reported a freeze had the luck of whitnessing an
>>> automatic reboot.
>>> - klaus