Hi all, I apologize opening a new thread in spite of that the problem has been discussed in the forum several times over and over. Just didn't find an adequate response... In my home network I have a server (an old laptop) running Debian 6.0.10 (kernel 2.6.32-5-686) and among others aiccu installed. The tunnel seems to work just fine and I can reach other ipv6 hosts in the internet from this server. I also have radvd installed and it seems to advertise as configured and my clients get there ipv6 addresses. But for some reason the connections from the clients to the internet do not work. I'm probably missing some really simple error in config, but anyway I'm stuck. Any hints what to do and change are appreciated! Settings on he server: * aiccu/sixxs: Tunnel T119958 - endpoint 2001:14b8:100:345::2 - enabled Subnet R217502 - prefix 2001:14b8:100:8345::/64 - enabled * ifconfig eth0 Link encap:Ethernet HWaddr 00:e0:00:5a:04:36 inet addr:192.168.144.112 Bcast:192.168.144.255 Mask:255.255.255.0 inet6 addr: 2001:14b8:100:8345:2e0:ff:fe5a:436/64 Scope:Global inet6 addr: fe80::2e0:ff:fe5a:436/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 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 sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: 2001:14b8:100:345::2/64 Scope:Global inet6 addr: fe80::14b8:100:345:2/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1 tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.144.112.1 P-t-P:10.144.112.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 (I've omitted the RX/TX lines from the output; the tun0 device is for openvpn, currently not working as my ISP is not giving any public ipv4 address anymore, neither ipv6) * route ipv4: 10.144.112.2 dev tun0 proto kernel scope link src 10.144.112.1 10.144.112.0/24 via 10.144.112.2 dev tun0 192.168.144.0/24 dev eth0 proto kernel scope link src 192.168.144.112 default via 192.168.144.1 dev eth0 * route ipv6: 2001:14b8:100:345::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 2001:14b8:100:8345::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 default via 2001:14b8:100:345::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0 * forwarding /proc/sys/net/ipv6/conf/eth0/forwarding : 1 * pinging: PING ipv6.google.com(arn09s05-in-x0e.1e100.net) 56 data bytes 64 bytes from arn09s05-in-x0e.1e100.net: icmp_seq=1 ttl=54 time=37.5 ms --- ipv6.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms * /etc/radvd.conf: interface eth0 { AdvSendAdvert on ; # Advertise at least every 30 seconds MaxRtrAdvInterval 30; # in order to force non RFC 6106 compliant clients to get a dns address AdvOtherConfigFlag on ; prefix 2001:14b8:100:8345::/64 { AdvOnLink on;# RDNSS 2001:14b8:100:345::1 2001:14b8:100:345::2 { # }; AdvAutonomous on; AdvRouterAddr on; }; }; Settings on the client #1: * Xubuntu 14.04 with kernel 3.13.0-107-generic * no manual configuration done for ipv6 * ifconfig (fresh after recent reboot) eth0 Link encap:Ethernet HWaddr 48:5b:39:c6:42:1b inet addr:192.168.144.77 Bcast:192.168.144.255 Mask:255.255.255.0 inet6 addr: 2001:14b8:100:8345:4a5b:39ff:fec6:421b/64 Scope:Global inet6 addr: fe80::4a5b:39ff:fec6:421b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 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:65536 Metric:1 * route ipv4: default via 192.168.144.1 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.144.0/24 dev eth0 proto kernel scope link src 192.168.144.77 * route ipv6: 2001:14b8:100:8345::/64 dev eth0 proto kernel metric 256 expires 86386sec fe80::/64 dev eth0 proto kernel metric 256 default via fe80::8eeb:c6ff:fec7:eb0c dev eth0 proto ra metric 1024 expires 1508sec hoplimit 64 default via fe80::2e0:ff:fe5a:436 dev eth0 proto ra metric 1024 expires 76sec hoplimit 64 * forwarding: /proc/sys/net/ipv6/conf/eth0/forwarding: 0 * neighbours fe80::8eeb:c6ff:fec7:eb0c dev eth0 lladdr 8c:eb:c6:c7:eb:0c router DELAY fe80::2e0:ff:fe5a:436 dev eth0 lladdr 00:e0:00:5a:04:36 router STALE * pinging the server: PING 2001:14b8:100:8345:2e0:ff:fe5a:436(2001:14b8:100:8345:2e0:ff:fe5a:436) 56 data bytes 64 bytes from 2001:14b8:100:8345:2e0:ff:fe5a:436: icmp_seq=1 ttl=64 time=0.388 ms --- 2001:14b8:100:8345:2e0:ff:fe5a:436 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms * pinging ipv6.google.com: PING ipv6.google.com(arn06s07-in-x0e.1e100.net) 56 data bytes --- ipv6.google.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms * traceroute6 ipv6.google.com: traceroute to ipv6.l.google.com (2a00:1450:400f:805::200e) from 2001:14b8:100:8345:4a5b:39ff:fec6:421b, 30 hops max, 24 byte packets 1 * * * Similar results with another client running Debian Jessie. Most of the problems discussed in the forum seemed to be related to missing ipv6 address on the server interface from the sixxs offered subnet, but that is not the problem here. The server eth0 interface has address 2001:14b8:100:8345:2e0:ff:fe5a:436 that belongs to the subnet given, although not being the recommended 2001:14b8:100:8345::1 or 2, so this time the problem must elsewhere. But where? //rkv Risto Virtanen