|
ping6 tracert6 works visit ipv6 sites work not
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Friday, 10 September 2004 21:09:01
I've registerd sixx.net and I have a tunnel with surfnet.
I installed hearbeat at windows xp sp1 I stopped the windows ipv6 firewall.
I can ping en trace ipv6 ip's
but I can't visit ipv6 sites, he say's that I visit via ipv4
I have a sweex hardware router, The ip from the local pc is in the dmz
What is wrong with my configuration
ping6 tracert6 works visit ipv6 sites work not
![[be]](/s/countries/be.gif) Carmen Sandiego on Saturday, 11 September 2004 10:36:25
Are you using the proxy server of SURFnet (if they even have one) in your Internet Explorer settings? If so turn it off, most likely their proxy server is only IPv4-capable and thus gets you an IPv4 page, since you can trace and ping (and you turned off the built-in firewall of Windows), I would assume this is the problem.
ping6 tracert6 works visit ipv6 sites work not
![[no]](/s/countries/no.gif) Shadow Hawkins on Saturday, 11 September 2004 10:38:24
Do you get this problem with more than one browser? You don't mention which browser you use. Since pinging works, and your firewall is off this should work, so try with another browser (I reccomend firefox) and see if that helps.
ping6 tracert6 works visit ipv6 sites work not
Shadow Hawkins on Saturday, 11 September 2004 10:49:21
I don't use a proxy server.
My provider is @home in the Netherlands I use only the tunnel from surfnet.
I've tried with internet explorer 6 and mozilla Firefox. But with both I can't visit ipv6 sites
I have also tried with nt6tunnel to make a connection with newszilla6.xs4all.nl but this work also not.
ping6 tracert6 works visit ipv6 sites work not
Shadow Hawkins on Saturday, 11 September 2004 16:09:02
Exactly the same problem here! I have two heartbeat tunnels, one from Scarlet and one from SurfNet. When I use the Scarlet tunnel, everything works fine. When I use the SurfNet tunnel, I can only ping6 and traceroute6, but that's as far as it goes; SSH or HTTP doesn't do anything. This leads me to believe that something is wrong with the SurfNet POP.
ping6 tracert6 works visit ipv6 sites work not
Shadow Hawkins on Saturday, 11 September 2004 17:16:47
I've send a email to sixxs to request more credits. So I can make a tunnel with scarlet.
I hope that the scarlet tunnel works.
ping6 tracert6 works visit ipv6 sites work not
Shadow Hawkins on Saturday, 11 September 2004 18:11:07
Here's an interesting bit of info; it's a traceroute from a machine on the Scarlet tunnel to a machine on the SurfNet tunnel:
1 11 ms 12 ms 9 ms update.your.resolver.ip6.int.is.deprecated.served.from.sixxs.net [2001:960:2:31d::1]
2 10 ms 12 ms 12 ms ge-0-5-800.juniper-1.ipv6.sc-network.nl [2001:960:800::1]
3 * * * Time-out bij opdracht.
4 12 ms 9 ms 10 ms Gi10-3.AR5.Amsterdam1.surf.net [2001:610:14:160::161]
5 17 ms 12 ms 17 ms Gi5-1.SW14.Amsterdam1.surf.net [2001:610:14:160::162]
6 9 ms 9 ms 12 ms Gi5-1.SW14.Amsterdam1.surf.net [2001:610:14:160::162]
7 11 ms 11 ms 9 ms sixxs.surtnet.nl [2001:610:1:80bb:192:87:102:107]
8 26 ms 27 ms 24 ms update.your.resolver.ip6.int.is.deprecated.served.from.sixxs.net [2001:610:600:1a::2]
What struck me is that hop 7 translates to sixxs.surTnet.nl. Shouldn't this be sixxs.surFnet.nl? I have no idea how, but could this typo explain some of the trouble we seem to be having with the SurfNet POP?
For what it's worth, here's the traceroute the other way around (from Surfnet to Scarlet):
traceroute to laszlo.vdhoek.nl.eu.org (2001:960:2:31d::2), 30 hops max, 40 byte packets
1 gw-27.ams-05.nl.sixxs.net (2001:610:600:1a::1) 13.827 ms 15.568 ms 15.435 ms
2 vl163.sw14.amsterdam1.surf.net (2001:610:1:80bb:192:87:102:97) 16.103 ms 18.320 ms 16.587 ms
3 Gi10-3.AR5.Amsterdam1.surf.net (2001:610:14:160::161) 17.062 ms 16.435 ms 16.941 ms
4 Lo0.BR2.Amsterdam1.surf.net (2001:610:25:5039::39) 150.610 ms 150.880 ms 151.309 ms
5 broker04.ams.nl.sixxs.net (2001:960:800::2) 21.336 ms 20.883 ms 21.538 ms
6 cl-798.ams-04.nl.sixxs.net (2001:960:2:31d::2) 31.882 ms * *
7 * * *
8 * * *
9 * * *
.
.
.
...but ping6-ing does work:
PING vdhoek.nl.eu.org(cl-27.ams-05.nl.sixxs.net) 56 data bytes
64 bytes from cl-27.ams-05.nl.sixxs.net: icmp_seq=1 ttl=64 time=0.075 ms
64 bytes from cl-27.ams-05.nl.sixxs.net: icmp_seq=2 ttl=64 time=0.056 ms
64 bytes from cl-27.ams-05.nl.sixxs.net: icmp_seq=3 ttl=64 time=0.049 ms
.
.
.
Also, a traceroute to another IPv6 host, xs6.xs4all.nl, does complete:
traceroute to xs6.xs4all.nl (2001:888:0:1::666), 30 hops max, 40 byte packets
1 gw-27.ams-05.nl.sixxs.net (2001:610:600:1a::1) 14.558 ms 14.425 ms 15.446 ms
2 vl163.sw14.amsterdam1.surf.net (2001:610:1:80bb:192:87:102:97) 15.738 ms 16.004 ms 17.272 ms
3 Gi10-3.AR5.Amsterdam1.surf.net (2001:610:14:160::161) 16.180 ms 16.613 ms 15.085 ms
4 * * *
5 2001:610:16:6056::58 15.012 ms 15.768 ms 17.687 ms
6 2001:610:16:6056::58 18.449 ms 18.304 ms 18.215 ms
7 2001:888:0:1105::1 18.769 ms 19.403 ms 19.397 ms
8 xs6.xs4all.nl (2001:888:0:1::666) 19.124 ms 20.497 ms 20.722 ms
ping6 tracert6 works visit ipv6 sites work not
Shadow Hawkins on Saturday, 11 September 2004 19:31:52
a traceroute to sixxs.surfnet.nl gives also al route to sixxs.surtnet.nl
Tracing route to sixxs.surfnet.nl [2001:610:1:80bb:192:87:102:107]
from 2001:610:600:1c::2 over a maximum of 30 hops:
1 15 ms 19 ms 13 ms sixxs.surtnet.nl [2001:610:1:80bb:192:87:102:
107]
strange
|
Posting is only allowed when you are