Mike

This is a standard default kernel config: https://github.com/raspberrypi/linux/blob/rpi-5.15.y/arch/arm64/configs/bcm2711_defconfig#L450 This does not automatically mean that it will be used to compile your kernel. If this entries CONFIG_CFG80211_WEXT=y CONFIG_CFG80211_WEXT_EXPORT=y are not present...

The suggested way to detect the presence of WIRELESS EXTENSIONS is to use an ioctl() system call: ``` #define SIOCGIWNAME 0x8B01 /* get name == wireless protocol */ /* SIOCGIWNAME...

BTW: If someone is interested how to detect the presence of NL80211, this is the suggested way: Instead of running an ioctl() system call, we use CTRL_CMD_GETFAMILY (via GENERIC NETLINK)...

Please notice that this driver is a very, "special" driver. It doesn't support all WIRELESS EXTENSIONS. That means, controlling the interface via ioctl() may or may not work. To get...

I have several Raspberry PI systems (all armv6). Unfortunately I have to say, that they are "very special", too. ``` $ uname -r 5.15.32+ ``` ``` $ cat /etc/debian_version bookworm/sid...

Great investigation. Thanks. I took a closer look at the driver code and noticed that there are several names: IEEE 802.11bn, EEE 802.11b, IEEE 802.11AC, IEEE 802.11an, IEEE 802.11a, IEEE...

Starting with this commit: https://github.com/ZerBea/hcxdumptool/commit/311e09325d70a0774d25f687b285c3af26ca7519 hcxdumptool is refactored and the entire code is replaced by hcxlabtool code. WIRELESS EXTENSIONS are completely retired and replaced by NL80211 stack (which is used...

For reference: Also taints nl80211 `Comm: wireshark Tainted: P W O 6.0.0-kali6-amd64` https://github.com/ZerBea/hcxdumptool/issues/246#issue-1533775961

No, not regarding hcxdumptool/hcxlabtool.

We have to wait until the driver will get a fix. I also only noticed some problems with this driver.