21 January 2009
I’m interesting in running a test IPv6-only Australian OpenArena or ioquake3 (with Quake 3 data files) server as a showcase for the (relatively) new IPv6 support in the ioquake3 engine, and as a demonstration of a serious game being run over IPv6.
I imagine this being a single event — I cannot imagine that a continuously-run server will garner much traffic over the weeks, so a single weekend could be organised for people to connect up on.
I have 256K (32kB) of bandwidth available here, which can support up to 6 or so players. It’s connected via a tunnel broker from Sydney to Adelaide, so the minimum ping time will be 50ms — though ping times of 100ms would be more typical. For international players, it would be virtually unplayable, unfortunately.
If anyone else has spare server space with good IPv6 connectivity, perhaps they could offer to host a server instead.
With the current status quo of IPv6 connectivity, there’s no way anybody would get a good ping time. That’s not the point. The point is to connect over IPv6 — i.e. do something geeky cool.
So…any interest? Let me know in the comments if you’d be willing to have a frag.
Tagged: gaming, IPv6 | 9 Comments »
20 January 2009
I’ve just become an “IPv6 Sage” according to Hurricane Electric’s free IPv6 certification program.
The program is a series of tests that encourages you to learn about IPv6, and put your skills into practice by setting up tunnels, web servers, mail servers, and DNS configuration that is all IPv6-enabled.
Signing up is easy and free. Just register on the site, and you can begin right away through a series of automated tests. It begins easy, with setting up a tunnel, having your computer pinged, and gets progressively harder with tasks such as setting up an IPv6-enabled web server and mail server. When you have set up each task (e.g. web server), the certification website will connect to your server to verify that it’s all working, and award you the relevant level.
Doing the tests gives you loads of fun (if you are that way inclined), and I highly recommend it to anybody who is remotely interested in system or network administration.
Tagged: IPv6, networking | No Comments »
15 January 2009
If anybody is looking for the WineD3D code that Parallels modified to get Direct3D acceleration in Parallels Desktop, look no further. I have mirrored it here, which I am legally able to do, as it is licensed under the LGPL.
WineD3D-0.9.36-Parallels.zip, 796K.
MD5: cfb15b3a2c4cb851eeadad17d5d39010
Stefan Dösinger also mirrors it on his server, but he tells me it is hosted on a Pentium 120 that is not kept running all the time.
Tagged: coding, virtualisation, wine | 3 Comments »
11 January 2009
I would like to ask a quick favour of my loyal readership (insert cricket chirping sound effect here).
Whenever, I load this page in Firefox 3.0.4, which is a perfectly innocuous page on the OSx86 wiki, my X server crashes, just as if I hit Ctrl+Alt+Backspace.
I have an NVIDIA GeForce 7600GT, running on Linux 2.6.27-gentoo, with both the open source nv driver, as well as the proprietary driver version 177.82 (also occurs on 177.80).
Does it happen to anybody else? I strongly suspect a video driver bug, as it doesn’t occur on my Eee 901, which is GMA950–based.
Tagged: aargh, Linux, NVIDIA, xorg | 8 Comments »
9 January 2009
I’ve used 6to4 in the past, which impressed me because of the simplicity of its configuration. It uses the specially assigned anycast IP address 192.88.99.1 to magically find the nearest 6to4 router.
Well, most of the time (like when we were signed up with iiNet), if you do a traceroute to 192.88.99.1, you’ll find that the nearest 6to4 router is somewhere in Antarctica, or some lunar base on the Moon — and latency is terrible.
If you’re an Internode customer, you’ll know that they already provide IPv6 access to their customers, but the only documented way for non-Ethernet customers to get on IPv6 is via a Gateway6 tunnel broker that they provide, which is a bit painful to configure.
Well, just out of curiosity, I thought I’d do a traceroute 192.88.99.1, and lookie what I found:
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 1.026 ms 3.103 ms 3.774 ms
2 lns10.syd7.internode.on.net (150.101.197.27) 30.188 ms 34.723 ms 39.424 ms
3 vl114.cor2.syd7.internode.on.net (150.101.120.166) 44.651 ms 49.756 ms 54.390 ms
4 gi6-0-0-102.bdr1.syd7.internode.on.net (150.101.120.169) 82.688 ms 87.482 ms 92.403 ms
5 pos2-3.bdr1.adl6.internode.on.net (203.16.212.22) 98.641 ms 111.468 ms 111.975 ms
6 gi1-22.cor1.adl6.internode.on.net (150.101.225.94) 120.101 ms 50.369 ms 52.897 ms
7 fa0-0.sixtofour.adl6.internode.on.net (150.101.1.165) 53.626 ms * *
Looks like Internode provide their own 6to4 router, of which the ping time is around 50msec. Awesome!
Tagged: IPv6, networking | 6 Comments »
