Hello! I'll probably switch back to the current stable version (2.x) but I wanted to give Panda a roll to see what new "features" were in store. Before I switch back though, I thought it would be a good idea to see if anyone had any input on how I can tap the power of my logs and such.

Here's my problem:
When I SSH into my network from the outside (through the RED interface, trying to ssh into my orange network) I not only can't get in, but it ends up crashing my Smoothwall box so that I can't access it, or any machine on my network (since they are all routed through the smoothie). Any ideas on how I can groke through my logs and such after a reboot? It seems that my logs get wiped after each successful reboot...

Or better yet, has anyone else had this happen to them who was able to 'fix' it?

Thanks!

Cool

Any ideas on how I can groke through my logs and such after a reboot? It seems that my logs get wiped after each successful reboot.
Like on a "regular" box there should be no automagical wiping, only periodical rotation of logs. I would first check for any (distro-specific?) settings or tools that do. The other possibility is there is nothing logged if the loglevels are turned up in syslog, so check that too. Next I would make everything log verbose, send everything to syslog and make syslog log remote to a box on your LAN. *Then* try and crash your stuff :-]

Remote logging, excellent idea. It may indeed be an issue with the lack of verbosity. I have tried the usual 'boot with a LiveCD disc' so I can tool around the filesystem easier, but the logs had nothing at all relating to my crash, just the basic startup data, and cron info. I'll keep plugging along, thanks for the ideas!

Cool