Posted by Grommish on Aug 10, 2019; 4:43am
URL: https://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1809.html

You can fork the repo if you want, but realistically, it's bigger than you need unless you plan on trying to build our an image yourself.  The only thing that would cause issues with building your own image is that I didn't keep track of the host package requirements.  So, you'd have to build out the image and when it errors, add the required package to your system, build out again.. Wash, rinse, repeat until it builds out.

Optionally, you can make the changes on your Shield device and once you're happy with the changes, you can send me the changed files directly, put them here, or git init your own repo on GitHub for just the Snort directory (or /etc) and I can cherry pick the changes from it.

However you want to do it, and whatever is easiest for you.  I can make it work in any of the above situations.

The /files folder are files that are included (in the file structure outlined) in the image when it's compiled, yes.  It's how I add custom files outside of the vanilla stock version unless I have to specifically edit a package itself (which is why I use https://github.com/Grommish/OpenWrt_Feeds_Packages for that, so I can merge my changes with commits from the upstream).

Gnomad wrote

Cool, so propose this as a reasonable way to track changes?
a. fork your repo
b. baseline these files under the /files/etc/snort/profile folder
c. PR changes back to you

(I presume content under /files is just pasted over the top once the image
is restored?)

Cheers, Dave.

On Mon, 5 Aug 2019 at 01:22, Grommish [via Itus Networks Owners Forum] <
[hidden email]> wrote: