Yeah! I’m finally connected to the IPv6 Internet via 6in4 tunnel.
christopher@nightshade:~$ ping ipv6.google.com -c 1 PING ipv6.google.com(sea15s02-in-x0e.1e100.net (2607:f8b0:400a:807::200e)) 56 data bytes 64 bytes from sea15s02-in-x0e.1e100.net (2607:f8b0:400a:807::200e): icmp_seq=1 ttl=57 time=59.4 ms --- ipv6.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 59.426/59.426/59.426/0.000 ms
Earlier I tried to do this via 6to4, a different IPv6 transition method, but failed. While trying to diagnose the problem, I kept running into Web information indicating that 6to4 is deprecated and unreliable, so I gave up on it.
So I went with what seems to be the common route of using 6in4 protocol along with a tunnel provided by tunnelbroker.net (he.net). It is a free service, though you are required to provide your email address and other real personal information. Also, you must have a public IPv4 address for your tunnel endpoint. After signing up, you get a configuration page like so:
(My configuration is of no use to you, as you do not have my public IPv4 address.)
In your libreCMC gateway router, you must switch the protocol of the WAN6 interface to 6in4. Then copy over the configuration items into the interface settings:
Your IPv6 capable desktops on the network will automatically get new IP addresses:
christopher@nightshade:~$ ip addr 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 inet6 2001:470:b:449:c49f:c37b:638c:b6fd/64 scope global temporary dynamic valid_lft 602629sec preferred_lft 83855sec inet6 2001:470:b:449:1e6f:65ff:feac:7d41/64 scope global mngtmpaddr noprefixroute valid_lft forever preferred_lft forever
And you will be able to communicate to IPv6 capable sites.
LibreCMC will need the 6in4 package installed. I’m planning to include this in my future builds.