[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 ]
Elvis Velea
elvis at velea.eu
Sat May 17 21:34:35 CEST 2014
Hi, I tried to test the experiment network on Friday as well. And kinda failed. On 17/05/14 21:18, Jen Linkova wrote: > On Sat, May 17, 2014 at 7:35 PM, Roger Jørgensen <rogerj at gmail.com> wrote: >> On Fri, May 16, 2014 at 4:24 PM, Jen Linkova <furry13 at gmail.com> wrote: >>> Thanks for organizing it, it just worked ;) >>> >>> What would be really awesome is to stop announcing that network as 'an >>> experiment'. My understanding is that we need >>> 1) [hardest part] get smth better than 'best effort' support level; >>> 2) change the password from 'iknowbesteffort' >>> 3) stop calling it 'experimental' in public >>> 4) tell people that if smth does not work they should fall back to the >>> 'standard' network and see if it helps. >>> >>> I'm not suggesting making it a default network at the current stage >>> but I think that it is mature enough to move out of 'experimental' >>> phase. >>> We could call it 'pilot', 'canary' or '1st phase of rollout' ;) >> I totally agree we should move forwards. I also agree with your points >> above, but then we have something called reality, an annoying thing >> that slow down progress... >> >> This time the reality is that as long as Android can't connect to a >> IPv6 only network without some manual hack it is a no-go there. > I think I need to clarify: I'm *NOT* suggesting making v6-only network > a default one, deprecate dual-stack SSID or anything like that. > I propose just to change the way we are calling it and get official > support. That's it. I think getting some support from the NCC OPS would be a great thing. Why I kinda failed to use the IPv6 only network was because there was something weird going on. I would connect to it, I would get an IPv6 address, the IPv6 address would then change (in a few seconds) to an other IPv6 address (as shown in the System Preferences -> Network on my Mac) and then the mac would say that I do not have a working connection. Second weird thing was that from time to time, over the same IPv6 only network I would get an IPv4 IP address from the conference network. The OPSie that was next to me when I was trying to troubleshoot this problem tried to contact MarcoH, but unfortunately MarcoH went offline a few minutes after the OPSie msg'ed him and we did not have the chance to really understand what was not working. > >> However - on a more serious note. We might consider to stop calling it >> an experiment as a starter. >> Then we could see if it's possible for the RIPE tech staff to run it >> for the next meeting. The password could stay the same so it's clear >> to people that it's not an official network just yet, it's a pilot, >> pre-release or something. > OK, so you agree with all my suggestions except for changing the password? Well, > I think we can reach a consensus then ;) > >> Then we could reevaluate how things worked out and what is missing >> before it can become a permanent thing... ? > Absolutely. > go for it, it will help people understand what breaks in their network. The only reason I was trying to test the IPv6 only network is to make sure that all our (V4Escrow) services are v6 capable. I even found out that the mail server was v6 capable but only over SMTP (and not IMAP) due to a configuration bug. Therefore, thumbs up for the effort, I managed to get something fixed ;) cheers, elvis
- 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 ]