Using IOCTL to get RSSI information from MT7981

Hi All. Novice here trying to get RSSI information from a Z8102AX from ZBTLink.

Version details;

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.4.213 (quds@quds-PowerEdge-R420) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 unknown)) #0 SMP Tue Sep 12 07:57:31 2023
[    0.000000] Machine model: MediaTek MT7981 RFB

root@061204100004:/# ubus call system board
{
        "kernel": "5.4.213",
        "hostname": "061204100004",
        "system": "ARMv8 Processor rev 4",
        "model": "MediaTek MT7981 RFB",
        "board_name": "mediatek,mt7981-spim-snand-rfb-z8102ax",
        "release": {
                "distribution": "OpenWrt",
                "version": "21.02-SNAPSHOT",
                "revision": "23.0921_091445",
                "target": "mediatek/mt7981",
                "description": "OpenWrt 21.02-SNAPSHOT unknown"
        }
}

The OpenWrt image does not seem to be a stock image and the kernel does not include the nl80211 module. The WiFi extension WEXT does seem to be loaded.

But iwconfig does not provide RSSI signal levels. The level is always given as 0.

My question is. Is it worth trying to use IOCTL to get the RSSI level. Given that this is a MT9871 device and there seem to be no driver information from mediatek.
How can I progress this or am I wasting my time?

Many thanks. MPC

Does invoking the following command give you the information you want?

ubus call iwinfo info '{"device": "DEVICE_NAME"}'

(Replace DEVICE_NAME with the actual name of your radio interface.)


To get a list of valid DEVICE_NAME arguments:

root@OpenWrt:~# ubus call iwinfo devices
{
        "devices": [
                "phy0-ap0",
                "phy1-ap0"
        ]
}

With this I can invoke this to get information for the phy0-ap0 device.

ubus call iwinfo info '{"device": "phy0-ap0"}'

Same reply as in your thread from yesterday.

Ask your SDK provider.

Closing this thread since it is not related to the official OpenWrt project. Please reach out to the maintainer of the SDK.