no, that would defeat the purpose of gaging the router throughput.
I will never use a client connected directly to my gateway, so removing the router from the network chain for testing would be pointless as that's not a viable topology for me.
no, that would defeat the purpose of gaging the router throughput.
I will never use a client connected directly to my gateway, so removing the router from the network chain for testing would be pointless as that's not a viable topology for me.
You are absolutely right that this is off topic, because the results of the speed tests in this case are not fw dependent. It is pointless to analyze how you measure, since you are comparing the results of two different speed tests that you measured in the same way. You did it right. For me, Ookla measures almost similar results, regardless of where I start the measurement (FF/Edge/router/MS store app/WiFi7) ~923-931/305-327 Mbps 2-6 ms latency. Of course, the result also depends on the selected server. In contrast, Cloudflare only 786/283 Mbps 26 ms. The difference is due to the measurement method. Ookla rather shows whether you reach the speed provided by your provider, while Cloudflare simulates real usage through its own network, which you can achieve. It means that Cloudflare’s Speed Test is not trying to show what the maximum speed your connection can reach, but rather what it typically delivers.