Never mind. I had manually upgraded the dnsmasq package and I just noticed that I forgot to also upgrade the corresponding dnsmasq-base package. And therefore, I was actually still running the v2.82 binary.

So this bug can be closed.

Cheers,

Timo

Reply via email to