4 ms·
I was just browsing websites that were loading unusually slowly, so did the usual ping/mtr to investigate, which pointed to the router. From there and a bit of
by zzzcpan 8y ago
I was just browsing websites that were loading unusually slowly, so did the usual ping/mtr to investigate, which pointed to the router. From there and a bit of tcpdumping the cause turned out to be UDP traffic to Google from another person, who was watching videos I think.
- the8472 8y agoyour router shouldn't introduce noticable latency. If it does it either has a weak CPU or network queues that are too large. In the former case you need to upgrade hardware, in the latter you need a firmware that supports CAKE.
- londons_explore 8y agoSome routers have hardware NAT for TCP, but use the CPU for UDP. Also, some routers prioritize all UDP packets because they treat them as VoIP. Then all TCP suffers. Some service providers traffic shape UDP because uTorrent uses it (UTP) on random port numbers.
- the8472 8y agoIf the router can't handle a scenario where you replace all TCP with UDP then it's a cheap plastic toy in my eyes. Don't blame the protocol, blame the router. Sending MTU-sized UDP flows to a dozen targets at most is not even the most extreme, non-malicious scenario you can encounter on networks. Similar arguments go for the prioritization.
- londons_explore 8y agoQuic measures delay so won't fill big buffers.