Maarten Lankhorst wrote:
Hey,
On 09/22/2011 11:25 AM, Ben Peddell wrote:
On 22/09/2011 6:24 PM, Maarten Lankhorst wrote:
Hey,
On 09/14/2011 12:47 PM, Francois Gouget wrote:
Connecting to https://testbot.winehq.org/ over IPv6 hangs for ages :-( This makes accessing it from my desktop very annoying.
$ time wget -4 --quiet http://testbot.winehq.org/ real 0m2.150s user 0m0.000s sys 0m0.000s
$ time wget -6 --quiet http://testbot.winehq.org/ ... still stuck after 6+ minutes
$ telnet -6 testbot.winehq.org Trying 2001:888:2000:38:1000::2... ... same thing
According to http://test-ipv6.com/ my desktop is configured just fine and I only have trouble with the TestBot.
Could this be a firewall problem? (testbot exposing an IPv6 address but the firewall dropping any IPv6 packets)
In the mean time I'm going to use my laptop which is still IPv4 only :-/
That ipv6 address is set on testbot, so it ought to work. Does ICMP6 ping work?
~Maarten
# traceroute -4 -T -p80 testbot.winehq.org traceroute to testbot.winehq.org (82.94.219.252), 30 hops max, 60 byte packets ... 9 te5-4.swcolo1.3d12.xs4all.net (194.109.12.30) 159.889 ms 159.942 ms 159.868 ms 10 v2.gse.nl (82.94.219.252) 161.955 ms 159.354 ms 164.692 ms
# traceroute -6 -T -p80 testbot.winehq.org traceroute to testbot.winehq.org (2001:888:2000:38:1000::2), 30 hops max, 80 byte packets ... 11 te5-4.swcolo1.3d12.xs4all.net (2001:888:0:114::2) 145.296 ms 145.109 ms 145.817 ms 12 * * * ... 30 * * *
Testbot has 2 ips assigned to it:
inet6 addr: 2001:888:2000:38:1000::1/66 Scope:Global inet6 addr: 2001:888:2000:38:1000::2/66 Scope:Global
Wow! /66? And that works? While the standard allows for that you "should use /64" which everybody and his dog read it as that is the only thing that needs to work and the only thing that get tested. IPv6 brings back the class-full thinking which everybody has to painfully unlearn once IPv6 catches on...
"Safe" prefix length (especially if involving client devices) are: /64 - LAN /126 and /127 - point to point /128 - host routes
bye michael