![]() ![]() Thus, you might have a strong signal when initially connected, but might be poor after the user starts to use it. We tried this and discovered that the update frequency of this value is perhaps once a minute if not longer (is not specified in that doc, and I could not find it otherwise). Yes, I read it through 6 months ago, and re-read it based on your recommendation. ![]() Really? i gave you 2 reliable ways to do it, pick one I did not see the other method you referenced. Have you used this metric before to measure over time? Have you found it to be useful in any situation? WlanSignalQuality always shows 100 even when there is really poor signal quality. Here’s the results (tested with 5 different wireless NICs to make sure we weren’t seeing a limitation from a single vendor): You should do only one thing at a time, capturing or walking arround for a signal check ![]() But this doesnt work if you want to be connected to a network. The link i provided gives you an accurate RSSI value between -50 and -100 dBm, this value is based on the exact same data you would get from a WlanScan(), it is absolutely accurate in its provided span.Īnd even if i still dont understand the use case here, you still could put the NIC into monitor mode, set it to the desired channel, live decode the PCAP stream and getting your values from there. If you can combine all of the tests into one tool that will analyze all of the above, you can solve problems within 5 minutes. If you have to do each of these as a separate test, it may take you 30 minutes to collect all of the information and analyze it to detect the problem. * Tracert to remote host (VPN tunnelling, as well as split-tunnelling) * Stability of packet flow to a remote host (Internet target) * Stability of packet flow to a local location (default gateway) * Network throughput (packet loss, latency, jitter, etc.) * Wireless health (signal strength, retries, etc.) Reply to this email directly, view it on GitHub, or unsubscribe.Īs an engineer trying to solve problems, you want to know a number of things: You are receiving this because you authored the thread. WlanScan() does of course cause a Packet loss, you are forcing the NIC to cycle through all channels, how could this not cause a loss?Ĭalling WlanScan() to get your current RSSI is a total overkill, you need to get this info from the current connection object, so you dont need to perform a scan Subject: Re: Measuring WiFi signal strength via the standard API causes packet loss ( #59) How do you get RSSI in dBm on an ongoing basis WITHOUT causing packet loss?Īccording to Microsoft support, all of the other methods do not provide RSSI in dBm, and are also not very accurate. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |