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: «3/4»
  Go to:

iwantlinuxgames 9 September 2019 at 8:08 pm UTC
i shall have to try this when i get home this evening. i haven't had a sub for quite awhile...many months now...decided yesterday i would pick up some game time. activate my game time card, install classic, and i notice a notification about a ddos attack going on. tried for about an hour to get logged in, but never could get ingame.
sigz 9 September 2019 at 8:09 pm UTC
prefer the ipv6 setting in first place if you can, it's never the good choice to have to modify the system to fix a program.
Liam Dawe 9 September 2019 at 8:40 pm UTC
sigzprefer the ipv6 setting in first place if you can, it's never the good choice to have to modify the system to fix a program.
As I understand it, ipv6 doesn't work on all servers so the TTL fix is likely the better option.
Madeanaccounttocomment 10 September 2019 at 3:32 am UTC
lejimster
PieOrCakeI played WoW for over a decade, but thankfully managed to kick the habit before the BfA xpac was released. I've been WoW-free for a couple of years now, and holding steady!

I played it for a 2 week trial thingy years ago and I barely left my room during that time. When the trial expired I decided against buying it for my health lol.

I played for two or three years myself and I still consider Burning Crusade to have been the best game experience I've ever had. Unfortunately I have an extreme habit-forming personality and so I avoid MMORPG's because I'm still at a point in my life where I need to be proactive with other things.


Last edited by Madeanaccounttocomment at 10 September 2019 at 3:33 am UTC
Guppy 10 September 2019 at 8:20 am UTC
Spendt the better part of yesterday troubleshooting this on the wow forums surprising how many Linux wow players there are.

But speaking of - the one thing that doesn't work for me with Lutrix in wow (classic) is the in game ticket system, it seems to want to load a webpage but instead just shows notting. Anyone have a fix for that?
devnull 2 years 10 September 2019 at 3:51 pm UTC
Setting a default of 128 is kinda silly. I don't play WoW but if you can identify what networks are required (with tcpdump for example), a better option is a policy route. ie


iptables -t mangle -I OUTPUT -d 1.1.1.1 -j TTL --set-ttl 128


Bit more advanced but simpler overall:

ipset create blizzard hash:net
ipset add blizzard 1.1.1.0/24

iptables -t mangle -I OUTPUT  -o enp5s0 -p tcp  -m set --match-set blizzard dst -j TTL --ttl-set 128
iptables -t mangle -I OUTPUT  -o enp5s0 -p udp  -m set --match-set blizzard dst -j TTL --ttl-set 128


Effectively doing the same thing but easier to update one table rather then add mangle rules for each block/ip.

From a security standpoint I've always dropped the TTL on internal networks, helps to limit leakage. I'd also be very surprised if this lasts long.

Edits: derpyness


Last edited by devnull at 10 September 2019 at 3:52 pm UTC
CanadianBlueBeer 10 September 2019 at 5:02 pm UTC
Well, that explains why it stopped working.

Will test that for tonights gaming. (I hate having to reboot into that "other" system)
Guppy 10 September 2019 at 8:43 pm UTC
CanadianBlueBeerWell, that explains why it stopped working.

Will test that for tonights gaming. (I hate having to reboot into that "other" system)

It stopped working? been playing for the past 3 hours with no problems - granted I use 80 for TTL
sigz 11 September 2019 at 2:54 pm UTC
Liam Dawe
sigzprefer the ipv6 setting in first place if you can, it's never the good choice to have to modify the system to fix a program.
As I understand it, ipv6 doesn't work on all servers so the TTL fix is likely the better option.

That's why I said if you can. I should have better said, "it's not the best choice to modify the system, but it can be considered on last solution"


Last edited by sigz at 11 September 2019 at 2:56 pm UTC
Liam Dawe 11 September 2019 at 3:08 pm UTC
Guppy
CanadianBlueBeerWell, that explains why it stopped working.

Will test that for tonights gaming. (I hate having to reboot into that "other" system)

It stopped working? been playing for the past 3 hours with no problems - granted I use 80 for TTL
I think they were talking about WoW not working, not the fix

devnullSetting a default of 128 is kinda silly. I don't play WoW but if you can identify what networks are required (with tcpdump for example), a better option is a policy route...
This is just the quickest and simplest solution to get people back up and running while it was an issue.
  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