Linux users unable to log in, WOW51900328/329 error after logging in

Padiccahan-bleeding-hollow · September 9, 2019, 10:38am

It works!!!

Darkodin-moonrunner · September 9, 2019, 10:40am

Neat, we just change the TTL to what would match windows

This worked for me too. Thank you and nice job!

Cherrys-lightninghoof · September 9, 2019, 10:43am

I’m going to take a wild guess and say the TTL filter is to try and filter out traffic coming from infected IoT devices, which usually run Linux.

You can add net.ipv4.ip_default_ttl=128 to /etc/sysctl.conf to make the TTL persist.

Tardigrade-remulos · September 9, 2019, 10:43am

128 TTL has got me connected through to Oceanic realms now too.

Cuvelia-remulos · September 9, 2019, 10:45am

When I try to run:

sudo echo 128 > /proc/sys/net/ipv4/ip_default_ttl
(with or without sudo)

I get:
bash: /proc/sys/net/ipv4/ip_default_ttl: Permission denied

I’m running Pop!_OS, which is an Ubuntu derivative. Is the command something different there?

Wakaba-emerald-dream · September 9, 2019, 10:46am

Actually login to root with just “su”

Then run it.

Cuvelia-remulos · September 9, 2019, 10:48am

Here’s what I ran to get it to change (for other Pop/Ubuntu users):

sudo sysctl net.ipv4.ip_default_ttl=128

Now I"m in and playing! Bless you Poolstool (with PW:Fort)!

Winkway-moon-guard · September 9, 2019, 10:48am

You’ll actually want to use sudo -s instead to get a root prompt.

anon68967974 · September 9, 2019, 10:50am

Woot… Good find, TTL change… Thanks… I’m in.

Cuvelia-remulos · September 9, 2019, 10:52am

MVP of the night right here <3

Kiramekirari-frostmourne · September 9, 2019, 10:58am

Worked perfectly, I will send a few gold your way when I get past the queue

Noirevenin-blaumeux · September 9, 2019, 11:08am

Was watching “The man in the high castle” season 1, and now it’s gone back to the queue, you beautiful bastard!!

also note the “missing” blue post here, at least to make it no so effing obvious.

Kebab-durotan · September 9, 2019, 11:10am

You are an absolute wizard.

Pray Bliz doesn’t block this as well…

Amier-arugal · September 9, 2019, 11:13am

Oh it WORKS!! Such a good find!! Thanks so much Poolstool. I would not have thought of adjusting the TTL.

Daemondread-amanthul · September 9, 2019, 11:17am

Same problem here on Arch running wine-staging 4.15 until I came across the ip_default_ttl solution in this thread. Thanks guys, awesome work!

I really hope Blizzard is going to put a proper fix in place that doesn’t just lock out all Linux users in such a sledgehammer approach, though, before it stops working…

Óni-westfall · September 9, 2019, 11:18am

Damn, there’s some true heroes in this thread. IPv6 did nothing but the TTL fix definitely worked

Raan-yojamba · September 9, 2019, 11:40am

Just throwing in another report of being unable to connect. Tried the IPv6 option to no avail (probably because my ISP doesn’t provide it), but changing the default TTL value to 128 worked perfectly.

Hanzzy-barthilas · September 9, 2019, 11:48am

how do u change TTL value?

Rindal-yojamba · September 9, 2019, 11:52am

Bumping TTL to 128 fixed it for me too.
You have made my day, or more so night by now.

Morgil-stalagg · September 9, 2019, 12:10pm

To keep things tidy and not erased by system updates, I recommend putting the line in /etc/sysctl.d/11-warcraft.conf. That way you’ll remember why it’s there 6 months from now and it’s less likely to be overwritten.