None of the parts are broken. Together they don’t work as they are supposed to because of some super intricate process of how usb works when it comes to acknowledging packages. That’s why I wrote the post. The title is true and yeah, it’s sensational but that’s what titles are there for. It’s not a false clickbait.
While it's completely right, even when having read it fully, it isn't so easy to understand unless the reader knows some things (see https://news.ycombinator.com/item?id=50588459 and its children), namely:
* That the "packet size 1024 bMaxBurst 3" (making the 4 KiB window size) is fixed for the whole connection, determined by the RTL8156B, and cannot be negotiated higher, no matter if the monitor is in between or not.
* That this window size is large enough for the NIC---Mac connection to run at full speed, but not enough for the NIC---Monitor-USB-Hub---Mac connection to run at full speed, because the added latency makes the BDP too large.
* If possible to measure, it might be illustrative to measure the NIC---Mac latency without hub directly, to compare it with the `7.6 µs` number going through the monitor (like cibyr suggested). That'd make it more obvious that the monitor increases the latency.
And I agree with dcrazy's sibling comment that the RTL8156B in the UGREEN _is_ to blame. It uses a send window size that cannot possibly deliver the advertised bandwidth behind a hub.
Anyway, great post that shows that just because you buy a device that says N Gbit/s and delivers N Gbit/s when directly attached, you cannot be sure that it'll be equally fast when attached to a form of "longer cable".
That said, I think you’re being too charitable to UGREEN. They shouldn’t advertise a product as 2.5Gb/s if it can’t actually transfer 2.5Gb/s to the host when the signal path includes a hub.
Typical Apple shit. Never had an issue with my Lenovo dock and 2.5G. Additionally, not having an eth adapter built in, in 2026, is enshittified hardware. Typical Apple again
I have had hundreds of USB devices in the past which dont work on a USB hub, its very common. The first troubleshooting step in basically any USB devices manual is if you are having trouble and you are using a hub, remove the hub and plug directly into the device.
The user went way over the top in troubleshooting this issue. Thats the first thing I would have tried. Its not worth the post and the title should really be something like "USB device didnt work with a hub, but did directly in the host" and it would never have made it to the front page of HN other than maybe to be mocked.
I am saying your blame is misplaced, and that the adapter manufacturer deserves the blame because they designed their product around a controller whose USB implementation has so much inherent latency that it mathematically cannot sustain the product’s advertised throughput when connected through a hub. The manufacturer should have tested this extremely common scenario and picked a part that could sustain it.
> The manufacturer should have tested this extremely common scenario and picked a part that could sustain it.
Hard disagree. Maybe if you bought a better one you would expect that, but I would expect a $15 2.5Gb ethernet adapter to not work on a hub right off the bat tbh.
The root of all evil right there. ;)