[ipv6-wg] v4 versus v6 -- who connects faster?
- Previous message (by thread): [ipv6-wg] v4 versus v6 -- who connects faster?
- Next message (by thread): [ipv6-wg] v4 versus v6 -- who connects faster?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jen Linkova
furry13 at gmail.com
Mon May 23 14:24:29 CEST 2016
On Mon, May 23, 2016 at 2:15 PM, Nico CARTRON <nicolas at ncartron.org> wrote: > Here [a] is a toy v6 service I came up with during the RIPE > Atlas hackathon over this weekend. Thought I share this along: > > [a] http://goo.gl/hbzbwD > > You enter a dual-stacked website (ALEXA top 10K) and it shows > you the difference in TCP connect times over v4 and v6 as seen > by all dual-stacked RIPE Atlas probes (~1.3K probes). You can > also filter the visualisation from a specific origin-AS. This > additional filter can be useful to view performance towards a > website from a specific origin-AS (say DTAG). > > Disclaimer: This is an outcome of a 1.5d long hackathon project. > As such, the codebase is possibly inundated with bugs. Please > don’t see it as a production service :-) > > Nice job, congratulations. > > Out of curiosity, I tried accessing it from the NAT64 Wifi network at > RIPE72, > and http://dragon.eecs.jacobs-university.de:5000 seems not to work for some > reason. > Thoughts? 1) Does it work from the dual-stacked network? I'm seeing significant packet loss on wireless right now, on both dual-stacked and v6-only network, so it might the reason 2) how exactly does it fail? DNS resolution/connection timeout? -- SY, Jen Linkova aka Furry
- Previous message (by thread): [ipv6-wg] v4 versus v6 -- who connects faster?
- Next message (by thread): [ipv6-wg] v4 versus v6 -- who connects faster?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]