On Thu, Dec 29, 2016 at 10:22 AM, Jörg Thalheim <jo...@higgsboson.tk> wrote:
> On the other hand switching between dual-stack/ipv4 only networks/ipv6 only 
> networks
> is problematic at the moment with the tools we have for roaming clients,
> because wireguard only supports one endpoint of one address family at the 
> time.
> This might be partially fixable in future by observing the availability of 
> default routes
> in userspace (switch address family if it become unavailable). However the 
> optimal
> solution would be something like the happy eyeballs protocol 
> (https://tools.ietf.org/html/rfc6555),
> which is implemented in modern browser -
> only because somebody got a v6/v4 default route does not mean it is also 
> route able.
> I don't know how the latter one would fit into the stateless concept of 
> wireguard.
> I currently help myself by using an dedicated routing protocoll.

Any suggestions on what the right behavior would be to support changes
in a dual stack environment?
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Reply via email to