Adamm
Part of the Furniture
OK, now what?
xxxxxxx@RT-AC68U-B088:/tmp/home/root# sh /jffs/scripts/firewall stats search malware 192.124.249.18
Debug Data Detected in /tmp/mnt/SNB/skynet/skynet.log - 184.0K
Monitoring From Dec 15 04:00:56 To Dec 15 09:43:54
407 Block Events Detected
170 Unique IPs
240 Autobans Issued
3 Manual Bans Issued
Exact Matches;
Possible CIDR Matches;
Skynet: [Complete] 157845 IPs / 2015 Ranges Banned. 0 New IPs / 0 New Ranges Banned. 97 Inbound / 0 Outbound Connections Blocked! [9s]
That IP (which I further confirmed myself) isn't currently on any of the standard banmalware filter lists. Potentially it was an autoban? Try the following command;
Code:
sh /jffs/scripts/firewall stats search ip xxx.xxx.xxx.xxx
That will show you if the IP is currently banned, the reason for it being banned and the most recent logs of it being banned. But with that being said, for this particular IP, banmalware at this point in time isn't the reason for it being blocked (if you're running the latest banmalware update ofcoarse)
And to reiterate your concerns, if you can investigate some of these other blocked IPs you were running into and they all point to a common list, let me know and I'll definitely consider removing it.
Last edited: