I can access IPv6 sites on the router but my clients cant even ping external IPv6 sites. Heres the output of my radvd.conf interface eth0 { AdvSendAdvert on; prefix 2a01:348:6:10e::2 /64 { AdvAutonomous on; AdvOnLink on; AdvRouterAddr on; }; }; Heres the output for aiccu test Tunnel Information for T16204: POP Id : gblon02 IPv6 Local : 2a01:348:6:10e::2/64 IPv6 Remote : 2a01:348:6:10e::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (90.212.252.27) ### 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 90.212.252.27 (90.212.252.27) 56(84) bytes of data. 64 bytes from 90.212.252.27: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 90.212.252.27: icmp_seq=2 ttl=64 time=0.061 ms 64 bytes from 90.212.252.27: icmp_seq=3 ttl=64 time=0.063 ms --- 90.212.252.27 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 0.061/0.062/0.063/0.006 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (77.75.104.126) ### 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 77.75.104.126 (77.75.104.126) 56(84) bytes of data. 64 bytes from 77.75.104.126: icmp_seq=1 ttl=60 time=381 ms 64 bytes from 77.75.104.126: icmp_seq=2 ttl=60 time=356 ms 64 bytes from 77.75.104.126: icmp_seq=3 ttl=60 time=123 ms --- 77.75.104.126 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 123.553/287.054/381.566/116.081 ms ###### ####### [3/8] Traceroute to the PoP (77.75.104.126) 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 sh: traceroute: command not found ###### ###### [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: icmp_seq=1 ttl=64 time=0.053 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.056 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.057 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.053/0.055/0.057/0.006 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:348:6:10e::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2a01:348:6:10e::2(2a01:348:6:10e::2) 56 data bytes 64 bytes from 2a01:348:6:10e::2: icmp_seq=1 ttl=64 time=0.049 ms 64 bytes from 2a01:348:6:10e::2: icmp_seq=2 ttl=64 time=0.063 ms 64 bytes from 2a01:348:6:10e::2: icmp_seq=3 ttl=64 time=0.062 ms --- 2a01:348:6:10e::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.049/0.058/0.063/0.006 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:348:6:10e::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 2a01:348:6:10e::1(2a01:348:6:10e::1) 56 data bytes From 2a01:348:6:10e:219:dbff:fec7:e0f8 icmp_seq=1 Destination unreachable: Address unreachable From 2a01:348:6:10e:219:dbff:fec7:e0f8 icmp_seq=2 Destination unreachable: Address unreachable From 2a01:348:6:10e:219:dbff:fec7:e0f8 icmp_seq=3 Destination unreachable: Address unreachable --- 2a01:348:6:10e::1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2010ms ###### ###### [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. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2a01:348:6:10e::2, 30 hops max, 16 byte packets 1 gw-271.lon-02.gb.sixxs.net (2a01:348:6:10e::1) 32.345 ms 111.706 ms 52.172 ms 2 ae0-1235.rt2.the.uk.goscomb.net (2a01:348:0:4:0:3:0:1) 54.324 ms 26.977 ms 28.045 ms 3 ge-0-0-0-1368.rt1.nik.nl.goscomb.net (2a01:348::10:1:1) 59.359 ms 52.899 ms 60.085 ms 4 ams-ix2.ipv6.concepts.nl (2001:7f8:1::a501:2871:2) 109.114 ms 84.429 ms 62.024 ms 5 2001:838:0:13::1 (2001:838:0:13::1) 59.67 ms 44.724 ms 99.253 ms 6 2001:838:0:12::2 (2001:838:0:12::2) 49.054 ms 72.351 ms 101.233 ms 7 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 64.271 ms 57.827 ms 97.797 ms ###### ###### [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 traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2a01:348:6:10e::2, 30 hops max, 16 byte packets 1 gw-271.lon-02.gb.sixxs.net (2a01:348:6:10e::1) 183.64 ms 379.442 ms 302.163 ms 2 ae0-1235.rt2.the.uk.goscomb.net (2a01:348:0:4:0:3:0:1) 268.489 ms 190.664 ms 104.139 ms 3 po-1-806.r01.londen03.uk.bb.gin.ntt.net (2001:728:1c00:5000::25) 60.601 ms 51.802 ms 122.417 ms 4 xe-2-3-0.r22.londen03.uk.bb.gin.ntt.net (2001:728:0:2000::119) 52.199 ms 77.69 ms 28.094 ms 5 as-0.r20.nycmny01.us.bb.gin.ntt.net (2001:418:0:2000::1a9) 134.981 ms 138.848 ms 130.533 ms 6 as-2.r21.sttlwa01.us.bb.gin.ntt.net (2001:418:0:2000::5) 222.689 ms 211.759 ms 236.763 ms 7 as-2.r21.osakjp01.jp.bb.gin.ntt.net (2001:218:0:2000::75) 278.819 ms 335.91 ms 297.572 ms 8 ae-4.r21.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::dd) 291.148 ms 287.636 ms 285.747 ms 9 xe-4-1.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::116) 309.178 ms 445.571 ms 431.626 ms 10 ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:5000::82) 272.409 ms 317.973 ms 295.113 ms 11 ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 324.168 ms 259.073 ms 298.275 ms 12 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 257.146 ms 280.556 ms 253.707 ms 13 ve45.nec2.yagami.wide.ad.jp (2001:200:0:12::74) 272.794 ms 284.999 ms 257.391 ms 14 lo0.alaxala1.k2.wide.ad.jp (2001:200:0:4800::7800:1) 267.259 ms 278.219 ms 258.912 ms 15 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 262.693 ms 257.52 ms 270.243 ms output of ifconfig sixxs sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2a01:348:6:10e::2/64 Scope:Global inet6 addr: fe80::c0a8:fd01/64 Scope:Link inet6 addr: fe80::c0a8:fd02/64 Scope:Link inet6 addr: fe80::5ad4:fc1b/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:293 (293.0 b) TX bytes:736 (736.0 b) and finaly out put of ping6 sixxs.net from client Pinging 2a01:348:6:10e::1 from 2a01:348:6:10e:e5dc:5bdc:9d5c:d560 with 32 bytes of data: Reply from 2a01:348:6:10e:e5dc:5bdc:9d5c:d560: Destination address unreachable. I have tested with no IPv6 firewall rules and net.ipv6.conf.all.forwarding = 1 any help will be much apreciated.