Ticket ID: SIXXS #14009685 Ticket Status: User PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)
Tunnel Uptime showing as "0 days"
Shadow Hawkins on Wednesday, 29 July 2015 18:45:44
Hi,
My tunnel uptime is always showing 0 days:
Tunnel Information for T166409
The configuration for this tunnel looks like:
Tunnel NameMy First Tunnel
PoP Nameusqas01
PoP LocationAshburn, Virginia, United States United States
PoP IPv466.117.47.228
TIC Servertic.sixxs.net (default in AICCU)
Your LocationFallston, United States United States
Your IPv4AYIYA, currently 71.121.176.154
IPv6 Prefix2001:4830:1600:545::1/64
PoP IPv62001:4830:1600:545::1
Your IPv62001:4830:1600:545::2
Created2015-05-21 13:04:40 UTC
Last Alivenever
Last Dead2015-07-29 01:15:01 UTC
Uptime 0 days (based on latency check)
Config StateAYIYA (automatically enabled on the fly)
PoP StatusLive Tunnel Status on the PoP
The tunnel is up, I have been using it (I added IPvFoo to chrome and it shows that I get the IPv6 version of the Google search page). However; the status page here always shows 0 days uptime. I checked the Windows advanced firewall and it shows the rule that was added to allow the IPv6 Ping. What else should I check to get past day zero?
Thanks,
Tom
State change: user
Jeroen Massar on Wednesday, 29 July 2015 20:10:16
The state of this ticket has been changed to user
Tunnel Uptime showing as "0 days"
Jeroen Massar on Wednesday, 29 July 2015 20:12:15 Last Alivenever
Clearly shows that it never was considered up.
The tunnel is up, I have been using it (I added IPvFoo to chrome and it shows that I get the IPv6 version of the Google search page).
That might mean you have connectivity, not that it satisfies that the connection is actually up.
What else should I check to get past day zero?
Read the FAQ on the subject. There is a link under the "latency check" that points to it, though searching for 'ping' on the FAQ page also clarifies it.
Tunnel Uptime showing as "0 days"
Shadow Hawkins on Wednesday, 29 July 2015 20:50:13
Jeroen Massar wrote:
> Last Alivenever
Clearly shows that it never was considered up.
I installed using AICCU. That did not allow the PING into the firewall (there are no other instructions under the "automated" installation about allowing the PING through the firewall.
Under the manual installation instructions it says to use:
netsh firewall set icmpsetting SixXS enable all
This doesn't work on Windows 7. After some searching on the internet, I finally found the following command which does allow the ping to start working:
netsh advfirewall firewall add rule name="All ICMP V6" dir=in action=allow protocol=icmpv6
The FAQ needs to be updated to reflect that the automatic install doesn't allow the ping and the manual instructions have the command incorrect.
The tunnel is up, I have been using it (I added IPvFoo to chrome and it shows that I get the IPv6 version of the Google search page).
That might mean you have connectivity, not that it satisfies that the connection is actually up.
What else should I check to get past day zero?
Read the FAQ on the subject. There is a link under the "latency check" that points to it, though searching for 'ping' on the FAQ page also clarifies it.
Tunnel Uptime showing as "0 days"
Jeroen Massar on Wednesday, 29 July 2015 22:43:25 I installed using AICCU.
AICCU on Windows enables IPv6 pings in the firewall rules.
aiccu_exec("netsh advfirewall firewall add rule name=\"%s\" "
"protocol=icmpv6:any,any "
"dir=in action=allow",
rulename);
But if the OS has other rules or configurations, the above might not be sufficient.
Something for you to configure, AICCU cannot solve everything.
Posting is only allowed when you are logged in. |