Posted by
Grommish on
Jul 14, 2020; 11:58pm
URL: https://itus.accessinnov.com/Itus-Networks-Shield-Firmware-v2-Released-tp2084p2092.html
The PLATFORM is stable, the device is stable, but it's just a platform to build on...
Some things to keep in mind: If you are using your Shield in a production environment, take the time to play with the recovery before you commit to anything. Keep in mind that if you're using the Shield in a production environment, you're using a device with inherent security flaws due to the age of the kernel and the packages.. That, honestly, was my main concern when starting this.
Installing the apps you want shouldn't be difficult. Most of the popular applications all have luCi interfaces, but some do not (like snort/snort+, which I'm having issues with) and packages like e2guardian have been removed from OpenWrt completely. I'm working on bring e2guardian back and updated, but it's just one of those things that "has to be done" in good time. Just checking the repo, snort3/Snort+ built, but snort 2.x did not (probably because I'm using gcc10.1 rather than gcc8). Snort3, if you install it, doesn't come with much pre-setup and doesn't have a luCi page. So, if you want snort3, you'll have to work at it. Those type of "turn-key" installs are something I (or anyone who wants to now that I've put the source up) can build out.. I would SUGGEST getting in touch with me if you want to try and build your own version, because the repo will build EVERY SINGLE PACKAGE and it takes forever (which is how we can have a opkg repo)
My goal is to migrate to kernel 5.4, but I'm having issues forward-porting the Ethernet drivers. If any of you know a decent C programmer, send them this way hehe. I can build (as evidenced by the dev thread) a 5.4 kernel, but the network fails to do anything. One of those things, again, for the future.
Example idea:
You could, in theory, set eth0 and eth2 as WAN ports, eth1 as LAN port, using the mwan3 package to create a hot-failover WAN link with load-balancing..

I was wondering if OpenWrt has iSCSI packages and the Shield could be used as a NAS front-end
In any case, I am going to continue playing with the codebase. For example, I just realized OpenWrt was build using -Os for space-constrained devices, and we probably would get BETTER results from an -O2 or -O3 - But, that's for later, and if I do go that direction, it'll be a sysupgrade file so at the worse, sysupgrade won't have been full fixed yet and it doesn't save some things (but saves others) - So an upgrade would simply mean resetting some things back up (Network settings get saved, for example, the password didn't, the theme didn't, etc). it still needs to be looked at, but I figure what is here is stable enough to do what you need it to do.
Running Itus Shield v2 Firmware