SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #789308
Ticket Status: User

PoP: nlams05 - SURFnet (Amsterdam)

[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint fails
[nl] Shadow Hawkins on Thursday, 21 August 2008 15:34:09
As you might have noticed in the forum (link1) I am quite a noob concerning IPv6, however I whish to give it a go. I used this guide link2 to set the thing up. However pings keep timing out. Here a copy paste of aiccu's autotest: sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs .net)" sock_printf() : "client TIC/draft-00 AICCU/2008.03.15-console-win32 WinNT/6.0.6 001-SP1" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1219316729" sock_printf() : "username FDV1-SIXXS" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 e5678e7c6e54781772ce8811aa7cb518" sock_printf() : "authenticate md5 805b63d3f6da258be6508c90390a3856" sock_getline() : "200 Succesfully logged in using md5 as FDV1-SIXXS (Flex Desaub in) from 2001:7b8:3:4f:202:b3ff:fe46:bec" sock_printf() : "tunnel show T16502" sock_getline() : "201 Showing tunnel information for T16502" sock_getline() : "TunnelId: T16502" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:610:600:4ed::2" sock_getline() : "IPv6 POP: 2001:610:600:4ed::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: Desaubin tunnel" sock_getline() : "POP Id: nlams05" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 192.87.102.107" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: a25369daad9dcc13fb63af49c1f95023" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T16502 sock_printf() : "QUIT Nothing Comes Easy" Tunnel Information for T16502: PoP Id : nlams05 IPv6 Local : 2001:610:600:4ed::2/64 IPv6 Remote : 2001:610:600:4ed::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : Desaubin tunnel Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D 36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1) Found interface named 'aiccu', with guid {78D4D8E2-95C9-4EA1-B60F-C414167B25B1}, using it [tun-start] Trying \\.\Global\{78D4D8E2-95C9-4EA1-B60F-C414167B25B1}.tap Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [AYIYA-start] : Anything in Anything (draft-02) heartbeat_socket() - IPv4 : 192.168.1.2 [AYIYA-tun->tundev] : (Socket to TUN) started ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.2) ### 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 Pingen naar 192.168.1.2 met 32 bytes aan gegevens: Antwoord van 192.168.1.2: bytes=32 tijd<1 ms TTL=128 Antwoord van 192.168.1.2: bytes=32 tijd<1 ms TTL=128 Antwoord van 192.168.1.2: bytes=32 tijd<1 ms TTL=128 Ping-statistieken voor 192.168.1.2: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van �é�én bewerking in milliseconden: Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (192.87.102.107) ### 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 Pingen naar 192.87.102.107 met 32 bytes aan gegevens: Antwoord van 192.87.102.107: bytes=32 tijd=13 ms TTL=58 Antwoord van 192.87.102.107: bytes=32 tijd=12 ms TTL=58 Antwoord van 192.87.102.107: bytes=32 tijd=14 ms TTL=58 Ping-statistieken voor 192.87.102.107: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van �é�én bewerking in milliseconden: Minimum = 12ms, Maximum = 14ms, Gemiddelde = 13ms ###### ####### [3/8] Traceroute to the PoP (192.87.102.107) 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 Traceren van de route naar sixxs.surfnet.nl [192.87.102.107] via maximaal 30 hops: 1 <1 ms <1 ms <1 ms Desaubin Gateway [192.168.1.1] 2 14 ms 13 ms 13 ms ip5362fc01.speedxs.nl [83.98.252.1] 3 12 ms 11 ms 12 ms edge-1-vl816.nkf.as30925.net [83.98.224.18] 4 13 ms 12 ms 12 ms XSR03.Asd001A.surf.net [195.69.144.50] 5 12 ms 12 ms 13 ms ae2.500.jnr01.asd001a.surf.net [145.145.80.78] 6 12 ms 12 ms 12 ms v1105.sw14.amsterdam1.surf.net [145.145.18.94] 7 13 ms 13 ms 12 ms sixxs.surfnet.nl [192.87.102.107] De trace is voltooid. ###### ###### [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 Pingen naar ::1 van ::1 met 32 bytes aan gegevens: Antwoord van ::1: tijd<1 ms Antwoord van ::1: tijd<1 ms Antwoord van ::1: tijd<1 ms Ping-statistieken voor ::1: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van �é�én bewerking in milliseconden: Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:610:600:4ed::2 ) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pingen naar 2001:610:600:4ed::2 van 2001:610:600:4ed::2 met 32 bytes aan gegeven s: Antwoord van 2001:610:600:4ed::2: tijd<1 ms Antwoord van 2001:610:600:4ed::2: tijd<1 ms Antwoord van 2001:610:600:4ed::2: tijd<1 ms Ping-statistieken voor 2001:610:600:4ed::2: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van �é�én bewerking in milliseconden: Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:610:600:4ed::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 Pingen naar 2001:610:600:4ed::1 van 2001:610:600:4ed::2 met 32 bytes aan gegeven s: Time-out bij opdracht. Time-out bij opdracht. Time-out bij opdracht. Ping-statistieken voor 2001:610:600:4ed::1: Pakketten: verzonden = 3, ontvangen = 0, verloren = 3 (100% verlies). ###### ###### [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 connecti on ### If your browser supports IPv6 and uses it of course. tracert6 wordt niet herkend als een interne of externe opdracht, programma of batchbestand. ###### ###### [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 tracert6 wordt niet herkend als een interne of externe opdracht, programma of batchbestand. ###### ###### 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. Tracert6 is unknown because of the Vista platform. I have currently no firewall/anti-virus software installed. My Vista machine is behind a Linksys RV042 router.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 21 August 2008 15:34:31
Message is Locked
The state of this ticket has been changed to user
[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint fails
[ch] Jeroen Massar SixXS Staff on Thursday, 21 August 2008 15:35:46
Which TUN/TAP driver did you install, and also what are the other tunnels/interfaces/routes that you have? Please read up on the "Reporting Problems" section of the contact page and provide those details.
[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint fails
[nl] Shadow Hawkins on Thursday, 21 August 2008 17:36:02
Thank you for you reply. I am using tap32 driver version 901. If I understand your question correctly, this is the info you requested: Tunnel Name Desaubin tunnel PoP Name nlams05 PoP Location Amsterdam, Netherlands, The PoP IPv4 192.87.102.107 Your Location Arnhem, Netherlands, The Your IPv4 AYIYA, currently 83.98.248.173 IPv6 Prefix 2001:610:600:4ed::1/64 PoP IPv6 2001:610:600:4ed::1 Your IPv6 2001:610:600:4ed::2 Created 2008-08-13 10:25:27 CEST State AYIYA (automatically enabled on the fly)
[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint fails
[ch] Jeroen Massar SixXS Staff on Thursday, 21 August 2008 17:43:40
I am using tap32 driver version 901.
That is good, as that is the only one that works. The information you pasted we have, we want to see information from the "netsh" command though: netsh int ipv6 show interface level=verbose netsh int ipv6 show route And other information requested on the checklist is always welcome. You might just want to try a 'netsh int ipv6 reset', reboot your computer, and then try AICCU again as another/quicker option/try.
[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint fails
[nl] Shadow Hawkins on Thursday, 21 August 2008 21:21:31
Microsoft Windows [versie 6.0.6001] Copyright (c) 2006 Microsoft Corporation. Alle rechten voorbehouden. d:\>netsh int ipv6 show interface level=verbose Interface Loopback Pseudo-Interface 1 Parameters ---------------------------------------------- IfLuid : loopback_0 IfIndex : 1 Compartiment-id : 1 Status : connected Metric : 50 Verbindings-MTU : 4294967295 bytes Bereikbare tijd : 44000 ms Basis voor bereikbare tijd : 30000 ms Herverzendingsinterval : 1000 ms DAD-verzendingen : 0 Lengte site-voorvoegsel : 64 Site-id : 1 Doorsturen : disabled Adverteren : disabled Neighbor-detectie : disabled Detectie onbereikbaarheid neighbor : disabled Router-detectie : enabled Beheerde adresconfiguratie : disabled Andere stateful-configuratie : disabled Zwakke host verzendt : disabled Zwakke host ontvangt : disabled Automatische metriek gebruiken : enabled Standaardroutes negeren : disabled Interface LAN-verbinding* Parameters ---------------------------------------------- IfLuid : tunnel_2 IfIndex : 9 Compartiment-id : 1 Status : disconnected Metric : 10 Verbindings-MTU : 1280 bytes Bereikbare tijd : 36500 ms Basis voor bereikbare tijd : 30000 ms Herverzendingsinterval : 1000 ms DAD-verzendingen : 0 Lengte site-voorvoegsel : 64 Site-id : 1 Doorsturen : disabled Adverteren : disabled Neighbor-detectie : enabled Detectie onbereikbaarheid neighbor : enabled Router-detectie : enabled Beheerde adresconfiguratie : disabled Andere stateful-configuratie : disabled Zwakke host verzendt : disabled Zwakke host ontvangt : disabled Automatische metriek gebruiken : enabled Standaardroutes negeren : disabled Interface LAN-verbinding* 2 Parameters ---------------------------------------------- IfLuid : tunnel_3 IfIndex : 16 Compartiment-id : 1 Status : disconnected Metric : 50 Verbindings-MTU : 1280 bytes Bereikbare tijd : 33000 ms Basis voor bereikbare tijd : 30000 ms Herverzendingsinterval : 1000 ms DAD-verzendingen : 0 Lengte site-voorvoegsel : 64 Site-id : 1 Doorsturen : disabled Adverteren : disabled Neighbor-detectie : disabled Detectie onbereikbaarheid neighbor : disabled Router-detectie : enabled Beheerde adresconfiguratie : disabled Andere stateful-configuratie : disabled Zwakke host verzendt : disabled Zwakke host ontvangt : disabled Automatische metriek gebruiken : enabled Standaardroutes negeren : disabled Interface LAN-verbinding Parameters ---------------------------------------------- IfLuid : ethernet_4 IfIndex : 8 Compartiment-id : 1 Status : connected Metric : 20 Verbindings-MTU : 1500 bytes Bereikbare tijd : 38500 ms Basis voor bereikbare tijd : 30000 ms Herverzendingsinterval : 1000 ms DAD-verzendingen : 1 Lengte site-voorvoegsel : 64 Site-id : 1 Doorsturen : disabled Adverteren : disabled Neighbor-detectie : enabled Detectie onbereikbaarheid neighbor : enabled Router-detectie : enabled Beheerde adresconfiguratie : disabled Andere stateful-configuratie : disabled Zwakke host verzendt : disabled Zwakke host ontvangt : disabled Automatische metriek gebruiken : enabled Standaardroutes negeren : disabled Interface LAN-verbinding* 14 Parameters ---------------------------------------------- IfLuid : tunnel_5 IfIndex : 19 Compartiment-id : 1 Status : disconnected Metric : 50 Verbindings-MTU : 1280 bytes Bereikbare tijd : 18000 ms Basis voor bereikbare tijd : 30000 ms Herverzendingsinterval : 1000 ms DAD-verzendingen : 0 Lengte site-voorvoegsel : 64 Site-id : 1 Doorsturen : disabled Adverteren : disabled Neighbor-detectie : disabled Detectie onbereikbaarheid neighbor : disabled Router-detectie : enabled Beheerde adresconfiguratie : disabled Andere stateful-configuratie : disabled Zwakke host verzendt : disabled Zwakke host ontvangt : disabled Automatische metriek gebruiken : enabled Standaardroutes negeren : disabled Interface aiccu Parameters ---------------------------------------------- IfLuid : ethernet_12 IfIndex : 17 Compartiment-id : 1 Status : connected Metric : 30 Verbindings-MTU : 1500 bytes Bereikbare tijd : 32000 ms Basis voor bereikbare tijd : 30000 ms Herverzendingsinterval : 1000 ms DAD-verzendingen : 1 Lengte site-voorvoegsel : 64 Site-id : 1 Doorsturen : disabled Adverteren : disabled Neighbor-detectie : enabled Detectie onbereikbaarheid neighbor : enabled Router-detectie : enabled Beheerde adresconfiguratie : disabled Andere stateful-configuratie : disabled Zwakke host verzendt : disabled Zwakke host ontvangt : disabled Automatische metriek gebruiken : enabled Standaardroutes negeren : disabled d:\>netsh int ipv6 show route Public. Type Met Voorvoegsel Idx Naam gateway/interface ------- -------- --- ------------------------ --- ------------------------ Ja Handmatig 256 ::/0 17 2001:610:600:4ed::1 Nee Handmatig 256 ::1/128 1 Loopback Pseudo-Interface 1 Nee Handmatig 256 2001:610:600:4ed::/64 17 aiccu Nee Handmatig 256 2001:610:600:4ed::2/128 17 aiccu Nee Handmatig 256 2002:81a8:102::/48 8 LAN-verbinding Nee Handmatig 256 2002:81a8:102::/128 8 LAN-verbinding Nee Handmatig 256 fe80::/64 9 LAN-verbinding* Nee Handmatig 256 fe80::/64 17 aiccu Nee Handmatig 256 fe80::/64 8 LAN-verbinding Nee Handmatig 256 fe80::100:7f:fffe/128 9 LAN-verbinding* Nee Handmatig 256 fe80::5efe:169.254.175.72/128 19 LAN-verbinding* 14 Nee Handmatig 256 fe80::5efe:192.168.1.2/128 16 LAN-verbinding* 2 Nee Handmatig 256 fe80::8c7e:6a4e:f1b7:af48/128 17 aiccu Nee Handmatig 256 fe80::a1f3:7cb4:696d:d5da/128 8 LAN-verbinding Nee Handmatig 256 ff00::/8 1 Loopback Pseudo-Interface 1 Nee Handmatig 256 ff00::/8 9 LAN-verbinding* Nee Handmatig 256 ff00::/8 17 aiccu Nee Handmatig 256 ff00::/8 8 LAN-verbinding I am sorry, but netsh int ipv6 reset, reboot and restart aiccu console did not help unfortunately
[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint fails
[ch] Jeroen Massar SixXS Staff on Thursday, 21 August 2008 21:33:06
Why do you have several interfaces named "tunnel_X"? Also, it seems 6to4 is still active, you can disable that with "netsh int ipv6 6to4 set state disabled", same for Teredo "netsh int ipv6 set teredo disable" The PoP btw doesn't see any valid AYIYA packets coming in from you. Are you behind a firewall maybe somewhere that blocks the packets out?
[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint fails
[nl] Shadow Hawkins on Friday, 22 August 2008 16:19:46
I don't know what you did, but all seems to be working fine now. Many thanks for your coöperation.

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker