Re:New phenomenon breaks inbound TCP policing
by bugtoo on Tuesday June 07, 2016 @11:52AM
(#11855310)
Hi chopsywa, on the Mikrotik, did you try to use PCQ with src-address only as a classifier on the Queues? This will create a unique bucket for each host on the lan, therefore it doesn't really matter how many connections the host will open (and where), the bandwitdh will be equally distributed among all hosts on the lan as soon as a new PCQ queue is automatically created. Be sure to remove the port and dst-address option.
Daniel
Re:New phenomenon breaks inbound TCP policing
by riskable on Tuesday June 07, 2016 @10:09AM
(#11854604)
Well, the good news is that this is a temporary problem. There's only so many computers out there that will get the Windows 10 upgrade and presumably that number will drop like a rock as PCs either get upgraded or the users switch to Linux ;)
The real kicker is that the connections are all to servers (Akamai) on port 80, so any serious blocking breaks all web browsing. The cynic in me says the whole Windows 10 update thing has been made to operate in lockdown environments when non-well known ports are blocked. Intentional, or not, the Internet is basically broken while this happens as Windows is ubiquitous and people all over the world who have successfully used inbound rate limiting to create successful shared Internet connections are going to be getting angry support calls. I hope my post goes viral so it starts to get seen by the likes of Microsoft and Akamai engineers. The local ISP I spoke to where I initially noticed this problem pretty much fobbed me off with the old "nobody else has reported the issue."