World IPv6 Day

Technical Support
Prev 1 3 4 5 6 Next
So, I decided to take part in world IPv6 day. At the moment, I am using a tunnel broker (HE.net) to get IPv6, but it's tunneled on my router, so my desktop has no clue it's not a native IPv6 connection. I've found my config.wtf file in the wow installation/wtf folder and added the SET unlockIPv6 "1" line to the bottom of it. Starting wow up still has a greyed out IPv6 checkbox. I double-checked the list and Winterhoof is on the list, so I should be able to test out IPv6 connectivity.

I have both a static IPv4 address, and a static IPv6 address (2001:470...), as well as DNS that works with IPv6. Running Windows 7 Enterprise (x64). The http://test-ipv6.com/ test site gives me 10/10 for both IPv4 and IPv6, yet WoW still can't sem to find a valid IPv6 address.

Any thoughts on how to make this work? I'd like to do my part and chip in to test, but it's difficult to do when the software won't let me.

More details (specific addresses/configs) can be furnished upon request.


I have an Airport Exteme and Cox, who uses Teredo. Under the IPv6 Friewall section, I had to check the box for "Allow Teredo Tunnels".

You might check for something similar in your Router.
Quirk,

We're interested in seeing a trace route to the IPv6 servers if you could provide one. From a command or terminal window use the command provided below:

1. MS : tracert -6 ipv6.blizzard.com or tracert -6 2001:1890:e000:c01:dad3:85ff:fed9:ce24
2. Mac OS : traceroute6 ipv6.blizzard.com or traceroute6 2001:1890:e000:c01:dad3:85ff:fed9:ce24
3. Linux : traceroute6 ipv6.blizzard.com or traceroute6 2001:1890:e000:c01:dad3:85ff:fed9:ce24

I've included the command for other OSs if others would like to provide the information as well.
________________________________________________
Technical Support
Want to speak with someone directly? http://us.blizzard.com/en-us/company/about/contact.html
How's my driving? https://www.surveymk.com/s/R5D3LCF

Check your G-diffuser system!
06/08/2011 12:33 PMPosted by JonD
I've included the command for other OSs if others would like to provide the information as well.


Here's my traceroute

Tracing route to ipv6.blizzard.com [2001:1890:e000:c01:dad3:85ff:fed9:ce24] over a maximum of 30 hops

1 32 ms 31 ms 33 ms 2002:c058:6301::1
2 34 ms 32 ms 33 ms gige-g2-10.core1.chi1.he.net [2001:470:0:14d::1]
3 37 ms 43 ms 39 ms 10gigabitethernet7-2.core1.nyc4.he.net [2001:470:0:1c6::1]
4 46 ms 136 ms 93 ms as7018-att.10gigabitethernet2-3.core1.nyc4.he.net [2001:470:0:1dd::2]
5 * 103 ms 183 ms cr2.n54ny.ip.att.net [::ffff:12.122.81.110]
6 179 ms 103 ms 101 ms cr2.wswdc.ip.att.net [::ffff:12.122.3.38]
7 102 ms 103 ms 171 ms cr1.attga.ip.att.net [::ffff:12.122.1.173]
8 180 ms 120 ms 103 ms cr2.dlstx.ip.att.net [::ffff:12.122.28.174]
9 103 ms 103 ms * cr1.dlstx.ip.att.net [::ffff:12.122.1.209]
10 103 ms * 102 ms cr1.phmaz.ip.att.net [::ffff:12.122.28.182]
11 * * * Request timed out.
12 104 ms * 102 ms 2001:506:2001:601::1111:f99a
13 102 ms 172 ms 103 ms 2001:1890:e000:80a::1005:d002
14 * * * Request timed out.
Here's mine:
Tracing route to ipv6.blizzard.com [2001:1890:e000:c01:dad3:85ff:fed9:ce24]
over a maximum of 30 hops:

1 <1 ms * <1 ms 2001:44b8:7916:eef0:204:edff:feb3:d5e5
2 37 ms 36 ms 37 ms loop0.lns6.syd7.internode.on.net [2001:44b8:b070::4]
3 36 ms 37 ms 36 ms te3-1-52.cor2.syd6.internode.on.net [2001:44b8:b070:9::2]
4 36 ms * 36 ms gi6-0-0-133.bdr1.syd6.internode.on.net [2001:44b8:b060:135::1]
5 185 ms 185 ms 185 ms pos6-0.bdr1.lax1.internode.on.net [2001:44b8:b060:7::2]
6 185 ms 196 ms 185 ms 2001:504:13::1a
7 185 ms 185 ms 185 ms 2001:470:0:1e6::2
8 198 ms 196 ms 197 ms cr1.la2ca.ip.att.net [::ffff:12.123.30.18]
9 197 ms 196 ms 196 ms cr2.phmaz.ip.att.net [::ffff:12.122.31.190]
10 197 ms 197 ms 197 ms 2001:1890:e000:809::1005:d001
11 196 ms 196 ms 196 ms 2001:506:2001:601::1111:f99a
12 197 ms 197 ms 196 ms 2001:1890:e000:809::1005:d001
13 * * * Request timed out.
14 * * * Request timed out.

Just an aside Blizzard, blocking certain ICMP6 messages breaks IPv6 features such as PMTUD which could break things for certain network stacks.
This may be a weird case, but I can't get tracert to pick up anything over my IPv6 connection.
However, forcing IPv6 in the config file does work, and I am able to log into the game using it.
Some information for the Mac checkbox can't be modified thing.

In this household we've had IPv6 connectivity through a sixxs.net tunnel for the last couple of years. We have WoW running on Windows 7, Mac OS X and Ubuntu 11.04 with Wine. Each machine has a public IPv6 address and scores 10/10 on the tests. The prefix is [EDITED]

WoW over IPv6 worked first time on both the Linux and Windows boxes. The Mac is a different story.

Essentially if I have only one network interface configured (the wired or wireless, it doesn't matter which), then the Mac refuses to allow modification of the "enable IPv6 when available" checkbox.

If I manually set the useIPv6 property to "1" (as well as the previously set unlockIPv6 property), then I do get an IPv6 connection to a supported server. Verified in game and via tcpdump.

If I enable /both/ the wired and wireless interfaces (en0 and en1) and allow both interfaces to get a global IPv6 address, then the "enable IPv6" checkbox can be modified.

Reverting back to a single active interface, the checkbox cannot be modified. This is repeatable.
EDITED@ebony:~$ traceroute6 ipv6.blizzard.com
traceroute to ipv6.blizzard.com (2001:1890:e000:c01:dad3:85ff:fed9:ce24) from EDITED, 30 hops max, 24 byte packets
1 EDITED (EDITED) 0.24 ms 0.185 ms 0.092 ms
2 gw-91.wlg-01.nz.sixxs.net (2001:4428:200:5a::1) 30.708 ms 30.648 ms 29.679 ms
3 ge0-1-6.v6wlg0.acsdata.co.nz (2001:4428:0:6::1) 40.055 ms 30.972 ms 30.019 ms
4 ge0-0-2321.v6akl1.acsdata.co.nz (2001:4428:0:911::4) 41.265 ms 42.079 ms 40.834 ms
5 ten-0-0-0-134.bdr01.akl02.akl.VOCUS.net.au (2402:7800:110:511::d) 42.121 ms 42.106 ms 42.002 ms
6 ten-0-2-0-400.bdr01.akl01.akl.VOCUS.net.au (2402:7800:110:1::1a) 42.384 ms 41.455 ms 41.699 ms
7 ten-0-1-0-61.bdr02.akl01.akl.VOCUS.net.au (2402:7800:110:1::21) 165.73 ms 166.193 ms 165.964 ms
8 pos-0-1-1.bdr01.pao01.ca.VOCUS.net.au (2402:7800:100:1::2a) 166.631 ms 166.734 ms 166.47 ms
9 paix.ipv6.he.net (2001:504:d::10) 193.167 ms 194.549 ms 199.232 ms
10 10gigabitethernet4-1.core1.sjc2.he.net (2001:470:0:32::1) 172.524 ms 173.117 ms 175.742 ms
11 10gigabitethernet3-1.core1.lax2.he.net (2001:470:0:16a::2) 182.938 ms 181.699 ms 175.335 ms
12 2001:470:0:1e6::2 (2001:470:0:1e6::2) 200.321 ms 175.342 ms 175.658 ms
13 * * *
14 * * *
15 2001:1890:e000:809::1005:d001 (2001:1890:e000:809::1005:d001) 194.628 ms 194.986 ms 200.058 ms
16 * * *
17 2001:1890:e000:809::1005:d001 (2001:1890:e000:809::1005:d001) 186.823 ms 186.705 ms 186.409 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Quirk,

We're interested in seeing a trace route to the IPv6 servers if you could provide one. From a command or terminal window use the command provided below:

1. MS : tracert -6 ipv6.blizzard.com or tracert -6 2001:1890:e000:c01:dad3:85ff:fed9:ce24
2. Mac OS : traceroute6 ipv6.blizzard.com or traceroute6 2001:1890:e000:c01:dad3:85ff:fed9:ce24
3. Linux : traceroute6 ipv6.blizzard.com or traceroute6 2001:1890:e000:c01:dad3:85ff:fed9:ce24

I've included the command for other OSs if others would like to provide the information as well.
________________________________________________
Technical Support
Want to speak with someone directly? http://us.blizzard.com/en-us/company/about/contact.html
How's my driving? https://www.surveymk.com/s/R5D3LCF

Check your G-diffuser system!


I got "Request timed out" from start to finish.

IP: 2001:0:4137:9376:30ec:19a1:e7c2:b616

Edit: I attempted an IPv6 tunnel and couldn't log on to any wow server after that. Promptly disabled it. I have also reinstalled network drivers, reset all default network settings and used TCPOptimizer to ensure no settings were modified beyond the default network adapter parameters.
Tracing route to ipv6.blizzard.com [2001:1890:e000:c01:dad3:85ff:fed9:ce24]
over a maximum of 30 hops:

1 16 ms 13 ms 13 ms 2002:c058:6301::
2 13 ms 12 ms 13 ms ge-6-28-ur05.area4.il.chicago.comcast.net [2001:
558:fe04:1::1]
3 13 ms 12 ms 13 ms te-8-4-ur04.area4.il.chicago.comcast.net [2001:5
58:300:e7::1]
4 16 ms * * te-1-3-0-0-ar01.elmhurst.il.chicago.comcast.net
[2001:558:300:56::2]
5 * * * Request timed out.
6 38 ms 36 ms 37 ms pos-1-12-0-0-cr01.chicago.il.ibone.comcast.net [
2001:558:0:f68d::1]
7 39 ms 41 ms 39 ms pos-1-1-0-0-pe01.350ecermak.il.ibone.comcast.net
[2001:558:0:f589::2]
8 86 ms 64 ms 51 ms 2001:1890:1fff:301:192:205:37:13
9 82 ms 137 ms 82 ms cr2.cgcil.ip.att.net [::ffff:12.122.86.42]
10 82 ms 82 ms 82 ms cr2.sl9mo.ip.att.net [::ffff:12.122.2.22]
11 81 ms 83 ms * cr2.kc9mo.ip.att.net [::ffff:12.122.28.89]
12 94 ms * 211 ms cr1.dlstx.ip.att.net [::ffff:12.122.28.85]
13 81 ms * 81 ms cr1.phmaz.ip.att.net [::ffff:12.122.28.182]
14 * * * Request timed out.
15 82 ms 131 ms 81 ms 2001:506:2001:601::1111:f99a
16 80 ms 80 ms * 2001:1890:e000:809::1005:d001
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
I got "Request timed out" from start to finish.

IP: 2001:0:4137:9376:30ec:19a1:e7c2:b616

Edit: I attempted an IPv6 tunnel and couldn't log on to any wow server after that. Promptly disabled it. I have also reinstalled network drivers, reset all default network settings and used TCPOptimizer to ensure no settings were modified beyond the default network adapter parameters.

Are you connecting through a router? Most of them are not compatible with iPv6, as that was the problem in my case.
06/07/2011 08:31 PMPosted by Abysis
Use hurricane electric ipv6 tunnel seems to work with WoW as it is 6in4.


I haven't heard of this tunnel system before. I'm wondering where I could possibly locate this tunnel to enable IPv6 on my network. Also, would Blizzard approve this to be used on their network?

Just don't want to break the Terms of Use and Terms of Service, If I do this that is.;)

Thanks! =)
Hi,

Source IPv6 address of 2402:6000:101:200:225:4bff:fea8:1b36 (native from an OSX machine), traceroute to ipv6.blizzard.com below. Despite the changes to config.wtf, the enable IPv6 option remains grayed out

traceroute6 to ipv6.blizzard.com (2001:1890:e000:c01:dad3:85ff:fed9:ce24) from 2402:6000:101:200:225:4bff:fea8:1b36, 64 hops max, 12 byte packets
1 2402:6000:101:200::1 0.582 ms 0.371 ms 0.331 ms
2 gigabitethernet0-3-927.wnmur-rt1.fx.net.nz 12.155 ms 2.043 ms 2.014 ms
3 2402:6000:0:5::2:1 14.135 ms 14.269 ms 13.415 ms
4 2402:7800:110:50e::1 14.790 ms 15.205 ms 13.704 ms
5 ten-0-2-0-300.bdr02.akl01.akl.vocus.net.au 14.258 ms 14.133 ms 14.841 ms
6 2402:7800:110:1::5 14.116 ms 14.742 ms 14.406 ms
7 ten-0-1-0-61.bdr02.akl01.akl.vocus.net.au 138.814 ms 138.726 ms 138.392 ms
8 pos-0-1-1.bdr01.pao01.ca.vocus.net.au 138.615 ms 139.111 ms 138.817 ms
9 paix.ipv6.he.net 166.966 ms 170.453 ms 175.487 ms
10 10gigabitethernet4-1.core1.sjc2.he.net 139.172 ms 144.013 ms 140.577 ms
11 10gigabitethernet3-1.core1.lax2.he.net 148.371 ms 146.836 ms 175.300 ms
12 2001:470:0:1e6::2 159.710 ms 147.626 ms 149.113 ms
13 * ^C (timeouts from here).

I'm CTO of the ISP I'm using, if I can help out with further information please let me know :)

Regards,

Mike.


Quick follow up - adding

SET enableIPv6 "1"
SET useIPv6 "1"

to the config file has enabled the protocol to work correctly.

06/08/2011 03:26 PMPosted by Teloraelin
Use hurricane electric ipv6 tunnel seems to work with WoW as it is 6in4.


I haven't heard of this tunnel system before. I'm wondering where I could possibly locate this tunnel to enable IPv6 on my network. Also, would Blizzard approve this to be used on their network?


There are several options for tunnel brokers. The main ones are tunnelbroker.net (the HE.net run one, whose network I've seen in almost every single traceroute posted), SixXs and Gogo6. They each have their pros and cons depending on your network location, technical capabilities, etc.

As to Blizzard involvement, it's not really 'on their network'. The tunnel enables you to use IPv6 if your ISP doesn't provide it. It's not much different than using a VPN when you get right down to it.
I'm home from work now, so I can't do any further testing, but I thought I'd add my 2 copper.

Loaded WoW on both a Mac running the latest version of 10.6, and an older WinXP box. Both on the same network, passing the IPv6 tests with 10/10. The Mac wouldn't let me check the "enable IPv6" option. The PC let me check it without any issues, and I was able to log into one of the IPv6-enabled realms and play with no problems. I only had the enableIPv6 line added to my config file, not the useIPv6 (the additional suggestions hadn't been posted yet when I was testing :( ). Sounds like there's some sort of bug with the IPv6 detection under MacOS.
06/08/2011 02:06 PMPosted by Superclaw
Just an aside Blizzard, blocking certain ICMP6 messages breaks IPv6 features such as PMTUD which could break things for certain network stacks.


Indeed - ICMP6 is REQUIRED and MUST NOT be blocked for ipv6 to work properly according to standards.
SET enableIPv6 "1"
SET useIPv6 "1"



This worked for me also
06/08/2011 05:55 PMPosted by Trolan
There are several options for tunnel brokers. The main ones are tunnelbroker.net (the HE.net run one, whose network I've seen in almost every single traceroute posted), SixXs and Gogo6. They each have their pros and cons depending on your network location, technical capabilities, etc.


Ya, I do have a new wireless router that was provided to me from Telus Communications, when I got Optik TV from them. This is TV service on the same line as my internet line, except it goes thru my router to the Telus Optik PVR box, and then to my TV.

I'll take a look at the IPv6, brokers, you mentioned though and see what I can do from there. =)

06/08/2011 05:55 PMPosted by Trolan
As to Blizzard involvement, it's not really 'on their network'. The tunnel enables you to use IPv6 if your ISP doesn't provide it. It's not much different than using a VPN when you get right down to it.


Yes, I do understand this. I just thought we had to edit a file in the World of Warcraft directory though, in order to enable this setting. Just want to ensure if I did this in the future if it then would affect the Terms of Use and Terms of Service, as I don't want to break Blizzard's policies. Unless this is extended after a single day of joining this event and is permitted in the future to do so.
Am I the only one getting better latency on IPv6 than IPv4 ? (100ms vs 120ms)
Teloraelin ,

The file you edit is your config.wtf file. We routinely have people make changes to that file while troubleshooting. It isn't a game file, it's just a text file holding settings. You won't have any policy issues editing it.

____________________________________________________________
Account and Technical Services
Mon-Fri 12pm-8pm
Feel free to rate my services at the following link: https://www.surveymk.com/s/T8S7BX2

"A Lannister always pays his debts."

Join the Conversation

Return to Forum