I have created a survey, it can be found here - Alleg IPv6 Survey. There are detailed instructions inside on how to check your ipv6 connectivity and choose your best ipv6 broker.
The more people participate, the better we'll be able to gauge the need for ipv6 alleg servers.
The method is very simple, we make servers and pilots connected to ipv6.
Does it involve code change - Hell NO !
Does it involve a little command line typing - YES
Does it cost any money - NO
The gist of it is as follows... there's a very nice and sweet ipv6 tunnel broker, it's called www.tunnelbroker.net, it belongs to Hurricane Electric and they have their own intercontinental high speed fiber, with endpoints in every geolocation worldwide:
Hong Kong, HK [ 216.218.221.6 ]
Paris, FR [ 216.66.84.42 ]
London, UK [ 216.66.80.26 ]
Frankfurt, DE [ 216.66.80.30 ]
Amsterdam, NL [ 216.66.84.46 ]
Chicago, IL, US [ 209.51.181.2 ]
Dallas, TX, US [ 216.218.224.42 ]
Toronto, ON, CA [ 216.66.38.58 ]
Los Angeles, CA, US [ 66.220.18.42 ]
New York, NY, US [ 209.51.161.14 ]
Seattle, WA, US [ 216.218.226.238 ]
Fremont, CA, US [ 72.52.104.74 ]
Ashburn, VA, US [ 216.66.22.2 ]
Miami, FL, US [ 209.51.161.58 ]
Aside from HE, people can try out their ipv4 connections to
http://www.sixxs.net and http://www.go6.net/ for Canada/US.
For our AU users, there's
http://broker.aarnet.net.au/ - 202.158.196.131
http://ipv6.internode.on.net/ - 150.101.0.201
For our thai pilots:
http://tb.ipv6.nectec.or.th/ - 203.185.129.133
Norway pilots could use:
http://www.ipv6tunnel.ssc.net/ - 213.179.32.14
French pilots:
http://tunnel-broker.renater.fr - (i don't speak french, so i couldn't lookup ipv4 POP)
What i propose is for server admins (ie GPZ, Planet) to connect to their closest ipv6 POP, via best available ipv6 tunnel broker and for users to connect to their own respective closest ipv6 POPs. The user's ISP would only be used in so far as to travel to the nearest ipv6 gateway, then the packets would traverse via ipv6 directly to servers.
here's an example of how easy it is to do it with winXP from command line:
ipv6 install
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.178.100 216.66.80.30
netsh interface ipv6 add address IP6Tunnel 2001:470
1552::2netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470
1552::1Same for servers and users, just copy paste from ipv6 broker web page.
The only drawback is that pilots would have to have an account on tunnelbroker.net (or other ipv6 broker) and would have to either install automatic script (some brokers have it for download, so modifying it a bit to be generic shouldn't be a problem) that updates their ipv4 address for the broker or do it by hand everytime they wish to play alleg. Other then that, it's really straight forward and simple.
The benefits really outweigh anything:
1. NO MORE LAG ISSUES.
2. Servers can still have ipv4 and those who like to can connect to them as usual. (It means both ipv4 and ipv6 pilots would be able to fly together seamlessly)
3. People from US would have a max of 70ms ping times to GPZ and people from EU would have a same ping to Planet. (Actually latencies would vary, but generally everybody would be able to find a closer ipv6 POP, that will improve their lag and those who don't need any improvement, can continue to use ipv4 and never bother with ipv6 tunnels)
Anyways,
I'd be happy to help out, so let me know what i can do.
/edit0:
In my haste, i forgot that DNS issues are easily solved by just adding AAAA records.... those are ipv6 A records...
/edit1:
I decided to include more tunnel broker IPs.
/edit2:
xp sp3 seems to have vista style ipv6 connectivity commands, updated the example accordingly.
/edit3:
A survey form created and added to the top of the post
Thnks
