On Fri, January 13, 2017 3:17 pm, Bob Camp wrote: > It just so happens that I'm trying to track down an issue with my WiFi > as I type this.
This is getting off topic for time-nuts very quickly, but use bufferbloat and "make wifi fast" as search phrases. The guy who did a lot of the work on queue disciplines to solve bufferbloat (over sized buffers in network devices and drivers adding unnecessary excess latency) turned his attention to Wi-Fi and found that Wi-Fi devices and drivers were even worse, and the devices often had firmware running on them that hid the sources of latency. Because you need to be able to measure latency and bandwidth concurrently they put together some scripts using combinations of iperf, netperf, ping, and other tools running concurrently to measure latency under conditions of various levels of simultaneous bandwidth use. You can start here: https://www.bufferbloat.net/projects/ https://www.bufferbloat.net/projects/make-wifi-fast/wiki/ For the level of problem you are trying to diagnose ping is probably an appropriate tool, although it doesn't give much diagnostic information when the reply time increases, it is more of a "what" than a "why" tool. -- Chris Caudle _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.