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/[email protected]/
[ipv6-wg] IPv6 only network at RIPE 68
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Sat May 17 12:17:18 CEST 2014
* Piotr Strzyzewski > On Sat, May 17, 2014 at 11:25:17AM +0200, Gert Doering wrote: > >> This is a known Android failure. If there is no IPv4, it will not >> connect to a WiFi network, unless you manually configure some (arbitrary) >> static IPv4 address on the interface. > > Heard the same thing from Marco. However, this means that some users > will fail to use this network, due to the lack of experience/knowledge. True. However, keep in mind that this was true for the main ESSID "ripemtg" this year too: People with devices that didn't support 5GHz had to connect to the secondary ESSID. I think we could very well do the same with IPv4 as with 2.4GHz; take away backwards compatibility for both 2.4GHz and IPv4 on the main "ripemtg" ESSID, but keep a "ripemtg-legacy" or something like that available for devices that requires the presence of either 2.4GHz and/or IPv4. We wouldn't be the first conference to do so, either: https://fosdem.org/2014/news/2014-02-01-pushing-ipv6/ Tore
- Previous message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
- Next message (by thread): [ipv6-wg] IPv6 only network at RIPE 68
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]