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/ipv6-wg@ripe.net/
[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:29:34 CEST 2016
On Mon, May 23, 2016 at 2:15 PM, Nico CARTRON <nicolas at ncartron.org> wrote: >> [a] http://goo.gl/hbzbwD > 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? furry at Wintermute:~>dig dragon.eecs.jacobs-university.de aaaa +short 2001:638:709:3000::3a furry at Wintermute:~>telnet -6 dragon.eecs.jacobs-university.de 5000 Trying 2001:638:709:3000::3a... telnet: connect to address 2001:638:709:3000::3a: Connection refused telnet: Unable to connect to remote host That host does have IPv6 address in DNS (so no NAT64 is involved) but nothing is listening on tcp/5000 on that IPv6 address. -- 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 ]