I had this same issue and assumed it was my IP being blocked. I’m on Windows 10 and connecting directly through the modem worked. I found out that it was because I was running a Linux based router(Untangle).
I logged into my router terminal and applied the fix from the Linux thread and it fixed my issue.
You need to type this into your Untangle terminal:
sudo sysctl net.ipv4.ip_default_ttl=128
It even works if you change it on your PC.
Changing it in windows wasn’t working for me.
Still no dice on PDANET tether or wifi.
I changed it on my Ubuntu desktop and it now all works. Logged in instantly. Haven’t touched my router.(it’s also running Linux )
Yea something tells me the botnets used in the attack probably consist of compromised mobile devices and they just blocked out a lot of the mobile carriers IP’s assuming nobody is using mobile devices to play the game… Just a theory but I submitted a ticket and now will wait to see if they can fix it for me on an individual basis.
when it comes to phone security what’s a good anti-malware thing you could suggest for android that you know about ?
Keep firmware updated and don’t install random apps from the playstore. Playstore is the main source for malware these days.
fter narrowing this down last night and proving it is a issue focused on linux and passive fingerprinting
Here is the info you all need to review to understand what they are doing and why, perhaps some windows 10 users have similar ‘strange out of spec’ packets. (perhaps they ran some network customization tools?)
Please review an external PDF paper from SFU university here on this topic:
SFU article on DDOS and packet fingerprinting (TTL is #1 stealth method) => journals.sfu.ca/apan/index.php/apan/article/download/14/5
UPDATE: just noticed others are modding their TTL in windows, so this confirms they are doing passive packet inspection and looking for abnormal (what they feel is abnormal anways) data in the packets
The the same problem here
Using Ubuntu 19.04/Lutris and ISP Bell … Error WOW51900328
sudo sysctl net.ipv4.ip_default_ttl=128 Try this. Was an instant fix for me.
Yes it’s working well
Been a few hours here now, still can’t even log into the bnet launcher. College campus wi-fi I believe using TWC.
Finally log in and moving around ok for now. Thanks to all who had suggestions. I tried 2 things so don’t know which or if both together was the success. Using Options on the initial Blizzard screen used the scan and repair and check for updates, after it completed the update button lit up so updated (maybe Blizz just released something?) Also did the windows 10 CMD that was suggested in this thread: netsh int ipv4 set glob defaultcurhoplimit=128
Not sure why it wasn’t working for me. I tried changing it in the registry and through power shell and it didn’t work(even after a reboot). As soon as I modified my Linux router it worked immediately.
Also, connecting directly with the Windows 10 machine fixed the problem as well. When using the Linux router, I couldn’t connect until I changed the default ttl.
Maybe your router is forcing TTL value overwrite for all packets?
Hey I was able to get it working, instead of installing a VPN app on my phone I just installed ProtonVPN on my PC and connected to their Switzerland VPN, I can now login just fine (still using PDAnet+ tether for internet connection)
OMG THANK YOU!!! Gonna post this again for people sorting by date. Go to command prompt (run as administrator) type:
netsh int ipv4 set glob defaultcurhoplimit=128
System responds ok.
Try logging in, worked immediately for me.
i use expressVPN currently, but any VPN services cause me to hit upwards of like , 250ms
No issues like that with ProtonVPN connected to Canada from the USA.