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 Network at RIPE 67
- Previous message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
- Next message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Thu Oct 17 08:32:27 CEST 2013
* Jen Linkova > On Mon, Oct 14, 2013 at 9:41 AM, Roger Jørgensen <rogerj at gmail.com> wrote: >> Android on the other hand failed horrible with IPv6 only, (Android >> 4.0.*/4.2 and 4.3), it expect IPv4 and when it don't get it after a >> while it move on to the next SSID it can connect to. > > Yeah, known issue. However it works perfectly fine for me (Android > 4.3) since I applied a workaround (static v4 and DNS config). > Tested all applications I normally use on my phone. Yes, this works for me too. However the 464XLAT functionality does not get enabled, presumably because the bogus static placeholder IPv4 configuration fools it into thinking that there is no need for it. Not that I expected this to work to begin with... Tore
- Previous message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
- Next message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]