Webamin is very slow (about 10sec for response time) on ASL 5. I was previously running ASL 4 on the same machine (PII 233 with 160Mo RAM) without any problem (about 1sec as response time). Any Idea ?
when i tested one of the betas with snort enabled i hit it with kazaa traffic from 4 machines on my hardware without any idegredation of performance. I be this mahcine could handle at least 10 if not more..[:)] it is not a performance or intergratiion issuse.
The use of snort in a small company with, lets say, 400 workstations CAN be a disaster. Not to mention the false postives/ true negatives or whatever they like to call them. It can be a very handy tool but nothing more and only if you know what you are doing.... again IMHO.....
with today's litigous environment it would not be a disaster but prudent. With Snort you can customize the rules however you like. ASL's webmin helps in the customization. I would take a bit of false positive in exchange for the savings from not having to fight the horde of lawsuits that would enevitibly follow p2p behavior or in some cases IM traffic.
IMHO it would be disastrous for SMB/Medium businesses to not use Snort to filter traffic as they can easily be put out of buinesse by one p2p lawsuit.
I myself already run snort on my network (PureSecure) but I am not interested in snort on ASL but rather PortScanning and from what I am told I need the IPS lic in order to enable port scanning [:(]
I'm not saying that you should not use SNORT (or equiv.) but i'm wonder if A) a firewall should be the place for SNORT and B) if there are not any options to block p2p in a 'firewall way'....
And if a company wants to stop the use of p2p they should review there policy when it comes to user rights etc....
1. 5.000 has a bug that makes index.fpl use lots of RAM. I'm talking about ~500 Megs here [:)]ent). 2. Version 5 does not require more CPU, but more RAM in general. The new reporting, confd and the IPS will require a big share. My personal recommendation is at least 512Megs.
What makes WebAdmin so slow is the disk swapping due to memory exhaustion. Get more RAM and it should respond much quicker. I'm afraid it will not reach V4 speeds, but that is due to our new architecture (which does have its advantages after all).
