ByteBlower Endpoint FAQ
Introduction | Since the ByteBlower Wireless Endpoint app runs on a lot of hardware and operating system configuration, some questions are asked at regular intervals. The most common questions are listed below. |
The Wi-Fi statistics show weird values. | The ByteBlower Wireless Endpoint tries to collect as much statistics as it can. In modern operating systems (like iOS, Android...), the access to some of these statistics is restricted, other statistics are not available at all. This is usually done to protect the privacy of the end-user. When the ByteBlower Wireless Endpoint is not able to collect a parameter, it will return a default value. The defaults are listed below:
|
No Wi-Fi statistics on Android devices | Android uses a permission system to grant apps access to certain components of the operating system. Wi-Fi parameters are part of the location permission. Granting this permission to the ByteBlower Wireless Endpoint app enables it to collect these. Location must be enabled on Android devices. |
No Wi-Fi statistics on iOS devices | iOS does not provide access to the RSSI, Channel number and Tx Rate, so the Wireless Endpoint will always return -1 as value for these statistics. |
The wrong IP address is announced for the device. | The application collects all available IP addresses on the device it is running on. The first IP address found, is shown in the ByteBlower GUI. See this KB on how to select a traffic IP interface address in the app. Windows 10 provides the last known IP address of an interface even when the interface is down (e.g. the Ethernet cable was disconnected from the interface). |