something interesting for the tech department. one of the firewall rules i created to try to fix this was for 24.105.0.0/18
owned by blizzard. i made the rule free/open bidirectional. didn’t help. but…
We are currently experiencing a power related outage in the Keedysville and Sharpsburg areas. Our technicians are aware and working toward resolution. We apologize for any inconvenience and appreciate your patience.
i just talked to Antietam and they made no routing or firewalling changes this morning at all. 9am EST is 6am Pacific so i’m assuming someone made a routing change at blizzard’s ISP. no TCP packets are getting ACK from 24.105.0.0/18 or from 137.221.96.0/19 to our ISP on ip range 24.170.224.0/22 i used wireshark in testing. many retrans but no ACK
Antietam confirmed and double checked they made no changes this morning
wireshark is showing many retrans packets like these:
No. Time Source Destination Protocol Length Info
138 22.521665800 192.168.50.195 137.221.105.232 TCP 66 [TCP Retransmission] 52805 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=256 SACK_PERM
No. Time Source Destination Protocol Length Info
143 23.891615700 192.168.50.195 24.105.52.61 TCP 66 [TCP Retransmission] 52802 → 3724 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=256 SACK_PERM
No. Time Source Destination Protocol Length Info
163 27.627046800 192.168.50.195 137.221.105.232 TCP 66 [TCP Retransmission] 52812 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=256 SACK_PERM
I don’t know what that means but is there a way to get it fixed? on a sidenote i can log into d4 without an issue.
Edit:
I tried the VPN route again and now it logs me in just like always when i set my location somewhere else in the US. However as soon as i turn it off it gives me the error. Definitely a routing issue and since Churrak has shown it is not our isp it must be Blizzard. Would appreciate someone looking into it.
I dont know the best i just installed free proton vpn but i did get kicked and have to relog after 20 mins so i dont know if i would do anything too hard. We shouldn’t have to pay for a vpn when we live in the US to play a 20 year old game.
First, @’ing doesn’t do anything in the forums, just fyi.
Second, Blizzard does not have control over where internet data flows. They take information in and spit it back out. Internet connection issues are handled by your ISP, and that is who you have to deal with when this issue arises.
Third, if a VPN fixes your connection issues, it’s an ISP issue. They control the routing of data.
they made a change at 6am PST yesterday that stopped routing to our network. no changes were made at my ISP. your statement “Blizzard does not have control over where internet data flows“ is completely wrong. their ISP does have control over where their data flows.
My understanding about NAT tables is changes propagate through out the network, while some ISP’s pick up on them pretty fast, others can take a while to update. Not sure how long it will take for your routing to get this update.
a router handling outbound traffic is configured to not route packets destined for the internal network. this is how it should be.
someone made a mistake in designating the internal network. instead of defining it as 24.105.0.0/18 which blizzard owns, they put 24.105.0.0/10 or maybe 24.105.0.0/8 which overlaps external ranges like my ISP
if i had to guess they put 24.105.0.0/8 and left the 1 out. a typo