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] 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 ]
Nico CARTRON
nicolas at ncartron.org
Mon May 23 14:35:50 CEST 2016
On 23 May 2016 at 14:32:59, Nico CARTRON (nicolas at ncartron.org) wrote: On 23 May 2016 at 14:24:55, Jen Linkova (furry13 at gmail.com) wrote: 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? Yes it does. I'm seeing significant packet loss on wireless right now, on both dual-stacked and v6-only network, so it might the reason Possibly. 2) how exactly does it fail? DNS resolution/connection timeout? Nope, DNS resolution works fine: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2934 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;dragon.eecs.jacobs-university.de. IN A ;; ANSWER SECTION: dragon.eecs.jacobs-university.de. 277 IN A 212.201.49.38 My mistake, with AAA it’s better: ;; QUESTION SECTION: ;dragon.eecs.jacobs-university.de. IN AAAA ;; ANSWER SECTION: dragon.eecs.jacobs-university.de. 107 IN AAAA 2001:638:709:3000::3a Could it be related to the special port (5000) you’re using? I confirm what Jen said, there’s noting listening on 5000 over IPv6. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ipv6-wg/attachments/20160523/40769a14/attachment.html>
- 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 ]