Julian Andres Klode

OK, in the linked commit 6a1861aad7c92ee54d172f3a5edcdd83d84a340c there are two dialogs: First the user is informed that power optimisations may cause issues, if he clicks yes, then a system-provided dialog pops...

The message is shown only once, and only if DNS66 is set to optimized.

Forgot to merge the ignore power optimization thingy :(

That's exactly the opposite of what this bug describes.

What I meant is that the notification looks more accurate than the activity. But perhaps I'm wrong.

It only says that Android told DNS66 that network connectivity changed to no connectivity. It obviously stops then, waiting for network.

Oh, but that's not _really_ a bug, you surely don't have 254 DNS servers configured, or well, more then 128. So the packet would be rejected anyway. Catching _all_ exceptions...

So, I'll do `&0xFF` somewhere to allow more than 128 DNS servers, as it does not hurt, but I don't think it will be all that useful in practice :)

Well, it's in logcat because it's explicitly logged so we know the reason why we could not forward. And I guess you are seeing multicast packets to those ip addresses....

not yet