SixXS::Sunset 2017-06-06

IPv6 partially functioning
[br] Shadow Hawkins on Friday, 23 September 2011 00:25:17
My Username: WJDOJ1-SIXXS My Tunnel: T62865 OS: Windows 7 x64 SP1 Language OS: Portuguese (Brazil) Antivirus\Firewall: Norton Internet Security v18.6.0.29 Wireless Internet Service Provider on NAT (I think) My computer accesses the "ipv6.google.com" but does not access some other sites in IPv6. The "test-ipv6.com" informs me that I have no IPv6 address. The site "www.ipv6.sixxs.net" works!
aiccu autotest >aiccu.log
Tunnel Information for T62865: PoP Id : brudi01 IPv6 Local : 2001:1291:200:195::2/64 IPv6 Remote : 2001:1291:200:195::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : My First Tunnel ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.6.81) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack Disparando 192.168.6.81 com 32 bytes de dados: Resposta de 192.168.6.81: bytes=32 tempo<1ms TTL=128 Resposta de 192.168.6.81: bytes=32 tempo<1ms TTL=128 Resposta de 192.168.6.81: bytes=32 tempo<1ms TTL=128 Estatisticas do Ping para 192.168.6.81: Pacotes: Enviados = 3, Recebidos = 3, Perdidos = 0 (0% de perda), Aproximar um numero redondo de vezes em milissegundos: Minimo = 0ms, Maximo = 0ms, Media = 0ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (201.48.254.14) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur Disparando 201.48.254.14 com 32 bytes de dados: Resposta de 201.48.254.14: bytes=32 tempo=249ms TTL=50 Resposta de 201.48.254.14: bytes=32 tempo=593ms TTL=50 Resposta de 201.48.254.14: bytes=32 tempo=519ms TTL=50 Estatisticas do Ping para 201.48.254.14: Pacotes: Enviados = 3, Recebidos = 3, Perdidos = 0 (0% de perda), Aproximar um numero redondo de vezes em milissegundos: Minimo = 249ms, Maximo = 593ms, Media = 453ms ###### ####### [3/8] Traceroute to the PoP (201.48.254.14) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem Rastreando a rota para brudi01.sixxs.net [201.48.254.14] com no maximo 30 saltos: 1 600 ms 248 ms 177 ms 192.168.6.1 2 1134 ms 1893 ms 565 ms 192.168.0.1 3 127 ms 58 ms 10 ms 189.53.73.97 4 * 682 ms 639 ms 187.28.234.217 5 791 ms 629 ms 460 ms ebt-G0-1-dist02.pvo.embratel.net.br [200.230.159.70] 6 336 ms 87 ms 102 ms ebt-G6-2-dist05.gna.embratel.net.br [200.230.159.38] 7 77 ms 93 ms 83 ms ebt-T0-4-2-0-tcore02.bhe.embratel.net.br [200.244.160.14] 8 423 ms 367 ms 211 ms ebt-T0-5-0-0-tcore01.spoph.embratel.net.br [200.230.251.54] 9 65 ms 67 ms 66 ms ebt-C1-gacc01.spomb.embratel.net.br [200.230.242.129] 10 88 ms 71 ms 62 ms peer-C11-gacc01.spomb.embratel.net.br [200.211.219.10] 11 325 ms 355 ms 661 ms xe-3-2-0-0.core-b.spo511.ctbc.com.br [201.48.44.209] 12 89 ms 87 ms 102 ms xe-3-0-0-0.core-b.ula001.ctbc.com.br [201.48.44.13] 13 469 ms * 107 ms ge-1-0-0-0.edge-b.ula001.ctbc.com.br [201.48.44.70] 14 767 ms 825 ms 1551 ms brudi01.sixxs.net [201.48.254.14] Rastreamento concluido. ###### ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack Disparando ::1 com 32 bytes de dados: Resposta de ::1: tempo<1ms Resposta de ::1: tempo<1ms Resposta de ::1: tempo<1ms Estatisticas do Ping para ::1: Pacotes: Enviados = 3, Recebidos = 3, Perdidos = 0 (0% de perda), Aproximar um numero redondo de vezes em milissegundos: Minimo = 0ms, Maximo = 0ms, Media = 0ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1291:200:195::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Disparando 2001:1291:200:195::2 com 32 bytes de dados: Resposta de 2001:1291:200:195::2: tempo<1ms Resposta de 2001:1291:200:195::2: tempo<1ms Resposta de 2001:1291:200:195::2: tempo<1ms Estatisticas do Ping para 2001:1291:200:195::2: Pacotes: Enviados = 3, Recebidos = 3, Perdidos = 0 (0% de perda), Aproximar um numero redondo de vezes em milissegundos: Minimo = 0ms, Maximo = 0ms, Media = 0ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1291:200:195::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall (both IPv4 and IPv6) of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem Disparando 2001:1291:200:195::1 com 32 bytes de dados: Resposta de 2001:1291:200:195::1: tempo=200ms Resposta de 2001:1291:200:195::1: tempo=193ms Resposta de 2001:1291:200:195::1: tempo=94ms Estatisticas do Ping para 2001:1291:200:195::1: Pacotes: Enviados = 3, Recebidos = 3, Perdidos = 0 (0% de perda), Aproximar um numero redondo de vezes em milissegundos: Minimo = 94ms, Maximo = 200ms, Media = 162ms ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. ###### ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 ###### ###### ACCU Quick Connectivity Test (done) ### Either the above all works and gives no problems ### or it shows you where what goes wrong ### Check the SixXS FAQ (http://www.sixxs.net/faq/ ### for more information and possible solutions or hints ### Don't forget to check the Forums (http://www.sixxs.net/forum/) ### for a helping hand. ### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
This did not appear in the log (I think it is a bug in the program commands): Portuguese (Original):
'tracert6' nao e reconhecido como um comando interno ou externo, um programa operavel ou um arquivo em lotes. 'tracert6' nao e reconhecido como um comando interno ou externo, um programa operavel ou um arquivo em lotes.
English (Translated):
'tracert6' is not recognized as an internal command or external, operable program or batch file. 'tracert6' is not recognized as an internal command or external, operable program or batch file.
IPv6 partially functioning
[ch] Jeroen Massar SixXS Staff on Friday, 23 September 2011 10:53:33
See the wiki, the trick is to add a valid IPv6 address to one of your Ethernet connected network adapters, then the resolver suddenly does resolve IPv6 addresses in addition to IPv4 addresses.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker