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 ]
Elvis Daniel Velea
elvis at velea.eu
Sat May 17 22:54:21 CEST 2014
Hi, actually, my partly failed test was on Thursday in the afternoon. See more below, inline: Excuse the briefness of this mail, it was sent from a mobile device. > On 17 May 2014, at 22:08, Jen Linkova <furry13 at gmail.com> wrote: > >> On Sat, May 17, 2014 at 9:34 PM, Elvis Velea <elvis at velea.eu> wrote: >> I tried to test the experiment network on Friday as well. And kinda failed. > >> 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. > > Very interesting..I did not see anything like that (I was using > v6-only SSID all the time, > no unpleasant surprises. A very few things did not work for me but it > was expected and had nothing to do with RIPE network. That is what I was trying to test. To see if anything in my network or any of the services would fail. > >> 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. > > OK, looks like we might need to think about support/escalation model > for the next meeting ;) Exactly what I ment to say. We can not expect to just request something and the RIPE NCC to provide. Support for an IPv6 only network will require more work for the NCC and probably a dedicated FTE because many attendees will come to ask all kind of questions and require help with troubleshooting all kind of weird problems. I would see the benefit - it will help attendees to fix broken IPv6 configurations and discover many bugs. I also see that the decission belongs to the NCC OPS Dept.. they already do a lot to support the meeting, remote access, etc.. cheers, elvis > > -- > SY, Jen Linkova aka Furry
- 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 ]