An extra amount of work was required because our dnsmasq build uses a different crypto backend. Fortunately themiron had time to adapt the code over the weekend.
Logging has always been quirky. Sometimes I've seen that logs simply took longer to update. Could also be a corrupted database or lack of space in the /jffs partition. You could try deleting the database, then restarting AiProtection:
Code:
rm /jffs/.sys/AiProtectionMonitor/*
"Auto" does not mean "always enable", it means "Enable if you can, otherwise disable".
Check the Tools -> Sysinfo page to confirm that it is indeed disabled. If it is, then it's most likely by design, and could be to resolve the reported issues of Time Scheduling not always properly terminating existing connections.