What does the following output (after there are IP's actively being blocked via running banmalware or whatnot);
Code:
wc -l /tmp/mnt/abs/skynet/scripts/ipset.txt
and
Code:
{ ipset save Whitelist; ipset save Blacklist; ipset save BlockedRanges; ipset save Skynet; } | wc -l
I think what happens is that Banmalware doesn't run anymore right after reboot, as before this Skynet version, I could see in the log the Skynet message every hour (assuming the router rebooted 5am, the skynet was starting fine and the message was every hour, 6am, 7am, etc), but now, after reboot, I cannot see that message anymore, for example, the router reboots at 5, then there is no message anymore until I manually run the Banmalware. After that, the message is back there every hour... until next reboot.
(PS: besides DNSCrypt, Skynet and ABS, I also have OpenVPN client set to run at boot.)
Anyways, this is 10 minutes after I've manually rebooted the router:
- in the router log I've seen:
Code:
Skynet: [Complete] 0 IPs / 0 Ranges Banned. 0 New IPs / 0 New Ranges Banned. 0 Inbound / 0 Outbound Connections Blocked! [61s]
- then I run the codes you've posted, and:
Code:
wc -l /tmp/mnt/abs/skynet/scripts/ipset.txt
47 /tmp/mnt/abs/skynet/scripts/ipset.txt
- and
Code:
{ ipset save Whitelist; ipset save Blacklist; ipset save BlockedRanges; ipset save Skynet; } | wc -l
47
Then I run Banmalware manually (I ran it twice, as after first run I've only got few IPs reported:"Skynet: [Complete] 313 IPs / 0 Ranges Banned. 313 New IPs / 0 New Ranges Banned. 0 Inbound / 0 Outbound Connections Blocked! [39s]"), and after couple of minutes:
- in the router log
Code:
Skynet: [Complete] 148431 IPs / 3373 Ranges Banned. 148118 New IPs / 3373 New Ranges Banned. 0 Inbound / 0 Outbound Connections Blocked! [60s]
Skynet: [Complete] 148431 IPs / 3373 Ranges Banned. 0 New IPs / 0 New Ranges Banned. 0 Inbound / 0 Outbound Connections Blocked! [7s]
- and
Code:
wc -l /tmp/mnt/abs/skynet/scripts/ipset.txt
151844 /tmp/mnt/abs/skynet/scripts/ipset.txt
- and
Code:
{ ipset save Whitelist; ipset save Blacklist; ipset save BlockedRanges; ipset save Skynet; } | wc -l
151844
Note/Bonus: after last Skynet update, my Dropbox client on computer doesn't want to connect/sync anymore, but I am not 100% sure whether it's because of Skynet or not, even if I did no other changes to my network or computer since before last Skynet update. However, Dropbox client can connect & sync perfectly fine on my other WiFi network/router, so that's a good enough workaround for now.