Hi Jaap, Thanks for the report. Is this a _new_ bug in _new_ version of WireGuard that wasn't there before. Or is this the first time you've observed this? Thanks, Jason