At lookup time this works already. The problem is, if the underlying network topology changes and you need to reconnect via IPv4, when you had IPv6 underlying before.
This is the feature that is - afaik- not currently implemented in wireguard. Henning Reich <henning.re...@gmail.com> writes: > Should a DNS entry Wirth one > AAAA record and one A record solve thus problem? So the OS decide the best > way to connect? > > Ulrich Kalloch <u...@noc23.de> schrieb am So., 29. Sep. 2019, 16:29: > >> Hello @ all >> >> i am interested in this too. >> >> Regards >> >> Ulli >> >> Am 27.05.19 um 20:10 schrieb Rene 'Renne' Bartsch, B.Sc. Informatics: >> > Hi, >> > >> > is it meanwhile possible to define an IPv6 endpoint AND and an IPv4 >> > endpoint as fallback >> > in case a road warrior does not get IPv6 connectivity when switching >> > internet sockets? >> > >> > Regards, >> > >> > Renne >> > _______________________________________________ >> > WireGuard mailing list >> > WireGuard@lists.zx2c4.com >> > https://lists.zx2c4.com/mailman/listinfo/wireguard >> >> >> _______________________________________________ >> WireGuard mailing list >> WireGuard@lists.zx2c4.com >> https://lists.zx2c4.com/mailman/listinfo/wireguard >> > _______________________________________________ > WireGuard mailing list > WireGuard@lists.zx2c4.com > https://lists.zx2c4.com/mailman/listinfo/wireguard -- Your Swiss, Open Source and IPv6 Virtual Machine. Now on www.datacenterlight.ch. _______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard