 | 1 | initial version |
It could be a Wireshark bug, but it is more likely that the wireless hardware or driver does not actually measure the signal strength or does not put them measured value into the capture. To tell between these two, click at the signal strength row in the dissection pane and look to the raw value in the packet dump (bottom-most pane). If the dissected value is always 0 while the raw values differ, it is a dissector bug; if the raw value is the same in all frames as well, it is a hardware or driver issue.
| | 2 | No.2 Revision |
It could be a Wireshark bug, but it is more likely that the wireless hardware or driver does not actually measure the signal strength or does not put them the measured value into the capture. To tell between these two, click at the signal strength row in the dissection pane and look to the raw value in the packet dump (bottom-most pane). If the dissected value is always 0 while the raw values differ, it is a dissector bug; if the raw value is the same in all frames as well, it is a hardware or driver issue.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
