Hey Toke, For incoming packets, this would be strange behavior, since it's listening on v4 and v6. For outgoing packets, if wireguard thinks it should be sending to a v6 address, then that's what it will do. One way to fix this would be to re-resolve DNS from userspace, which is a bit ugly. Another way would be to simply store the last v4 address, and fall back to that if it can't establish a route for the v6 address. And yet another way -- if simplicity is desired -- would be to do nothing (the status quo), and not build legacy semantics into something new. Any opinions on this?
Jason _______________________________________________ WireGuard mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/wireguard
