SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1315584
Ticket Status: User

PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)

T24636 not working with aiccu
[us] Shadow Hawkins on Friday, 01 January 2010 08:44:22
Hello, I set up with AICCU (Version: 2006.07.23-gui-win32 tunnel T24636 to usqas01. Set the workstation to be "DMZ host" on my Linksys router. Tunnel does not seem to work, I am at a loss on how to proceed. I can ping -6 my locally assigned interface 2001:4830:.....::2, but cannot seem to reach the pop-end 2001:4830:.....::1. Tried with XPsp2 and VistaHome, same results. ipconfig shows aiccu tunnel is getting set up in XPsp2 system, but Vista does not show the aiccu tunnel at all (??) even though the GUI reports all the "right" information. It seems if I wait long enough (120 seconds? 600 seconds?) even the XPsp2 drops the aiccu tunnel setting(s). I can ping to 66.117.47.228 (pop ipv4 addr). I can traceroute to iad0-sixxs.hotnic.net [66.117.47.228] Tracing route to iad0-sixxs.hotnic.net [66.117.47.228] over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. <snip repeats> 13 * * * Request timed out. 14 23 ms 23 ms 22 ms iad0-sixxs.hotnic.net [66.117.47.228] Trace complete. Will try from another location (coffee shop) tomorrow. If aiccu does not work what are my options? Switching tunnel type to AIYIA requires more credits than I have at the moment, not sure how to get more unless the tunnel is actually up. Perhaps I can offer a clarification to the documentation to earn some credits: On the "Request tunnel" page, it mentions that the tunnel drops if no response is received in 120sec, but the heartbeat info page (FAQ?) indicates the tunnel drops if no heartbeat is received in 600sec, and the 120sec is the allowable timestamp offset (with reminder to use NTP to avoid getting too far off the right time). It seems the correction should be made to the tunnel request page to clarify that tunnels drop after 600sec without a response. Unfortunately my "request tunnel" option is disabled (insufficient credits) so I cannot confirm my recollection. Any suggestions would be welcome - thanks ! Shukong Ou (handle: soh2-sixxs) shukong@gmail.com
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Friday, 01 January 2010 11:40:11
Message is Locked
The state of this ticket has been changed to user
T24636 not working with aiccu
[ch] Jeroen Massar SixXS Staff on Friday, 01 January 2010 11:43:00
AICCU 2006.07.23-gui-win32 does not support the new TAP devices, this is mentioned on the download page, use the console edition instead. But it more seems that your local network is in such a horrible state that it will never allow any kind of tunneling. If ICMPv4 doesn't properly pass through, then IPv6 tunneling is not going to help either. As you are mentioning going to the local coffee shop, I also assume that you do not have any control over the local network, and for that matter you should not be starting a tunnel from that location in the first place.

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

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