(Not so) Secret test plan

[richb-hanover]

I see Crusader as an important component in the quest to characterize bufferbloat.

We have pretty good web-based tests (speedtest.net, Waveform, Cloudflare) and applications (flent, netperf) that test from the laptop to servers out on the internet. But there's no way to determine how much those results are influenced by latency induced by the local wifi.

Crusader makes it straightforward to test against a server on the local network. This gives a handle on the WiFi bloat, which can be factored out of the overall bloat measurements.

This leads to a few observations and questions:

• I just realized that it might be possible to measure both "WiFi bloat" and "ISP bloat" in one Crusader test by using the Latency peer. Perhaps it would be possible to run a test against a Crusader server on the internet (to get overall latency), and also measure the latency to a peer on the local subnet. Do I have that right?

• Not everyone has a spare Raspberry Pi lying around so I'm experimenting with Crusader installed directly on the router. This is probably a doomed effort: it appears that some (many? most?) routers (the Beryl MT3000, for example) aren't fast enough to support the Crusader server without affecting latency/throughput.

• But maybe a Crusader server running on the router could act as a Latency peer without too much effect on its ability to pass traffic? (I suspect so...)

Thanks.