* Request to change IPv4 preference - mobile apps @ 2019-04-14 17:17 Will Tisdale 2019-05-06 20:57 ` Nico Schottelius 0 siblings, 1 reply; 4+ messages in thread From: Will Tisdale @ 2019-04-14 17:17 UTC (permalink / raw) To: wireguard Hello, I sent a message to the list about weirdness with IPv4 being preferred over IPv6 in the iOS app a few days ago, but it didn't get there for whatever reason. I've since done a bit of digging through the code and found that preferring IPv4 is intentional, and it's also implemented that way on the Android app too. It seems a shame to hobble native IPv6 support for everyone just to work around some peoples misconfigured setups. My suggestion/request would be to change the apps to prefer IPv6 as default, but add a switch to the apps to disable IPv6 or prefer IPv4 for those with broken setups. Does that seem reasonable? Cheers, -Will _______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Request to change IPv4 preference - mobile apps 2019-04-14 17:17 Request to change IPv4 preference - mobile apps Will Tisdale @ 2019-05-06 20:57 ` Nico Schottelius 2019-05-07 16:28 ` Will Tisdale 0 siblings, 1 reply; 4+ messages in thread From: Nico Schottelius @ 2019-05-06 20:57 UTC (permalink / raw) To: Will Tisdale; +Cc: wireguard Hey Will, I think the "proper" way to handle this is by using the happy eyeballs algorithm: resolve AAAA and A, connect to both, use whatever answers first. Best, Nico Will Tisdale <will@z3n.uk> writes: > Hello, > > I sent a message to the list about weirdness with IPv4 being preferred > over IPv6 in the iOS app a few days ago, but it didn't get there for > whatever reason. > > I've since done a bit of digging through the code and found that > preferring IPv4 is intentional, and it's also implemented that way on > the Android app too. > > It seems a shame to hobble native IPv6 support for everyone just to > work around some peoples misconfigured setups. > > My suggestion/request would be to change the apps to prefer IPv6 as > default, but add a switch to the apps to disable IPv6 or prefer IPv4 > for those with broken setups. > > Does that seem reasonable? > > > Cheers, > > > -Will > _______________________________________________ > 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Request to change IPv4 preference - mobile apps 2019-05-06 20:57 ` Nico Schottelius @ 2019-05-07 16:28 ` Will Tisdale 2019-05-08 9:18 ` Nico Schottelius 0 siblings, 1 reply; 4+ messages in thread From: Will Tisdale @ 2019-05-07 16:28 UTC (permalink / raw) To: Nico Schottelius; +Cc: wireguard [-- Attachment #1.1: Type: text/plain, Size: 1978 bytes --] Hi Nico, Not sure how that would work with WireGuard being a stateless protocol. It also sounds a bit racey given that both v4 and v6 addresses would be flinging packets at essentially the same endpoint. I think the ‘proper’ way is to use the address returned in the AAAA record if one exists. If people’s setup is so broken that it becomes an issue, they will likely have worse issues than WG not working. :) Preferring v4 does weird things like WG using DNS64 addresses over real v6 addresses too - and using NAT64 instead of native v6 is really broken behaviour. Cheers, -Will On Mon, 6 May 2019 at 21:57, Nico Schottelius <nico.schottelius@ungleich.ch> wrote: > > Hey Will, > > I think the "proper" way to handle this is by using the happy eyeballs > algorithm: resolve AAAA and A, connect to both, use whatever answers > first. > > Best, > > Nico > > Will Tisdale <will@z3n.uk> writes: > > > Hello, > > > > I sent a message to the list about weirdness with IPv4 being preferred > > over IPv6 in the iOS app a few days ago, but it didn't get there for > > whatever reason. > > > > I've since done a bit of digging through the code and found that > > preferring IPv4 is intentional, and it's also implemented that way on > > the Android app too. > > > > It seems a shame to hobble native IPv6 support for everyone just to > > work around some peoples misconfigured setups. > > > > My suggestion/request would be to change the apps to prefer IPv6 as > > default, but add a switch to the apps to disable IPv6 or prefer IPv4 > > for those with broken setups. > > > > Does that seem reasonable? > > > > > > Cheers, > > > > > > -Will > > _______________________________________________ > > 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. > [-- Attachment #1.2: Type: text/html, Size: 3155 bytes --] [-- Attachment #2: Type: text/plain, Size: 148 bytes --] _______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Request to change IPv4 preference - mobile apps 2019-05-07 16:28 ` Will Tisdale @ 2019-05-08 9:18 ` Nico Schottelius 0 siblings, 0 replies; 4+ messages in thread From: Nico Schottelius @ 2019-05-08 9:18 UTC (permalink / raw) To: Will Tisdale; +Cc: wireguard Hey Will, even though I do prefer IPv6, the approach that you describe has been shown to be rather error prone and is one of the reasons, why people turn off IPv6 at the moment. So in my opinion, using happy eyeballs would be the proper way of handling the matter, as it gives users the best experience and has proven to be working for browsers. In terms of "flinging packets": there is at maximum 2 packets in this state, as can be seen in the following diagram: client -----> [v6] -----> server -----> [v4] -----> client <----- [v6] <----- server <----- [v4] <----- Τhen the client continues to use either of both protocols, let's say ipv6 was faster in answering: client -----> [v6] -----> server client <----- [v6] <----- server ... I don't think this any realistic problem, we are talking about a few bytes per session / reconnect, not a generic overhead. Best, Nico Will Tisdale <will@z3n.uk> writes: > Hi Nico, > > Not sure how that would work with WireGuard being a stateless protocol. > It also sounds a bit racey given that both v4 and v6 addresses would be > flinging packets at essentially the same endpoint. > > I think the ‘proper’ way is to use the address returned in the AAAA record > if one exists. If people’s setup is so broken that it becomes an issue, > they > will likely have worse issues than WG not working. :) > > Preferring v4 does weird things like WG using DNS64 addresses over real > v6 addresses too - and using NAT64 instead of native v6 is really broken > behaviour. > > > Cheers, > > > -Will > > On Mon, 6 May 2019 at 21:57, Nico Schottelius <nico.schottelius@ungleich.ch> > wrote: > >> >> Hey Will, >> >> I think the "proper" way to handle this is by using the happy eyeballs >> algorithm: resolve AAAA and A, connect to both, use whatever answers >> first. >> >> Best, >> >> Nico >> >> Will Tisdale <will@z3n.uk> writes: >> >> > Hello, >> > >> > I sent a message to the list about weirdness with IPv4 being preferred >> > over IPv6 in the iOS app a few days ago, but it didn't get there for >> > whatever reason. >> > >> > I've since done a bit of digging through the code and found that >> > preferring IPv4 is intentional, and it's also implemented that way on >> > the Android app too. >> > >> > It seems a shame to hobble native IPv6 support for everyone just to >> > work around some peoples misconfigured setups. >> > >> > My suggestion/request would be to change the apps to prefer IPv6 as >> > default, but add a switch to the apps to disable IPv6 or prefer IPv4 >> > for those with broken setups. >> > >> > Does that seem reasonable? >> > >> > >> > Cheers, >> > >> > >> > -Will >> > _______________________________________________ >> > 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. >> -- 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-05-11 13:10 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-04-14 17:17 Request to change IPv4 preference - mobile apps Will Tisdale 2019-05-06 20:57 ` Nico Schottelius 2019-05-07 16:28 ` Will Tisdale 2019-05-08 9:18 ` Nico Schottelius
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).