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

Same issue. Haven’t been able to get in since yesterday afternoon. Stuck on “logging into game server” Can’t even get into retail now.

SOAB

IT IS A LINUX BAN ISSUE (with however the packets are fingerprinted)

I forgot I had used NAT in virtualbox for the interface (usually 1 bridge the connection) before moving it to vmware.

Once I bridged the connection instead of NAT, BAM character is there.

OK so now this is proven, they are doing IDS scanning and fingerprinting of the packets as mentioned before.

UPDATE: My character is where it was when I got stuck and I can move around no problem.

I saw some reports about IPv6 working either here or on Reddit somewhere, so I looked up my router model and figured out how to enable IPv6 in my router’s settings (192.168.0.1). After enabling, I went into classic wow, went to Settings>Network, checked the box to prefer IPv6, then closed classic wow and reconnected to my wireless network. After reconnecting, I tried logging in and now I’m ingame again!

So, if you have this issue, figure out how to enable IPv6 on your router, then enable IPv6 ingame, and reset everything and you should be able to play. I’ll report back if I get banned again.

2 Likes

Just wanted to say me too. Was playing this avo (about 10 hours ago) actually during the DDoS but then at some point I was disconnected and haven’t been able to reconnect yet. I can get to the server select screen OK, but then when I try to actually connect it hangs, then I get the error at the top of the post. StarCraft 2 still seems to be working though.

Linux osiris 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u1 (2019-07-19) x86_64 GNU/Linux
wine-4.12.1 (Staging)

Someone mentioned TCP fingerprinting, so I tried
echo 128 > /proc/sys/net/ipv4/ip_default_ttl
which seemed to let me in.
(also dos guys don’t read this pls)

58 Likes

And we have a winner. Did that and straight in game.

Changing ttl works, look at this genius.

1 Like

It works!!!

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

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

2 Likes

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.

3 Likes

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

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?

Actually login to root with just “su”

Then run it.

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)!

9 Likes

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

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

MVP of the night right here <3

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

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.

You are an absolute wizard.

Pray Bliz doesn’t block this as well…