@ShorehamNICK wrote:
... I find your response only confirms my statement that throttling or if you want to call it prioritisation is applied, the new hardware has the ability to identify traffic it thinks should be given lower bandwidth, if your endpoint (laptop) is locked down and you have no way to override the way in which your router identifies the traffic your are stuffed
Au contraire (bold). What I'm suggesting is almost the opposite.
The new hardware does not tag any traffic as low priority. It marks what it thinks should be high priority e.g. EE TV and Voice services. The problem is, it also 'accepts' the tagging any other tom/**bleep**/harry application decides to apply on your local network. This potentially saturates the EF/high priority queue out in the broadband network (which is where the prioritisation is actually honoured).
If you want to look at it from a 'throttling' perspective then I'd be inclined to say it's actually the old, 'working' hardware that's 'fiddling' with stuff - by ignoring/stripping any priority tagging that is done by local applications so it's treated the same as (almost) everything else. Presumably, this is what the new hardware also needs to start doing.
It's a subtle distinction, but it's actually the high priority queue here that's being assigned the (significantly) lower slice of bandwidth. It's just looking like too much is being shoved into said queue by the newer hubs e.g. Teams Calls.
Completely agree that if you can't alter the behaviour of software due to a laptop being locked down, then it leaves you few options outside of replacing the hub/waiting for a fix. Exercise caution if you go the third party hub route though, as I think there were comments early on in this thread of a TP Link router exhibiting similar behaviour.
Edit: seem to have fallen foul of the forum censoring in a fairly amusing way 😂
