BTW. There is another thread with regards to the same issue:
Was told on that thread that GMs can manually unblock users. However atm it seems like a temp measure as you can get hit by the ban hammer again later
2 Likes
I canât log in after 12-noon PST.
ubuntu 18.04, lutris with wine 4.9, California ISP, Bigglesworth server
ISP assigns me a valid IPV6 address but that still doesnât solve the issue.
Yes, I tried for about 3 hours connecting on my linux install, figuring it was just remnants of, or ongoing, attacks and no successâŚalways that same error. I copied over the same exact installation folder over to my windows 10 partition (on the same computer, no network changes), rebooted, and the game launched perfectly.
I think i have bad news , its not first time that Blizzard cannot fix problems about ddos and first choice its âTemporary BANâ for linux users , i just live chat with GM and sadly she point about System Requeriments (how someone with bad skills like this work in a company so big , its like a robot)
Same issue here. Wine/Lutris on Arch Linux 5.2.11
Perhaps there is some way to edit the network headers to a different operating system as a temporary fix?
Slackware Linux
Oceanic - Remulos
I can play on US servers using IPv6, but that doesnât help me because Blizzard never bothered turning on IPv6 in the Australian data center. Those servers are all IPv4-only. My connection packets just get ignored on IPv4.
I honestly believe that Blizzards hamfisted response to the DDoS situation is worse than the DDoS itself. At least the interruption of service for everyone was fair in that no one could play. I slept 2-3 hours a night a for a week to stay ahead of the pack, now I get to have blizz cut my legs off in the last mile. God only knows how long it will take them to figure out what they did wrong, assuming they care, of course.
In the meantime, windows users get to play and surpass everything I worked for because some obscenely incompetent IT person doesnât understand packet filtering.
I wish we could get a rollback, but windows sub money is more important than ours. I wanna die rn : (
2 Likes
Actualy if delay so much to Remove Ban from linux users i will ask refund and go play some private server no make sense stay 1 week behind everyone cuz company dont have skilled IT workers
2 Likes
FYSA:
I run a IPS/IDS and application based firewall (Untangle) in front of my Windows 10. The moment I put my desktop computer in bypass mode on the firewall I received an instant connection to the game.
I assume with this knowledge you can likely do the same with IPTABLES, UFW, or pfSense to see if it works. Pop a hole in the firewall to prevent any form of NATing that replaces your header after it scans your outbound traffic.
Hope this helps a few of you all⌠I gotta head to work or I would expand upon this and see what is causing the issue.
2 Likes
A rollback is pretty harsh, and itâs not like there was an even playing ground really to begin with with all the disconnect issues the first couple days. I think itâs much more reasonable to ask for a refund instead for affected LInux users. Blizzard KNOWS who the affected LInux users are too, since I had a GM manually lift my ban. So a widespread subscription refund should occur and is possible from Blizzardâs side.
(I am also affected by this bug and I use Linux/Lutris, by the way.)
1 Like
Also cannot connect
Pop OS 19.04 / Lutris
So i took a virtualbox image of windows 10 that I had kicking around and converted it to vmware player via OVF, enabled acceleration and install vmware tools then copied my classic wow folder to it and I get the same issue but this could be something about the specific windows 10 instance/build version.
VMware player workstation 15.1.0 build-13591040
Windows 10 version 1809 (OS Build 17763.678)
Same error, quick disconnection.
Windows updates had been auto-updated a few days ago.
Iâm going to move this installation to my wifeâs PC tomorrow if this issue is not resolved and see whats going on from there, Iâll also compare the Windows 10 OS / build info.
There is no reason why this should not work under VMWARE since they have really good support for 3d applications compared to virtual box (I also tried virtualbox too but that was just a big waste of time)
Repair install of WoW said it didnât require or need to make any changes so yay no known corrupt files.
Even went as far as renaming WTF, Addon, Cache, GPUcache folder, nope⌠same issue.
Meh, spent too much time on this tonight and frustrated.
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