Hi like many others i am currently unable to log into WoW
Logging into battlenet and getting to the server selection works just fine but when i select the server the client tries logging me in for a few seconds and then kicks me back to the Clients login screen
no error message or indicator what could be wrong at all
i’m on windows 10
anyone else encountered this and found a fix? resetting my router and dnsflush yielded no success
Good morning Bonedrone,
Could you please run a WinMTR and post it here so that we can see if there is anything blocking your connection?
Kind regards
What’s your opinion?
there is word going around the blizzard is flagging linux users after the ddos the servers experienced yesterday.
This is unacceptable!!! next month the subscription won’t be renewed, and I encourage all other linux wow players to do the same thing.
I’d guess that isn’t intentional, just a side effect of something they did because of the DDoS attacks.
Agree.
Since Linux is not officially supported, I don’t expect to be supported or Blizz to hold my hands to install the client. Thank you very much I am able to take care of this myself using the amazing opensource support.
What I do expect is * * * NOT TO GET F’D ON PURPOSE * * * !!!
Well, for what it matters, you were probably “f’d” by accident, not on purpose.
Hello Kiemmaki, i ran one as instructed in the link, here are the results
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| internetbox.home - 0 | 607 | 607 | 0 | 1 | 22 | 1 |
|1.216.203.62.dynamic.wline.res.cust.swisscom.ch - 0 | 607 | 607 | 7 | 9 | 77 | 8 |
| 193.134.95.65 - 0 | 607 | 607 | 12 | 15 | 89 | 12 |
| i68geb-005-bun11.bb.ip-plus. net - 0 | 607 | 607 | 12 | 14 | 126 | 13 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| lag-27.ear3.Frankfurt1.Level3. net - 1 | 599 | 597 | 19 | 23 | 209 | 21 |
| ae-1-3109.edge3.Frankfurt1.Level3. net - 0 | 607 | 607 | 18 | 20 | 135 | 20 |
| BLIZZARD-EN.edge3.Frankfurt1.Level3. net - 0 | 607 | 607 | 21 | 26 | 146 | 22 |
| 137.221.80.35 - 0 | 607 | 607 | 25 | 29 | 138 | 26 |
| et-0-0-2-br01-eqpa4.as57976. net - 0 | 607 | 607 | 25 | 31 | 138 | 27 |
| be1-pe01-eqpa4.as57976. net - 0 | 607 | 607 | 26 | 28 | 132 | 27 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
Hello Bonedrone,
Thanks a million for the data. I have gathered all the feedback from the various threads and escalated them. I will update you all as soon as I here something back to update on.
Kind regards
What’s your opinion?
Not to spam this guys thread, but as someone with education from an IT university (not working in the sector) I find it highly unlikely that the guys who patched the DDoS fix were unaware that they were going to gimp linux users.
Well, in theory probably, but if it’s a stressful situation where players are dropping from servers and so on, you mightn’t remember everything you’ve ever learned. You go with something and see if it works, etc.
i found someone in another thread mentioning executing
“netsh int ipv4 set glob defaultcurhoplimit=128” in the command console
this worked somehow and i am able to enter the game again
Thanks for investigating/escalating. Most interesting fact seems to be that we’re seeing all systems/connections blocked coming in with a IPv4 TTL being 64 … notably android mobile tethering and all linux/wine gamers. Changing the TTL to 128, the Windows default), works.
But you can’t change that on mobile/tethered connections, and if the provider modifies the TTL you are locked out for good.
It seems even some Windows installations have set a TTL of 64 (DefaultTTL of 0x000040) for some reason, but who knows what all those installers do to users systems… any app could change the default TTL
nvm the problem is back…
I’ve been using my phones 4g connection tethered to my PC and have been since classic launched but now i’m getting the same problem as OP, now i’m unable to play the game at all so if it’s not fixed soon i’m just gonna have to cancel my sub since i can’t play…
one of the tips going floating around is turning on ipv6 in WoW, which i did
however an hour ago i had an idea and actually checked my routers settings and apparently ipv6 wasn’t turned on there, might be worth checking out for you
currently able to play again, no clue if the problem will return tho
No success here, ipv6 is on and normally using it, but can’t connect either way