I had a problem with 1.22 where it stopped responding.  I ended up keeping a web browser connected
to http://{m0n0wall}/exec.php and http://{m0n0wall)/status.php and http://{m0n0wall)/diag_logs.php .

You might find that an established connection will give you a window into what's happening.  There
are kernel messages that show up in diag_logs.php that don't get syslog'ed (in my experience).  I
think my problem turned out to be a misconfigured proxy-arp.

bernie

-----Original Message-----
From: Andrew Kemp [mailto:akemp at iquest dot net] 
Sent: Tuesday, June 13, 2006 2:31 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: m0n0wall crashing

my m0n0wall is crashing for some reason, it hard locks and the keyboard is unresponsive. my syslog
messages do not show anything, no messages come back in until traffic is passed again. is there
anyway to see logs or messages from the system before it locks so that i can troubleshoot what is
going on?
 
Andrew
Network Operations
IQuest Internet