Aha, so it would seem my untangle is to blame. Well, I canât change the ttl on that, itâs managed by the building and not me. So I guess I just canât play until blizz stops blocking it. UghâŠ
Thank you very much, this worked
Funny,I am Windows 10 64 bit, Spectrum ISP Saint Louis, MO. 3 in the house hold here cant play. All other blizzard services work. I am using a Untangle Router that is running a version linux but why should that matter. Its no the os i am running.
Same problem here with an Untangle firewall⊠Still trying to fix it but no success until now.
FIXED!!!
For everyone suffering with Untangle Firewall now, just access your firewall â Configuration â Network â Bypass Rule and create a new rule with the following parameters:
Destination Port => 3274,1119,6012 | Protocol: TCP, UDP;
Mark the rule as enable and VOILA!
Been struggling with this since the DDoS attack on saturday. For some reason, after the attacks, we have to force our firewall to bypass those rules as mentioned on this blizzard article.
Hope it helps!
Bow to the OP Dwarf priest! Much love!
Can anyone from Blizz give us some insight on this issue so we donât have to figure a work around?
I know you can see the thread here about Linux users. Can we get some type of support? Or at least something. This affects android phones too as they run a Linux kernel.
Hello, linux users that cannot login.
I fixed the problem on my computer by running
echo 128 > /proc/sys/net/ipv4/ip_default_ttl
as root.
you can also run
sudo sysctl net.ipv4.ip_default_ttl=128
this fixed the problem for me on NixOS staging
2018
whoopsie
This fixed the problem for me on Classic. But for retail something else seems messed up, I can log in and hear my character and wow sounds, but the game window shows a frozen login screen.
This worked for me last night. Had issues again today, ran it again and it worked instantly. Must have reset or something when I rebooted. Thanks again.
This worked for me. Ubuntu 18.04 and Wine Staging.
THANKS SO MUCH.
@Blizzard â you make me sad.
Howdy!
I wanted to make sure you all knew we are investigating these connection issues. I do not have any additional information to provide at this time. Just know we are on it.
Thank you.
Thank you @Zuvykree. This will be of great relief to many of us across multiple operating systems and WAN access devices. I know myself and many of the people involved in this effort have been hopping forum to forum to assist people with thier accounts. An official fix or at least position for it would be detrimental to a permanent solution, whether community supplied or developer supplied.
Thanks again to everyone who has assisted in these efforts!
Upon further investigation, I know a guy who says this may be related to a âMiraiâ botnet attack using linux based internet of things. The default TTL for many linux seems to be fairly high - as much as 255. So setting the ip_default_ttl to 128 matches your system with what Windows 10 typically has for a setting thereby making your machine be not targeted for packet dropping.
I understand that Blizzardâs core business is windows and mac users and linux users are a tiny fraction. It would be really nice to at least have some kind of ability to reach out to the linux users and give them a simple fix like what was posted above rather than have to rely on crowd sourcing. Changing the setting on gaming systems would not have an impact on all the IOT systems in the wild that are actually responsible for the bad packets.
This is a mititgation technique to deny access to bot nets for sure, it is a passive check that blocks on certain TTL values (this may not be the only thing they are checking packets via DPI on but at least the work around for most of us is rather easy)
Iâve posted several things about this issue, combined multiple fixes on each of the 3 forums I know about. and personally proven this is fingerprinting based on linux using NAT vs bridged networks on my linux box via vmware workstation [vm player])
This only started to happen just after âthey continued to monitor the situation of the DDOS attacksâ and legit blocked several VPN / Android mobile or tether customers / windows 10 users of certain builds that use odd TTL values / etc, even the odd mac user is blocked.
Some could be IP bans, others could be user temp bans, or a combination of all of the above.
^ What this fellow said.
Came back between Blizz DDoS tweets long enough to level an alt to 7 then dcâd. I waited it out until the launcher didnât display the announcement and still I timeout on every realm.
Side note, I was put into a 2min queue for the login server at one point before the massive server crash 
we got hosed.
Regards ipv4 I have been behind nat the entire time. The only thing needed for me was the increase in ttl. Which I have since dropped back to the default of 64 and it is still working. In game at the moment with tcpdump running on eth0 watching packets with ttl 64 leaving and packets from the game with ttl 51 coming back.
Yes blizzard uses 55 as the TTL for some packets Iâve noticed, spent a fair amount of time examing and testing stuff before going to bed (actually found it more fun compared to playing wow⊠oddly enough)
Being behind NAT with the TTL adjusted will work just fine, my linux box with a virtualization hypervisor software running in linux setup with windows 10 had the same issue until I bridged the connection to my router (meaning the OS had a good TTL but my linux box did not and it is all because the VM hypervisor uses my linux network default TTL as itâs own)
If I had made adjustments to my TTL on the linux box and used NAT on the VM it would have been just fine, it was just a proof of concept.
Another way you can get around adjusting the whole TTL is to try this