Baselayout network scripts should include support for connecting to IPv6 network over IPv4. This should include at least following methods: 1) Static IPv6 over IPv4 tunnels from one point to another - Manually specified tunnel remote address. The oldest method. 2) 6to4 - Standard method for connecting to IPv6 network and acquiring a ::/48 prefix for yourself (basically 2002:<youripv4addr>::). Easy to set up - http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/configuring-ipv6to4-tunnels.html. Remote IPv4 address is always 192.88.99.1 - an IPv4 anycast address which connects to your nearest 6to4 gateway regardless where you are. Very automatic, basically the user should only need to specify on/off toggle. Script needs to take your IPv4 address and use it to set up a tunnel. Also needs to take down tunnel if cable is disconnected or wireless LAN connection is broken (perhaps with help of ifplugd). 3) ISATAP - Standard method for connecting to IPv6 network and acquiring a ::/64 prefix. Relatively easy to set up, http://www.litech.org/isatap/. Instead of a standard IPv4 address, such as 192.88.99.1 the 6to4 uses, the "standard" method for autodiscovering ISATAP gateway seems to be querying for DNS name ISATAP.<domain>. User needs an option to specify remote address manually. 4) Teredo: Microsoft's method for connecting to IPv6 over IPv4+UDP. Linux implementation at http://www.simphalempin.com/dev/miredo/. Needs the client software - no automatic server discovery, altough Windows XP SP2 uses teredo.ipv6.microsoft.com by default. The Linux implementation is called Miredo, an can be found at http://www.simphalempin.com/dev/miredo/. Are any of these already in baselayout 1.12.0? At least 6to4 should be simple to implement. It also works both with iproute and ifconfig tools. ISATAP may require iproute, Teredo needs Miredo to be installed. Any interest in including these functionalities to Gentoo?
Apparently someone has already made something up for 6to4 in Gentoo-wiki: http://gentoo-wiki.com/HOWTO_IPv6#IPv6_tunneling_with_6to4 Maybe this can be used as a basis at least for the 6to4 portion. Anyway, it seems that ISATAP has recently run into patent encumberance problems and is no longer supported by USAGI project (removed somewhere around kernel 2.6.8). So I guess that can be dropped for now. Miredo/Teredo support is needed, because 6to4 does not work over NATs and Firewalls (6to4 is basically Ip over Ip (protocol 41), Teredo is just standard UDP traffic from FW's point of view). 6to4 support should probably be in baselayout, because the tunnels can be established without any external tools. Teredo support should probably be provided by Miredo ebuild.
Static IPV6 tunnel config_eth0=( "192.168.0.2/24" "2001:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:feb/64" ) routes_eth0=( "default via 192.168.0.1" ) iptunnel_sit1="mode sit remote xxx.xxx.xxx.xxx ttl 64" config_sit1=( "2001:xxxx:xxxx::xxxx:xxxx/128" ) routes_sit1=( "2000::/3" ) That should work in baselayout-1.11, but definitely works on my server on baselayout-1.12 The benefit of this approach is that you can setup a radvd server to autoconfigure your clients for ipv6 addresses and routing - works like a charm :) Personally, I don't like your option 2 as that requires extra config on all clients. So someone else (maybe you?) can write a module for that. ISATAP looks nice, but only supports linux 2.4 kernels by the looks of it so that's a no. Teredo will not be supported by baselayout - instead the Teredo Gentoo maintainer (if there is/will ever be) one should write a net module or init script for integration. If you disagree with any of the above then please open a new bug addressing each point seperately.
> Personally, I don't like your option 2 as that requires extra config on all > clients. So someone else (maybe you?) can write a module for that. Umm, the point of 6to4 is to get RID of all that extra config on all the clients. Anyway, opening a new bug for 6to4.
