Am 26.05.21 um 16:37 schrieb Jason A. Donenfeld:
This might help:
https://lists.zx2c4.com/pipermail/wireguard/2021-March/006442.html
Hi.
Thanks for the answer.
The registry keys were not present, so I added them manually. That and
the PostUp script seem to have done the trick.
For now, I see this as a viable workaround. Thank you for that.
I still see this as a bug though. I read the reasoning behind it in the
other mail
(https://lore.kernel.org/wireguard/cahmme9rxv2_yg3fgmerdetjfhenkhdc2ccya6kw93n9a328...@mail.gmail.com/).
Maybe only use the IP_UNICAST_IF to the default route if AllowedIPs is
0.0.0.0/0 and/or ::/0? For all other cases it seems unnecessary (errors
in those cases would be configuration problems on the users side) and in
some cases (i.e. mine, the non-default-route case) just wrong.
Thanks again and best Regards
Andre
