Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have 2 smoothwall 1.0 systems that I have updated to fixes5 and now the Intrusion Detection System (snort) will not start (i.e. the status page shows it as stopped and it has always been enabled in the IDS tab). It was running before I uploaded fixes1-5.
I suspect that it was fixes4 that caused the problem since that updates to snort2.0 but I can't be sure since I applied all the fixes at once.
I am a Linux novice.
Any suggestions on how to track this down?
Did you reboot between fixes? There were kernel changes as well that need the new modules running
There was a problem with fixes 4 incorrectly addressing the rules files.
I turned snort off before applying fixes 5 and all went well.
There are also a lot of mailing list comments about making sure there is sufficient ram available to install fixes 5, hence turning services off before applying the fix.
Maybe you can try re-installing fixes 5...
If you ssh -p 222 into the box as root and do ps -ax you will see if snort is actually running or not.
Peter,
Thanks for the reply.
I uploaded all the fixes and then rebooted. Did that screw things up? If so, should I just reinstall or is there an easy way to recover?
One system is a P200 with 192M RAM. Web proxy, VPN, secure shell server, and DHCP server are stopped.
The other is a P75 with 64M RAM. Web proxy, VPN, and secure shell server are stopped.
Do you know what is considered to be "sufficient" RAM?
I have not yet learned what goes on during the patch process. Would uploading the fixes 5 update again, re-install it?
I ran the process status command on one system and snort is definitely not running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.