MxGuard accuracy_us field in dropcatch engine is broken
← back to forum
bug wontfix

accuracy_us field in dropcatch engine is broken

bill@transcom.net (Transcom IS) ยท 2026-04-25 14:00
The accuracy_us field in dropcatch engine_config.json reads nonsensical values. Engine has been ignoring it but the log line is misleading.

Comments (1)

bill@transcom.net (Transcom IS)admin 2026-04-25 14:00
Different project (dropcatch, not mxguard). Leaving the field broken โ€” real timing comes from SOCKET_N_WRITE_TIMING. Documenting as wontfix here for the record.
Sign in to add a comment.