WLAN Analysis Tricks | Peter Mackenzie | WLPC Phoenix 2020 

Love the WLAN Monitor Tool! Thanks Peter!

I love the powershell script. I would just like to comment that the IP ID field isn't recommended for this use. RFC 6864 section 4.1 paraphrased says, that in a atomic datagram (a datagram in which hasn't been fragmented and further fragmentation has been prohibited by the Don't Fragment Flag in the IP header) the IPV4 ID field has no meaning and can thus be set to any value desired. Which means the source TCP/IP stack implementation can set this however it desires. And in fact it has been noted in the past that some implementations of TCP/IP stacks have indeed not only used arbitrary number selections to start, but then further do not use a simple linear algorithm to increment the ID field, but instead use a complicated algorithm to change the IP ID field for further packets in the same tuple. In fact this has been used in the past to help identify operating systems. The last bit of info, is that the ID field is usually linked to a tuple if used in non-atomic datagrams, that tuple would be the source address, destination address, and protocol.

Hi Peter, Did you check for latency during the test with multiple clients? I guess throughput goes down but latency should improve when AP is serving multiple clients on 802.11ax network