Testing IPv6 on AusGamers
As of today we are rolling out IPv6 across Mammoth VPS and part of our testing includes making AusGamers IPv6 compatible!
I am a bit of an IPv6 noob so I'm hoping some of you network gurus who know what you're doing and are on IPv6 networks might be able to try loading the site. Currently the main stuff should all work via IPv6 - the website (www.ausgamers.com). Our video server and primary file server are also both configured for IPv6, so you should be able to download and stream as normal - if you could test these as well that would be great. Any feedback would be appreciated! |
04:39pm 06/06/12 Permalink
Seems you're also noob at linking url in a forum you created! |
04:43pm 06/06/12 Permalink
I'm hoping some of you network gurus who know what you're doing and are on IPv6 networks might be able to try loading the site. Would there be an achievement in it for us? ;D |
04:53pm 06/06/12 Permalink
the "I'm not busy enough at work, so I'll do trog's beta testing for him" achievement.... ;)
|
05:10pm 06/06/12 Permalink
trololololololol haw haw haw haw hawwww... ;)
|
05:12pm 06/06/12 Permalink
403 Forbidden on the last two.yeh I took them out cuz I just realised they were probably confusing. The intent wasn't that people click on them; it was mostly for people who wanted to check that they were using IPv6 when streaming video/downloading files by giving them the hostnames that we use for those things. |
05:54pm 06/06/12 Permalink
Good work Trog for the ipv6 day!
PING6(56=40+8+8 bytes) 2001:67c:2e8:13:b578:feb0:7c2a:1264 --> 2404:9400:0:1::1 16 bytes from 2404:9400:0:1::1, icmp_seq=0 hlim=53 time=310.205 ms 16 bytes from 2404:9400:0:1::1, icmp_seq=1 hlim=53 time=396.534 ms 16 bytes from 2404:9400:0:1::1, icmp_seq=2 hlim=53 time=311.722 ms 16 bytes from 2404:9400:0:1::1, icmp_seq=3 hlim=53 time=311.624 ms We peer at AMS-IX and then it goes through Hurricane Electric to your servers. |
09:53pm 06/06/12 Permalink
works fine y0 |
01:17am 07/06/12 Permalink
sweet as. We've had someone tell us routing is a bit weird from Brisbane so just waiting on some more traceroutes - looks like you're seeing the same thing teq - can you do an IPv4 traceroute to see what the difference is?
|
10:32am 07/06/12 Permalink
traceroute to www.ausgamers.com (110.232.115.10), 64 hops max, 52 byte packets
1 gw.nikrtr.guestnet.ripe.net (193.0.10.2) 1.611 ms 3.649 ms 1.378 ms 2 gigabitethernet6-17.car2.ams1.level3.net (195.69.144.110) 3.932 ms 1.934 ms 1.828 ms 3 ae-31-90.car1.sanjose2.level3.net (4.69.152.203) 147.270 ms ae-21-60.car1.sanjose2.level3.net (4.69.152.11) 147.272 ms 146.903 ms 4 time-warner.car1.sanjose2.level3.net (4.59.0.230) 147.315 ms 147.079 ms 146.994 ms 5 pdx1-ar4-xe-5-0-0-0.us.twtelecom.net (66.192.254.86) 161.527 ms pdx1-ar4-xe-0-1-0-0.us.twtelecom.net (66.192.244.74) 161.637 ms pdx1-ar4-xe-5-0-0-0.us.twtelecom.net (66.192.254.86) 161.683 ms 6 syd-sot-ken-crt1-ge-3-1-0.tpgi.com.au (203.29.135.33) 301.930 ms 302.138 ms 302.091 ms 7 202-7-162-246.tpgi.com.au (202.7.162.246) 301.467 ms 301.256 ms 301.329 ms 8 29.112.220.203.unassigned.comindico.com.au (203.220.112.29) 301.344 ms 301.294 ms 301.806 ms 9 29.112.220.203.unassigned.comindico.com.au (203.220.112.29) 301.355 ms 301.074 ms 300.709 ms 10 ns4.mammothvps.com.au (110.232.115.10) 301.900 ms !Z 302.020 ms !Z 301.971 ms !Z traceroute6 to www.ausgamers.com (2404:9400:0:1::1) from 2001:67c:2e8:13:ad7c:f8fd:ca7e:3085, 64 hops max, 12 byte packets 1 gw.ipv6.nikrtr.guestnet.ripe.net 946.731 ms 1.735 ms 1.919 ms 2 20gigabitethernet1-3.core1.ams1.ipv6.he.net 3.156 ms 3.247 ms 3.134 ms 3 10gigabitethernet1-4.core1.lon1.he.net 21.375 ms 13.464 ms 10.063 ms 4 10gigabitethernet7-4.core1.nyc4.he.net 86.606 ms 78.413 ms 85.015 ms 5 10gigabitethernet5-3.core1.lax1.he.net 139.874 ms 148.561 ms 145.198 ms 6 10gigabitethernet4-2.core3.fmt2.he.net 147.559 ms 147.750 ms 148.226 ms 7 10gigabitethernet8-4.core1.pao1.he.net 147.173 ms 147.399 ms 147.675 ms 8 10gigabitethernet3-4.core1.sjc1.he.net 152.667 ms 157.223 ms 147.015 ms 9 tpg-internet-pty-ltd.10gigabitethernet3-1.core1.sjc1.he.net 294.011 ms 295.023 ms 293.630 ms 10 2407:8800:a000:2000::1c5 332.890 ms 332.853 ms 333.198 ms 11 2407:8800:a000:2000::1c9 308.109 ms 308.923 ms 307.460 ms 12 2407:8800:a000:2000::1a 307.921 ms 308.154 ms 307.743 ms 13 * * * 14 2404:2800:1ff0:2000:3::1 428.021 ms 309.152 ms 308.582 ms 15 * * * 16 * * * 17 *^C |
07:55pm 07/06/12 Permalink
08:03pm 07/06/12 Permalink
I see you guys via your pipe peering, if I force the route via Vocus it just ends up back on pipe
|
08:40pm 07/06/12 Permalink
