Bug: Block counter (TOTAL_BLOCKS) remained at 0 despite detecting and
logging multiple block events (FIREWALL_BLOCK, SUBNET_BLOCK, INSTANT_BLOCK_RCE,
CPHULK_BLOCK, DISTRIBUTED_ATTACK). This caused the monitoring display to show
"Blocks: 0" even when blocks were actively occurring.
Root cause: Block event logging was performed at 6 locations but the
increment_block_counter() function was never called to update the counter.
Fixes applied (6 total):
1. Line 1951: Add counter increment after INSTANT_BLOCK_RCE logging
2. Line 2231: Add counter increment after FIREWALL_BLOCK logging
3. Line 2298: Add counter increment after CPHULK_BLOCK logging
4. Line 2525: Add counter increment after SUBNET_BLOCK (network attack) logging
5. Line 3314: Add counter increment after DISTRIBUTED_ATTACK logging
6. Line 3340: Add counter increment after SUBNET_BLOCK (distributed) logging
Result: Block counter now properly increments when each block type is detected,
providing accurate reflection of security action counts in the monitoring display.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
cschantz
23a571fc0c