News for hackers. Stuff that matters.

A comment on New phenomenon breaks inbound TCP policing. Parent comment

Re:New phenomenon breaks inbound TCP policing by rhubarbquid on Monday June 06, 2016 @10:43PM (#11852049)
It's also not Windows 10 specific, the post also mentions Office updates
[ Parent | on HN ]
Re:New phenomenon breaks inbound TCP policing by JonathonW on Monday June 06, 2016 @11:08PM (#11852125)
There's a mention somewhere in the middle of the thread that someone had seen something similar with Apple's software updates, too: maybe it's a more general Akamai issue?

Even if it is isolated to the servers distributing MS's updates, I'm having trouble seeing how this could even be MS's fault-- it's the server side (owned and operated by Akamai) that's misbehaving here.

[ Parent | on HN ]
Re:New phenomenon breaks inbound TCP policing by colanderman on Monday June 06, 2016 @11:17PM (#11852147)
I'm not convinced either way. Windows Update is the one opening the dozens of connections (it has to if it's behind a firewall), not Akamai; Akamai's just serving the data. But Windows Update is possibly just calling out to an Akamai library that opens the dozens of connections on its behalf.

If there are also congestion-algorithm shenanigans like the forum post suggests, then Akamai is definitely at fault. But the issue I see is that of connection hogging.

[ Parent | on HN ]
Re:New phenomenon breaks inbound TCP policing by chopsywa on Tuesday June 07, 2016 @09:16AM (#11854229)
Apparently Apple has gone away from Akamai.
[ Parent | on HN ]