This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 only as default for next meeting
- Previous message (by thread): [ipv6-wg] Implications of NAT/NAT64 and similar
- Next message (by thread): [ipv6-wg] IPv6 only as default for next meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Radu-Adrian FEURDEAN
ripe-wgs at radu-adrian.feurdean.net
Fri May 15 14:36:23 CEST 2015
On Fri, May 15, 2015, at 00:21, Jérôme Fleury wrote: > During WG this afternoon, the idea was submitted that the IPv6 only > experimentation be made the default SSID for the next meeting. > > While this has been working tremendously well for routine internet > usage, I've been unable to use this network mainly because of > incompatibility with my VPN network. Hi Jerome, The VPN clients (almost all of them) are actually changing your host from a IPv6-only one to a dual-stacked one. The "split DNS" feature is supposed to solve (or at least alleviate) the problem if available and enabled. A somehow similar situation (IPv6 only device turned dual-stack) arises when you use your mobile phone on the v6-only network, with mobile data still turned on.The problem in that set-up is that you are not able to see misbehaving applications, since they may be using the 3G/4G interface to communicate using IPv4. I've seen this happening with Lollipop (Kitekat was not working at all on v6-only network). Does somebody have any idea about the exact situation in Apple/iOS-land ?
- Previous message (by thread): [ipv6-wg] Implications of NAT/NAT64 and similar
- Next message (by thread): [ipv6-wg] IPv6 only as default for next meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]