Butterfly Bones
Very Senior Member
Ok, it was running with no issues for me, I was seeing more block and fewer invalid, but no big deal.Update and re-run banmalware, the issue should correct itsself
Since running the 384.10 beta releases I get kernel: bcm63xx_nand errors every time banmalware runs, though I doubt it is Skynet and I know that it is outside RMerlin control. (sigh...)
Code:
Mar 22 10:39:18 Skynet: [%] New Version Detected - Updating To v6.8.4 (41ae62766f615de2484a6d11ca6bb027)
Mar 22 10:39:22 Skynet: [%] Restarting Firewall Service
Mar 22 10:39:22 rc_service: service 8504:notify_rc restart_firewall
Mar 22 10:39:22 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Mar 22 10:39:22 custom_script: Running /jffs/scripts/nat-start
Mar 22 10:39:22 (install_stubby.sh): 8512 Starting Script Execution (checkipv6)
Mar 22 10:39:22 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Mar 22 10:39:22 Skynet: [%] Startup Initiated... ( skynetloc=/tmp/mnt/SNB/skynet )
Mar 22 10:39:30 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Mar 22 10:39:31 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
Mar 22 10:39:43 Skynet: [#] 217837 IPs (+0) -- 30170 Ranges Banned (+0) || 0 Inbound -- 0 Outbound Connections Blocked! [start] [21s]
Mar 22 10:40:20 Skynet: [#] 158051 IPs (-59786) -- 29145 Ranges Banned (-1025) || 2 Inbound -- 0 Outbound Connections Blocked! [banmalware] [21s]