|
Ticket ID: SIXXS #1237732 Ticket Status: User PoP: frmrs01 - Jaguar Network SARL (Marseille)
https://www.sixxs.net not responding for its IPv6 address
![[fr]](/s/countries/fr.gif) Shadow Hawkins on Friday, 23 October 2009 20:18:52
Hi,
I do not have yet a subnet with associated to my SixXS account (only 4 days since I have a tunnel) but I already setup a 6to4 tunnel.
So, with this tunnel, IPv6 seems working (I'm seeing goggle waving on http://ipv6.google.com for example). However, https://www.sixxs.net does not seems to work.
Looking at TCP traces, I see that my navigator try to use your IPv6 server first (2001:838:1:1:210:dcff:fe20:7c7c) and when a timeout occurs, it switch to one of the two IPv4 and then got the web page.
Can you check if your IPv6 server is up or remove the IPv6 address for www.sixxs.net in the DNS ?
Regards,
Vincent Danjean
State change: user
The state of this ticket has been changed to user
https://www.sixxs.net not responding for its IPv6 address
The webserver is working fine, just like it always did.
It would be useful if you would at least try to provide a source address and what about those traceroutes?
Also, if your traceroute does complete, check that your pMTU is correct (tracepath6 on Linux is very useful for that).
Last resort always: wireshark/tcpdump it.
https://www.sixxs.net not responding for its IPv6 address
Shadow Hawkins on Friday, 23 October 2009 22:22:08
Hi,
Here are my experiment on your web site and on the google web site.
My local IP for these tests is 2002:58ac:8494::1
It seems that my packets are not routed correctly to your web site
(whereas they go to other IPv6 routers with 2001:: prefix)
Is there more tests I can do ?
kooot:~# host www.sixxs.net
www.sixxs.net is an alias for www.m.sixxs.net.
www.m.sixxs.net has address 213.204.193.2
www.m.sixxs.net has address 193.109.122.244
www.m.sixxs.net has IPv6 address 2001:838:1:1:210:dcff:fe20:7c7c
kooot:~# traceroute6 2001:838:1:1:210:dcff:fe20:7c7c
traceroute to 2001:838:1:1:210:dcff:fe20:7c7c (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 port0v6.gr10.eqqas.us.easynet.net (2001:504:0:2::4589:1) 131.285 ms * *
6 2001:6f8:1:0:87:86:77:106 (2001:6f8:1:0:87:86:77:106) 136.099 ms 110.980 ms 110.807 ms
7 2001:6f8:1:0:87:86:77:104 (2001:6f8:1:0:87:86:77:104) 121.396 ms 117.090 ms 111.712 ms
8 2001:6f8:1:0:87:86:77:110 (2001:6f8:1:0:87:86:77:110) 180.922 ms 180.126 ms 178.743 ms
9 2001:6f8:1:0:87:86:77:121 (2001:6f8:1:0:87:86:77:121) 195.539 ms * 178.455 ms
10 2001:6f8:1:0:87:86:77:29 (2001:6f8:1:0:87:86:77:29) 187.584 ms 187.111 ms 186.950 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
kooot:~# host ipv6.google.com
ipv6.google.com is an alias for ipv6.l.google.com.
ipv6.l.google.com has IPv6 address 2001:4860:a005::68
kooot:~# traceroute6 2001:4860:a005::68
traceroute to 2001:4860:a005::68 (2001:4860:a005::68), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 ey-in-x68.1e100.net (2001:4860:a005::68) 78.277 ms 78.613 ms 72.500 ms
kooot:~# tracepath6 2001:838:1:1:210:dcff:fe20:7c7c
1?: [LOCALHOST] pmtu 1480
1: no reply
2: no reply
3: no reply
4: no reply
5: port0v6.gr10.eqqas.us.easynet.net 129.024ms asymm 4
6: 2001:6f8:1:0:87:86:77:106 128.060ms asymm 3
7: 2001:6f8:1:0:87:86:77:104 127.008ms asymm 3
8: 2001:6f8:1:0:87:86:77:110 194.634ms asymm 4
9: 2001:6f8:1:0:87:86:77:121 194.119ms asymm 5
10: 2001:6f8:1:0:87:86:77:29 202.691ms asymm 6
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1480
Resume: pmtu 1480
kooot:~# tracepath6 2001:4860:a005::68
1?: [LOCALHOST] pmtu 1480
1: no reply
2: no reply
3: no reply
4: no reply
5: 2001:4860:1:1:0:3022:0:5 79.795ms !A
Resume: pmtu 1480
kooot:~#
https://www.sixxs.net not responding for its IPv6 address
My local IP for these tests is 2002:58ac:8494::1
Which is 6to4, sorry, but we are not going to debug that, it is near impossible.
And as you can see from your traceroutes yourself, several hops don't even respond to ICMP for the traceroute.
You claim to have a 1480 MTU path, I am very sure that is not the case. Try setting it to 1280 you will have a lot more success if you want to use 6to4.
Can we suggest that you get get real connectivity instead of 6to4!?
https://www.sixxs.net not responding for its IPv6 address
Shadow Hawkins on Friday, 23 October 2009 22:49:24
Setting my MTU to does not change anything (both for the traceroute6 and the tracepath6 except the reported value of pmtu).
I was thinking at first that your IPv6 website was down but now, I think there is a problem somewhere in routers about 6to4 address (and you probably cannot do anything about it).
About getting a real connectivity instead of 6to4, I requested and setup a SixXS tunnel 4 days ago. I'm waiting (probably still 3 days) to get 5 more ISK to ask for a prefix and get a real connectivity ;-)
Regards,
Vincent
https://www.sixxs.net not responding for its IPv6 address
![[de]](/s/countries/de.gif) Shadow Hawkins on Wednesday, 28 October 2009 21:30:58
Did you try http://www.sixxs.net/ (HTTP instead of HTTPS)? I had the problem that most IPv6 addresses worked fine, but the SixXs website didnt work with HTTPS (the browser always switched back to v4 after the TCP timeout). It turned out later that I was blocking inbound traffic for port 443 at the gateway to my LAN.
Regards,
Markus
|
![[ch]](/s/countries/ch.gif)
on Friday, 23 October 2009 20:39:27
Posting is only allowed when you are