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: I am unable to ping my pop or send ping responses to anyone. tcpdump on my physical ethernet device shows that I am indeed sending IPv6 packets to my pop, but other users confirm that while I am sending an ICMP6 response, they are not recieving it. additionally, my IPv6 tunnel::1 endpoint does not respond when I send it a ping. tcpdump does confirm that packets are sent when I send a ping. root@routerkrieg:~# aiccu autotest sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)" sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console Linux/2.4.30" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1201640741" sock_printf() : "username CS3917-RIPE" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 CENSORED" sock_printf() : "authenticate md5 CENSORED" sock_getline() : "200 Succesfully logged in using md5 as CS3917-RIPE (Christopher Schlacta) from 69.62.232.46" sock_printf() : "tunnel show T14068" sock_getline() : "201 Showing tunnel information for T14068" sock_getline() : "TunnelId: T14068" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:4978:f:86::2" sock_getline() : "IPv6 POP: 2001:4978:f:86::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1428" sock_getline() : "Tunnel Name: New tunnel for Home Servers." sock_getline() : "POP Id: uschi02" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 216.14.98.22" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: CENSORED" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T14068 sock_printf() : "QUIT Aufwiedersehen" Tunnel Information for T14068: POP Id : uschi02 IPv6 Local : 2001:4978:f:86::2/64 IPv6 Remote : 2001:4978:f:86::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started heartbeat_socket() - IPv4 : 69.62.232.46 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (69.62.232.46) ### 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 BusyBox v1.00 (2007.01.30-11:42+0000) multi-call binary Usage: ping [OPTION]... host Send ICMP ECHO_REQUEST packets to network hosts. Options: -c COUNT Send only COUNT pings. -s SIZE Send SIZE data bytes in packets (default=56). -I IPADDR Use IPADDR as source address. -q Quiet mode, only displays output at start and when finished. ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.14.98.22) ### 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 BusyBox v1.00 (2007.01.30-11:42+0000) multi-call binary Usage: ping [OPTION]... host Send ICMP ECHO_REQUEST packets to network hosts. Options: -c COUNT Send only COUNT pings. -s SIZE Send SIZE data bytes in packets (default=56). -I IPADDR Use IPADDR as source address. -q Quiet mode, only displays output at start and when finished. ###### ####### [3/8] Traceroute to the PoP (216.14.98.22) 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 216.14.98.22 (216.14.98.22), 30 hops max, 40 byte packets 1 002.96-113-64.ftth.swbr.surewest.net (64.113.96.2) 18.641 ms 17.726 ms 19.4 ms 2 172.21.1.49 (172.21.1.49) 19.891 ms 18.677 ms 19.689 ms 3 172.21.0.254 (172.21.0.254) 18.371 ms 18.465 ms 19.768 ms 4 ge-6-5.car1.Sacramento1.Level3.net (64.158.144.1) 19.624 ms 19.969 ms 19.51 ms 5 ae-11-11.car2.Sacramento1.Level3.net (4.69.132.150) 19.125 ms 20.716 ms 18.742 ms 6 ae-4-4.ebr1.SanJose1.Level3.net (4.69.132.158) 28.334 ms 23.209 ms 30.879 ms 7 ae-61-61.csw1.SanJose1.Level3.net (4.69.134.194) 29.811 ms 22.938 ms 31.963 ms 8 ae-62-62.ebr2.SanJose1.Level3.net (4.69.134.209) 22.229 ms 29.475 ms 35.547 ms 9 ae-3.ebr1.Denver1.Level3.net (4.69.132.58) 48.438 ms 50.049 ms 53.534 ms 10 ae-1-100.ebr2.Denver1.Level3.net (4.69.132.38) 62.058 ms 57.395 ms 53.738 ms 11 ae-3.ebr3.Chicago1.Level3.net (4.69.132.62) 70.205 ms 72.027 ms 71.458 ms 12 ae-68.ebr1.Chicago1.Level3.net (4.69.134.57) 79.801 ms ae-78.ebr2.Chicago1.Level3.net (4.69.134.61) 72.189 ms ae-68.ebr1.Chicago1.Level3.net (4.69.134.57) 76.403 ms 13 ae-23-56.car3.Chicago1.Level3.net (4.68.101.167) 71.278 ms ae-23-52.car3.Chicago1.Level3.net (4.68.101.39) 73.841 ms ae-13-51.car3.Chicago1.Level3.net (4.68.101.7) 73.846 ms 14 261.xe-0-3-0.cr2.ord1.us.scnet.net (4.71.100.26) 71.985 ms 72.606 ms 74.348 ms 15 v21.ar2.ord1.us.scnet.net (216.246.95.244) 74.993 ms v21.ar1.ord1.us.scnet.net (216.246.95.243) 70.281 ms 73.99 ms 16 sce.bg0.ord01.gw.stilenet.com (64.202.111.33) 73.262 ms sce.bg0-v4.ord01.gw.stilenet.com (64.202.111.37) 70.443 ms sce.bg0.ord01.gw.stilenet.com (64.202.111.33) 72.128 ms 17 sixxs.cx01.chi.bb.your.org (216.14.98.22) 74.526 ms 72.38 ms 72.754 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 PING ::1 (::1): 56 data bytes 64 bytes from ::1: icmp6_seq=0 ttl=64 time=0.8 ms 64 bytes from ::1: icmp6_seq=1 ttl=64 time=0.5 ms 64 bytes from ::1: icmp6_seq=2 ttl=64 time=0.4 ms --- ::1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.4/0.5/0.8 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4978:f:86::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:4978:f:86::2 (2001:4978:f:86::2): 56 data bytes 64 bytes from 2001:4978:f:86::2: icmp6_seq=0 ttl=64 time=0.6 ms 64 bytes from 2001:4978:f:86::2: icmp6_seq=1 ttl=64 time=0.4 ms 64 bytes from 2001:4978:f:86::2: icmp6_seq=2 ttl=64 time=0.5 ms --- 2001:4978:f:86::2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.4/0.5/0.6 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4978:f:86::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 PING 2001:4978:f:86::1 (2001:4978:f:86::1): 56 data bytes --- 2001:4978:f:86::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% 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. sh: traceroute6: not found ###### ###### [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 sh: traceroute6: not found ###### ###### 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. the aiccu version is the reccomended backport version as listed in the guide to installing on an openwrt based machine. the machine aiccu is running on is running openwrt white russian 0.9. my e-mail is aarcane@surewest.net uname -a Linux routerkrieg 2.4.30 #1 Sat Feb 3 13:16:08 CET 2007 mips unknown iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT ipv6 -- anywhere anywhere ACCEPT ipv6 -- anywhere anywhere DROP all -- anywhere anywhere state INVALID ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED DROP tcp -- anywhere anywhere tcp option=!2 flags:SYN/SYN input_rule all -- anywhere anywhere input_wan all -- anywhere anywhere LAN_ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere ACCEPT gre -- anywhere anywhere REJECT tcp -- anywhere anywhere reject-with tcp-reset REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain FORWARD (policy DROP) target prot opt source destination DROP all -- anywhere anywhere state INVALID TCPMSS tcp -- anywhere anywhere tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED forwarding_rule all -- anywhere anywhere forwarding_wan all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere Chain LAN_ACCEPT (1 references) target prot opt source destination RETURN all -- anywhere anywhere ACCEPT all -- anywhere anywhere Chain OUTPUT (policy DROP) target prot opt source destination DROP all -- anywhere anywhere state INVALID ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED output_rule all -- anywhere anywhere ACCEPT all -- anywhere anywhere REJECT tcp -- anywhere anywhere reject-with tcp-reset REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain forwarding_rule (1 references) target prot opt source destination Chain forwarding_wan (1 references) target prot opt source destination ACCEPT tcp -- anywhere web tcp dpt:80 ACCEPT tcp -- anywhere web tcp dpt:22 ACCEPT tcp -- anywhere mail tcp dpt:110 ACCEPT tcp -- anywhere oldbaz tcp dpts:9080:9089 ACCEPT udp -- anywhere ichigo udp dpt:5029 ACCEPT tcp -- anywhere ichigo tcp dpts:9090:9099 Chain input_rule (1 references) target prot opt source destination Chain input_wan (1 references) target prot opt source destination DROP tcp -- cided201.asia.info.net anywhere tcp dpt:22 Chain output_rule (1 references) target prot opt source destination root@routerkrieg:~# root@routerkrieg:~# ip -6 ro 2001:4978:f:86::/64 dev aiccu metric 256 mtu 1428 advmss 1368 2001:4978:12f::/64 dev br0 metric 1024 mtu 1500 advmss 1440 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 fe80::/64 dev br0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev vlan1 metric 256 mtu 1500 advmss 1440 fe80::/64 dev aiccu metric 256 mtu 1428 advmss 1368 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev vlan0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev br0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev aiccu metric 256 mtu 1428 advmss 1368 default via 2001:4978:f:86::1 dev aiccu metric 1024 mtu 1428 advmss 1368 root@routerkrieg:~# root@routerkrieg:~# ip route 69.62.232.0/25 dev vlan1 proto kernel scope link src 69.62.232.46 10.66.6.0/24 dev br0 proto kernel scope link src 10.66.6.97 default via 69.62.232.1 dev vlan1 root@routerkrieg:~# root@routerkrieg:~# ifconfig -a aiccu Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: fe80::4878:f:86:2/64 Scope:Link inet6 addr: 2001:4978:f:86::2/64 Scope:Global UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1428 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) br0 Link encap:Ethernet HWaddr 00:18:39:87:19:97 inet addr:10.66.6.97 Bcast:10.66.6.255 Mask:255.255.255.0 inet6 addr: fe80::218:39ff:fe87:1997/64 Scope:Link inet6 addr: 2001:4978:12f::1/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:342849 errors:0 dropped:0 overruns:0 frame:0 TX packets:366075 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:40837585 (38.9 MiB) TX bytes:201920434 (192.5 MiB) eth0 Link encap:Ethernet HWaddr 00:18:39:87:19:97 inet6 addr: fe80::218:39ff:fe87:1997/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:601644 errors:0 dropped:31 overruns:0 frame:0 TX packets:531612 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:231854401 (221.1 MiB) TX bytes:118709085 (113.2 MiB) Interrupt:4 eth1 Link encap:Ethernet HWaddr 00:18:39:87:19:99 inet6 addr: fe80::218:39ff:fe87:1999/64 Scope:Link UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:186872 errors:0 dropped:0 overruns:0 frame:607178 TX packets:264772 errors:124 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:21324188 (20.3 MiB) TX bytes:147733354 (140.8 MiB) Interrupt:2 Base address:0x5000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:7818 errors:0 dropped:0 overruns:0 frame:0 TX packets:7818 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:655958 (640.5 KiB) TX bytes:655958 (640.5 KiB) sit0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) vlan0 Link encap:Ethernet HWaddr 00:18:39:87:19:97 inet6 addr: fe80::218:39ff:fe87:1997/64 Scope:Link UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:194343 errors:0 dropped:0 overruns:0 frame:0 TX packets:237843 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:26880410 (25.6 MiB) TX bytes:69003747 (65.8 MiB) vlan1 Link encap:Ethernet HWaddr 00:18:39:87:19:98 inet addr:69.62.232.46 Bcast:69.62.232.127 Mask:255.255.255.128 inet6 addr: fe80::218:39ff:fe87:1998/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:407230 errors:0 dropped:0 overruns:0 frame:0 TX packets:293767 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:194141437 (185.1 MiB) TX bytes:47126428 (44.9 MiB) root@routerkrieg:~# eth0 is a physical connection to a switch which is segmented to vlan0 (lan) and vlan1(internet). tcpdump running on either vlan1 or eth0 shows that the UDP encapsulated packets are indeed being sent, but as stated previously, they do not reach their destination.