Sterling, the odd thing for me was that this started occurring on a WRAP
board with m0n0wall v1.3b4 (I think was the version), then I updated
the WRAP to m0n0wall v1.3b10 - saw same results, at which point I put in
a new ALIX with m0n0wall v1.3b10 - same results.
From what I saw, when connected to the serial port it looked like the
nat state table was being overwhelmed...
Once that happened, web gui stopped responding, and remote syslogging
stopped too, then it would panic, reboot and all was well for a random
period of time.
Things have mostly cleared up, though I have seen it (it is back on
original WRAP) exhibit this behavior a couple time since then.
Sterling Windmill wrote:
> I have an Alix 2c1 running m0n0wall in a production environment and I
> have seen it reboot on me a few times, although it doesn't in my case
> correlate with logging into the web interface.
>
> I am outputting my logs to a syslog server behind the router and have
> seen the unit reboot almost as if it had had the power removed and
> replaced. Unfortunately, no suspicious messages are contained in the
> logs, and while it happened three or so times over the course of two
> days, it hasn't happened in about a week.
>
> These events and your e-mail lead me to believe that there is an
> underlying problem of sorts with these pieces of hardware and the
> current beta release of m0n0wall (using b10, I know b11 was released
> yesterday).
|