kaihendry
commented
12 years ago If a network ipv6 enabled, Webconverger should just be able to use it. I don't see the need of supporting tunnelling etc.
So at this point I just want to ensure the iptable/firewall rules are enabled for ipv6. IIRC we could be "inspired by" the ChromeOS project's rules.
I fail to locate any info regarding IPv6 support of Webconverger.
Could be good if this can be mentioned already at the startpage.
Things to verify when it comes to IPv6 support (among other things):
1) Using ip6tables to protect the Webconverger host (similar rules as with iptables (IPv4 edition)).
2) DHCP6 and RA support (so the Webconverger host can get an IPv6 address to use).
3) DNS6 support in the webbrowser (but only if IPv6 connectivity works).
4) Optimizations when using IPv6 (or for that matter when IPv6 is not being used) so IPv4 lookups wont get a slowdown (its not uncommon that dualstack environments will first try to lookup IPv6 and when failing they will use IPv4 - which will add 4 seconds or even more per click in the browser if you are unlucky).
A suggestion to above could be to have a boot string named ip-stack (or so) which can have following setups:
ip-stack=auto ip-stack=v4only ip-stack=v6only ip-stack=dualstack
along with:
v6=auto v6=static v6=DHCP6 v6=RA
5) A question is if various v4 to v6 tunneling protocols should be supported or not, such as Teredo etc.