I can't seem to find any issue on my end. Set as DMZ in the modem's firewall. I'm hoping that maybe there is something on the PoP end. tunnel_id T82882, using AYIYA will$ ifconfig tun0 tun0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1280 inet6 fe80::223:32ff:fea1:11b1%tun0 prefixlen 64 scopeid 0xa inet6 2607:f878:ff00:1::2 --> 2607:f878:ff00:1::1 prefixlen 128 open (pid 373) Note: Testing from one of my WiMax modems which is why the latency is high. aiccu autotest Tunnel Information for T82882: POP Id : usmia01 IPv6 Local : 2607:f878:ff00:1::2/64 IPv6 Remote : 2607:f878:ff00:1::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled add net default: gateway 2607:f878:ff00:1::1 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.15.24) ### 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 PING 192.168.15.24 (192.168.15.24): 56 data bytes 64 bytes from 192.168.15.24: icmp_seq=0 ttl=64 time=0.070 ms 64 bytes from 192.168.15.24: icmp_seq=1 ttl=64 time=0.054 ms 64 bytes from 192.168.15.24: icmp_seq=2 ttl=64 time=0.117 ms --- 192.168.15.24 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.054/0.080/0.117/0.027 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (184.22.119.138) ### 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 PING 184.22.119.138 (184.22.119.138): 56 data bytes 64 bytes from 184.22.119.138: icmp_seq=0 ttl=52 time=141.773 ms 64 bytes from 184.22.119.138: icmp_seq=1 ttl=52 time=149.170 ms 64 bytes from 184.22.119.138: icmp_seq=2 ttl=52 time=148.378 ms --- 184.22.119.138 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 141.773/146.440/149.170/3.316 ms ###### ####### [3/8] Traceroute to the PoP (184.22.119.138) 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 traceroute to 184.22.119.138 (184.22.119.138), 64 hops max, 52 byte packets 1 192.168.15.1 (192.168.15.1) 6.622 ms 7.331 ms 9.994 ms 2 * * * 3 10.41.193.169 (10.41.193.169) 117.763 ms 89.382 ms 115.145 ms 4 66-233-236-161.wsh.clearwire-wmx.net (66.233.236.161) 130.210 ms 155.193 ms 129.523 ms 5 te-8-2.car1.baltimore1.level3.net (4.59.244.17) 104.666 ms 300.520 ms 269.602 ms 6 ae-11-11.car2.baltimore1.level3.net (4.69.134.110) 284.633 ms 197.057 ms 346.045 ms 7 ae-8-8.ebr2.washington1.level3.net (4.69.134.105) 44.350 ms 238.318 ms 79.407 ms 8 ae-92-92.csw4.washington1.level3.net (4.69.134.158) 160.554 ms 197.548 ms ae-82-82.csw3.washington1.level3.net (4.69.134.154) 185.290 ms 9 ae-41-80.car1.washington3.level3.net (4.69.149.140) 99.817 ms ae-21-60.car1.washington3.level3.net (4.69.149.12) 95.594 ms 84.187 ms 10 xo-communic.car1.washington3.level3.net (4.71.204.26) 94.767 ms 59.684 ms 74.682 ms 11 216.156.116.94.ptr.us.xo.net (216.156.116.94) 53.968 ms 120.188 ms 95.138 ms 12 3-1.r1.at.hwng.net (69.16.191.126) 85.239 ms 804.842 ms 170.265 ms 13 3-1.r1.mi.hwng.net (209.197.0.210) 139.154 ms 104.671 ms 175.197 ms 14 unknown.hwng.net (205.185.198.130) 134.763 ms 155.031 ms 128.260 ms 15 unknown.hwng.net (205.185.198.134) 516.748 ms 254.965 ms 148.774 ms 16 ec0-63.1a0201.mifl01.hostnoc.net (64.120.243.134) 124.855 ms 125.929 ms 113.749 ms 17 usmia01.sixxs.net (184.22.119.138) 125.155 ms 249.783 ms 179.691 ms ###### ###### [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 PING6(56=40+8+8 bytes) ::1 --> ::1 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=0 hlim=64 dst=::1 time=0.189 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1 time=0.222 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1 time=0.434 ms --- ::1 ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.189/0.282/0.434/0.109 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2607:f878:ff00:1::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING6(56=40+8+8 bytes) 2607:f878:ff00:1::2 --> 2607:f878:ff00:1::2 --- 2607:f878:ff00:1::2 ping6 statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2607:f878:ff00:1::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 of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem PING6(56=40+8+8 bytes) 2607:f878:ff00:1::2 --> 2607:f878:ff00:1::1 --- 2607:f878:ff00:1::1 ping6 statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss ###### ###### [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. traceroute6 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2607:f878:ff00:1::2, 64 hops max, 12 byte packets 1 * *^C ###### ###### [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 traceroute6 to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2607:f878:ff00:1::2, 64 hops max, 12 byte packets ^C ###### ###### ACCU Quick Connectivity Test (done) Thanks!