on an old router it takes to it fine, on new asus be router with vpn im getting an issue failed to start. any tricks I could do to fix it. maybe sleep command just so vpn can start first.
whitelisted firewall settings that reflect unbound config
I changed the values for whitelisting vpn and etc. does it look alright
%YAML 1.1
---
# Holds variables that would be used by the engine.
vars:
# Holds the address group vars that would be passed in a Signature.
address-groups...
Just wanna avoid the oops I didn't know I just fixed it. or just noticed it was missing something. I have been here for long time now and just know how this story goes.
does his new skynet only allow 15 addresses max, and takes way longer to add a list, or has that been fixed. when i added my list to that version it failed after the 15 mark, just a bunch of failed to loads.
If you use vpn, try whitelist the vpn asn or all dynamic ips that vpn connects to. also whitelist the dns ip related to the vpn. seems to make it come together nice when thats done
To install on older routers such as AC68u use
/usr/sbin/curl -s "https://raw.githubusercontent.com/Adamm00/IPSet_ASUS/08d0c3e47a96d843dba8e33101b6644eb8205cee/firewall.sh" -o "/jffs/scripts/firewall"
so i guess the amount of lists allowed to be used is just capped. like 15 at the most it looked like to me. went from 700 thousand to 50 thousand pretty quick lol
For anyone who wants to go back, uninstall skynet. exit to root and use this code for version v7.6.5 basically copy and paste, copy full thing
/usr/sbin/curl -s "https://raw.githubusercontent.com/A...47a96d843dba8e33101b6644eb8205cee/firewall.sh" -o "/jffs/scripts/firewall" && chmod 755...
Way slower, not very efficient , failed to download is a common occurrence. go back to the quick and dirty build cause this sucks. can't even use a custom firewall without it throwing a fit. Isn't linux supposed to be fast. so wack