Check in /etc/rc.local as I know I had put some of the stuff user8446 had suggested here in there. It's why the links jump up and down on boot at the end.

I'm not a massive knowledge base when it comes to Snort, but I have to ask why the preprocessors were suggested to be removed?  Performance has yet to taken a hit in this build at all that I can tell, but it might be from Snort having been such an older version?  Do me a favor and test with the rules to see if the performance hit is still around? I don't mind losing them, I just wish I had more experience.  I've spread the load over both cores and am using afpacket rather than the one Itus used.  I know I was testing with ALL the rules from whatever that rule repo was (don't remember offhand) which even they say not to do AND the Snort community rules on both incoming and outgoing traffic (eth0 and br-lan) without issue.  It was something like 28000 rules all told, and I still hit my link Max of 200-225Mbps down with under a 1.0 load *shrug*

Right now, the system has 400mb free (of the 1gb) RAM after Snort and e2 guardian loads (along with everything else)

Oh! Before I forget again.  I did add full Python support on it, in case you or someone has need of it.

Running Itus Shield v2 Firmware

---

If you reply to this email, your message will be added to the discussion below:

http://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1811.html

To unsubscribe from [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*, click here.
NAML