Okay so using the first link, i am not sure why there are no ranges since it would be pulling the lists straight from the sources like skynet default does:
as you can see, there is not that much difference between the default, versus mine:
in fact I include all the lists that are in skynet default. So it should be banning those "ranges" still.
The question begs to ask why is skynet doing this incorrectly in some instances?
Let us look at what skynet code defines to be a "range"-
This is User added ranges (added by skynet menu option for ranges):
This is ranges blocked by blocking countries:
This is ranges blocked by blocking VIA "ASN" codes
@Adamm- "Why are when users load a custom filter.list, their user defined ranges are not included in the iptable rules; however, when they use the default filter lists their user defined ranges are included in the iptable rules?"
Basically
@Ubimo has pointed out when they load a custom filter.list, not much different from the default, there are no longer any ranges showing up as being banned in the statistic ( which implies the skynet-banned ranges rules are not getting loaded when switching to custom filter.list option). However, when they switch back to default filter.list, their banned ranges are once again included in the statistics (which implies skynet-banned ranges are once again loaded properly into the iptable ruleset).
@Ubimo
In the code link below, I see reference to using the custom list with the banmalware option. Possibly different steps are taking if "fast-switch" is enabled in diversion or skynet. Maybe this is causing the skipping of adding ranges when using custom filter lists? But I don't know
@Adamm script well enough yet to tell you.
more specifically, this line:
@Ubimo
A temporary solution is to manually restart skynet after switching to custom filter lists and your "blocked ranges" should hopefully be added back. (banned ranges = ranges you have added, any countries you block, and any ASN codes you block, and anything that gets added with a subnet attached like /24 at the end of the ipaddress).
Code:
( firewall ban range 8.8.8.8/24 "Apples" ) This Bans the CIDR Block Specified With The Comment Apples
( firewall ban country "pk cn sa" ) This Bans The Known IPs For The Specified Countries (Accepts Single/Multiple Inputs If Quoted) https://www.ipdeny.com/ipblocks/
( firewall ban asn AS123456 ) This Bans the ASN Specified
@Ubimo
If the custom filter list were loading correctly, here would be the amount of banned IPS ranges contributed.
