News for hackers. Stuff that matters.
Re:New phenomenon breaks inbound TCP policing by jsnell on Monday June 06, 2016 @10:42PM (#11852042)
Where did the HN submission title get UDP from? I don't see anyone in that thread suggesting that the updates were done in UDP, and all the traffic in the trace file is all TCP.

The trace is indeed a total mess, but I'm not convinced it's anything to do with TCP acceleration. There's absolutely massive levels of reordering and packet duplication happening in ways which are not consistent with TCP acceleration at all. It's much more likely that it's some kind of configuration problem elsewhere in the network.

From eyeballing the trace, almost half the payload segments there are duplicates, while a much smaller proportion are retransmits. (You can tell the difference e.g. using IP ids or by TCP timestamp TSvals / TSecrs).

Re:New phenomenon breaks inbound TCP policing by dang on Tuesday June 07, 2016 @02:38AM (#11852803)
We changed the title back to what the article says. The submitted title was "Windows 10 updates via UDP bypassing QoS restrictions".

Submitters: the HN guidelines ask you please not to rewrite titles except when they are misleading or linkbait. It seems like in this case the rewrite made it more misleading.

If anyone suggests a better title, we can change it again.

Re:New phenomenon breaks inbound TCP policing by RachelF on Tuesday June 07, 2016 @03:09AM (#11852904)
Apologies for that, I was trying to summarize the linked article in the title, not to mislead.