Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*
Posted by
Roadrunnere42 on
Jun 26, 2019; 9:08pm
URL: https://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1779.html
Hi Grommish
I was under the impression that snort could not do multi tasking, so itus has one instant of snort running on each core, I could be wrong.
With regards to doing Lua for luCi i did look into it a few years back but could not work out do i learn Lua or luCi. I could not find any learning docs for luCi.
How are you doing testing with openwrt on the Shield, do you work things out in a vm running openwrt and then copy to the Shield?
I also ran ipvar HOME_NET [
10.0.0.0/8,172.16.0.0/12,192.168.1.0/16] instead of ipvar HOME_NET any on my Shield, but left it out on any upgrade because it had a side effect which messed things up for some people, but you right not to use ipvar HOME_NET any.
Do i have to build a firmware image from github and then copy over a you said at the beginning of these emails.
Roadrunnere42
On Wed, 26 Jun 2019 at 01:41, Grommish [via Itus Networks Owners Forum] <
[hidden email]> wrote:
Question time.
I've already put out there that I really don't know Snort, so I'm checking to see if what I'm thinking is actually correct.
In Router mode, where there 2 snort instances running concurrently - one for the WAN, one for the LAN - rather than 1 instance that just covers both? This is what it looks like from what I can see in the codebase. Is this so you can have multiple rule sets, one less restrictive between eth1/eth2 (br-lan) and a heavier barrier over eth0? Can anyone explain why this setup might be better than a single instance of snort covering both br-lan and eth0 at the same time? Since a properly setup HOME_NET limits the IP scope (I'm currently using ipvar HOME_NET [10.0.0.0/8,172.16.0.0/12,192.168.1.0/16] instead of ipvar HOME_NET any, for example, with EXTERNAL_NET being !$HOME_NET)