You can sign up to get a daily email of our articles, see the Mailing List page!

It seems Blizzard have been having some issues with World of Warcraft and the newer WoW Classic with them coming under a DDoS attack. Their countermeasures (well, whatever they've done recently) seem to have blocked Linux players in Wine but there's a fix.

You will be able to load the game and bring up the server list but once you click to join a server, it just doesn't work. If you find this happening to you, changing your networking TTL can help. First, run this command in your terminal to find what your current default is:

sysctl net.ipv4.ip_default_ttl

Make a note of the number it shows in case you need to change it back for whatever reason. As for the actual fix, set it to something different like this:

sudo sysctl -w net.ipv4.ip_default_ttl=128

128 is the default in Windows 10.

What does the command do? It changes your "Time To Live" and that's all. As always though you run such commands at your own risk, just here to provide information that might be helpful.

Another possible solution is to enable IPv6 support in the WoW Login screen options, although that won't work for everyone and depends on your ISP and Router.

While you're not supported by Blizzard playing on Linux, people have enjoyed WoW for many years thanks to Wine. Sometimes there's blips like this but thankfully the workaround does work for myself and a number of others who also tested it.


If you use a game launcher like Lutris, it can run commands or scripts you set before launching a game and after you close it, so it's handy for stuff like this where you might not want a permanent change. If you wish to try it through Lutris using that method, you will need to open the options for it: right click -> Configure -> System Options tab, tick the Show advanced options box at the bottom and then scroll to find this:

I've just setup two tiny little scripts to put TTL up and down again on launch and exit. Here's my "upttl.sh" script as a rough example:

#!/bin/bash
[ "$UID" -eq 0 ] || exec kdesu bash "$0" "$@"
sysctl -w net.ipv4.ip_default_ttl=128

You will likely need to replace kdesu with gksu if you're on a GNOME based desktop, which is what will show an actual prompt to ask for your root password since it's needed to change the TTL. Make sure the script is set as executable too. You can use the same for when the game closes, with a lower number than 128 or whatever you wish to set. This is just an example though, whatever way makes it easier for you.

Hat tip to Jaco.

Article taken from GamingOnLinux.com.
17 Likes, Who?
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG, Humble Store and Paradox Interactive. See more information here.
About the author -
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
32 comments
Page: «4/4
  Go to:

Caenth 11 September 2019 at 9:18 pm UTC
Yes, I can log in without problems without the fix again, but it saved me from two evenings without WoWC!
14 14 September 2019 at 2:39 pm UTC
View PC info
  • Supporter
I decided to see if I could log in without the workaround, and sure enough (like Caenth), I can! Yay.
  Go to:
While you're here, please consider supporting GamingOnLinux on Patreon, Liberapay or Paypal. We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!

You need to Register and Login to comment, submit articles and more.


Or login with...

Livestreams & Videos
Community Livestreams
  • Resident Evil 2 Remake First Playthrough
  • Date:
See more!
Popular this week
View by Category
Contact
Latest Comments
Latest Forum Posts