So just in a surprised moment of serendipity, my _non-IT_ boyfriend has beaten me to IPv6 connectivity and he didn't even know it. I'm a little jealous as this has been on my two do list for over half a year. Back-story, early in 2015 I upgraded his home from early linksys WRT54G (linksys firmware), to a D-Link DIR-825 (rev. B1), with OpenWRT 14.07. Roughly a month ago OpenWRT 15 was release, so I logged into gather info for doing the firmware upgrade and see this. http://revident.net/images/OpenWRT-network-info-with-IPv6.png I've known Teksavvy, his provider, has had a beta program for IPv6 for DSL customers. I signed up, I have an allocation, but I've not used it yet. At some point, Teksavvy turned it live, and the OpenWRT router I set-up for my BF just picked it up and ran with it. It works! His connection gets a full 20/20 score from http://ipv6-test.com/ Out of box, no intervention. My boyfriend, and the two other room-mates have been using IPv6, for some unknown period (maybe months), with no observable difference. Just Wow! Had to share. ===== Just some info form my laptop. ======== [scott@arcticnoise fonts]$ ifconfig [...snip...] wlp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.4.230 netmask 255.255.255.0 broadcast 192.168.4.255 inet6 fd1c:3456:4edf::1ef prefixlen 128 scopeid 0x0<global> inet6 2607:f2c0:9281:1900::1ef prefixlen 128 scopeid 0x0<global> inet6 2607:f2c0:9281:1900:3210:b3ff:fe9b:457c prefixlen 64 scopeid 0x0<global> inet6 fd1c:3456:4edf:0:3210:b3ff:fe9b:457c prefixlen 64 scopeid 0x0<global> inet6 fe80::3210:b3ff:fe9b:457c prefixlen 64 scopeid 0x20<link> ether 30:10:b3:9b:45:7c txqueuelen 1000 (Ethernet) RX packets 1828026 bytes 2043219415 (1.9 GiB) RX errors 0 dropped 0 overruns 0 frame 2457050 TX packets 1108781 bytes 250361333 (238.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 [scott@arcticnoise fonts]$ ping6 google.com PING google.com(yyz08s14-in-x05.1e100.net) 56 data bytes 64 bytes from yyz08s14-in-x05.1e100.net: icmp_seq=1 ttl=58 time=143 ms 64 bytes from yyz08s14-in-x05.1e100.net: icmp_seq=2 ttl=58 time=156 ms 64 bytes from yyz08s14-in-x05.1e100.net: icmp_seq=3 ttl=58 time=158 ms 64 bytes from yyz08s14-in-x05.1e100.net: icmp_seq=4 ttl=58 time=190 ms 64 bytes from yyz08s14-in-x05.1e100.net: icmp_seq=5 ttl=58 time=288 ms 64 bytes from yyz08s14-in-x05.1e100.net: icmp_seq=6 ttl=58 time=403 ms ^C --- google.com ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5005ms rtt min/avg/max/mdev = 143.201/223.390/403.423/93.816 ms [scott@arcticnoise fonts]$ ping6 -n google.com PING google.com(2607:f8b0:400b:80b::1005) 56 data bytes 64 bytes from 2607:f8b0:400b:80b::1005: icmp_seq=1 ttl=58 time=106 ms 64 bytes from 2607:f8b0:400b:80b::1005: icmp_seq=2 ttl=58 time=133 ms 64 bytes from 2607:f8b0:400b:80b::1005: icmp_seq=3 ttl=58 time=142 ms ^C --- google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 106.601/127.501/142.416/15.227 ms -- Scott Sullivan