SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #877657
Ticket Status: User

PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)

Tunnel setup problem.
[us] Carmen Sandiego on Saturday, 13 December 2008 17:22:14
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: BJ855-RIPE Recently unable to setup tunnle after about 3 mounths of flawless service. Was working until 12-11-2008, Wireshark shows UDP packets sent to the pop but nothing ever comes back. I know that this is behind NAT but Protocol 41 is forwared and has worked until now. Tunnle: T13114 OS: WIndows 2003 Ent. AICCU: aiccu-2008-03-15-windows-console.exe and aiccu-2006-07-23-windows-gui.exe Iv tried include everything i can think of if you need anything elsa let me know. Also I have a 2nd tunnle on request so I could trouble shoot with it but still wating. Thanks, Brandon Jackson Remote traceroute from route-server.he.net (This is with aiccu running)
route-server.he.net>traceroute 2001:4978:f:7::1 Type escape sequence to abort. Tracing the route to 2001:4978:F:7::1 1 2001:470:1FFF:3::2 0 msec 0 msec 0 msec 2 2001:470:0:44::3 4 msec 0 msec 12 msec 3 2001:470:0:2F::2 4 msec 4 msec 0 msec 4 2001:470:0:3C::2 60 msec 64 msec 60 msec 5 2001:470:0:7F::2 60 msec 60 msec 60 msec 6 2001:4978:1:400:202:B3FF:FEB4:5974 64 msec 64 msec 64 msec 7 2001:4978:1:400:202:B3FF:FEB4:5974 !H !H !H
Note the !H for host unreachable on the ::1 address.
Tracing route to sixxs.cx01.chi.bb.your.org [216.14.98.22] with TTL of 32: 1 0ms 0ms 0ms car5-port1.napshome.local [10.0.1.6] 2 9ms 9ms 9ms h1.96.90.75.dynamic.ip.windstream.net [75.90.96.1] 3 9ms 9ms 9ms h54.122.90.75.static.ip.windstream.net [75.90.122.54] 4 13ms 13ms 17ms h68.248.213.151.static.ip.windstream.net [151.213.248.6 8] 5 14ms 13ms 13ms h98.254.213.151.static.ip.windstream.net [151.213.254.9 8] 6 14ms 13ms 13ms te-3-2.car2.Atlanta2.Level3.net [4.71.254.13] 7 20ms 25ms 26ms ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62] 8 20ms 17ms 23ms ae-62-60.ebr2.Atlanta2.Level3.net [4.69.138.3] 9 33ms 38ms 42ms ae-3.ebr2.Chicago1.Level3.net [4.69.132.73] 10 33ms 33ms 33ms ae-23-56.car3.Chicago1.Level3.net [4.68.101.167] 11 34ms 33ms 71ms nlayer-level3-10ge.Chicago1.Level3.net [4.71.100.62] 12 34ms 34ms 33ms po2.ar1.ord1.us.nlayer.net [69.31.111.138] 13 34ms 34ms 33ms as19255.po1-107.ar1.ord1.us.nlayer.net [69.31.111.26] 14 34ms 35ms 34ms sixxs.cx01.chi.bb.your.org [216.14.98.22] Traceroute complete.
C:\Program Files\Support Tools>tracert uschi02.sixxs.net Tracing route to uschi02.sixxs.net [2001:4978:1:400:202:b3ff:feb4:59cb] over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. C:\Program Files\Support Tools>tracert 2001:4978:f:7::1 Tracing route to sixxs-tunnel-gw-uschi02.ipv6.napshome.local [2001:4978:f:7::1] over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out.
Pinging 2001:4978:f:7::1 from 2001:4978:f:7::2 with 32 bytes of data: Request timed out. Request timed out. Ping statistics for 2001:4978:f:7::1: Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
C:\>aiccu test 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/5.2.3 790-SP2" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1229177836" sock_printf() : "username BJ855-RIPE" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 ************************" sock_printf() : "authenticate md5 ***************************" sock_getline() : "200 Succesfully logged in using md5 as BJ855-RIPE (Brandon Jac kson) from 2001:960:800::2" sock_printf() : "tunnel show T13114" sock_getline() : "201 Showing tunnel information for T13114" sock_getline() : "TunnelId: T13114" sock_getline() : "Type: 6in4-heartbeat" sock_getline() : "IPv6 Endpoint: 2001:4978:f:7::2" sock_getline() : "IPv6 POP: 2001:4978:f:7::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1472" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: uschi02" sock_getline() : "IPv4 Endpoint: heartbeat" sock_getline() : "IPv4 POP: 216.14.98.22" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: ****************************" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T13114 sock_printf() : "QUIT Ajuuu paraplu" Tunnel Information for T13114: PoP Id : uschi02 IPv6 Local : 2001:4978:f:7::2/64 IPv6 Remote : 2001:4978:f:7::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled Name : My First Tunnel Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present heartbeat_socket() - IPv4 : 10.0.1.2 [HB] HEARTBEAT TUNNEL 2001:4978:f:7::2 sender 1229177838 de7f6c4a2bc9f6b76f77657 0868392ce [error] Tunnel Setup Failed
Interface 16: aiccu Addr Type DAD State Valid Life Pref. Life Address --------- ---------- ------------ ------------ --------------------- Manual Preferred infinite infinite 2001:4978:f:7::2 Link Preferred infinite infinite fe80::10:a00:102 Connection Name : aiccu GUID : {8636F413-25E0-31A7-A42F-49B717AB6BD2} State : Connected Metric : 1 Link MTU : 1472 bytes True Link MTU : 65515 bytes Current Hop Limit : 128 Reachable Time : 31s Base Reachable Time : 30s Retransmission Interval : 1s DAD Transmits : 1 DNS Suffix : Firewall : disabled Site Prefix Length : 48 bits Zone ID for Link : 16 Zone ID for Admin : 5 Zone ID for Site : 2 Uses Neighbor Discovery : No Sends Router Advertisements : No Forwards Packets : Yes Link-Layer Address : 10.0.1.2 Remote Link-Layer Address : 216.14.98.22
netsh interface ipv6>show routes Querying active state... Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- ---- ------------------------ --- --------------------- no Manual 1 2001:4978:f:7::/64 16 aiccu yes Manual 1 ::/0 16 2001:4978:f:7::1 yes Manual 0 2001:4978:103::/64 4 Local Area Connection
Tunnel setup problem.
[ch] Jeroen Massar SixXS Staff on Saturday, 13 December 2008 21:32:06
Note the !H for host unreachable on the ::1 address.
The "!H" is ambiguous as the version of this 'traceroute' tool is unknown and thus the exact meaning it has. But looking at the PoP, it indicates that it doesn't receive proper heartbeat messages from your endpoint, and then indeed the PoP does not enable the <tunnel>::1 address as the tunnel is down. You seem to have configured an MTU of 1472, is that really correct? Another note is that AICCU states at the end: "[error] Tunnel Setup Failed" You have several places to look for errors for.
Tunnel setup problem.
[us] Carmen Sandiego on Sunday, 14 December 2008 00:06:17
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: Ok just like Nathan (Ticket 877659) for no reason its now back up and running with no chages didn't even restart aiccu. You sure no one did anything? As for the MTU of 1472 its is correct 1480 being the Max for a ipv6 over ipv4 connection with a MTU of 1500 then minus the 8 for pppoe = a mtu of 1472 (1492 - 20 = 1472) and I setup Win 2003 for a MTU of 1472 on both interfaces (My "LAN" and "WAN") thus all ipv6 clients auto config for 1472 and it works fine. Well since its working now ill let you know if it happens again. p.s I shut down aiccu and did anouther "aiccu test" and again I got the same "[error] Tunnel Setup Failed" even though the the test setup the tunnle corectly and allowed for ipv6 connectivity, I even deleted the aiccu interface befor I ran the test to confirm and it went from no interface to a fully futional tunnle with the test still showing the same thing so not really sure whats up with it. Thanks, Brandon Jackson
Tunnel setup problem.
[us] Carmen Sandiego on Sunday, 14 December 2008 09:17:42
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: Ok I'm back to having the same problem again, My uschi02 tunnel (T13114) will not setup after being down for about 1hr with a new IP (Note: My Tunnel info page show the new ip from the heartbeat), I have connected to my new usdal01 tunnel (T18582) for the moment and it is working fine, any suggestions? Brandon Jackson
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 13 December 2008 21:32:10
Message is Locked
The state of this ticket has been changed to user

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

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