No data at all can currently be read from the control socket.
Set up the permission exactly like hostapd's wpa_cli utility to fix it.
Among other this fixes a mesh's encryption being shown as "None".
Signed-off-by: Andre Heider
---
iwinfo_nl80211.c | 16
1 file changed, 16
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Branch: refs/heads/master
USB devices can now be added to devices.txt as:
0x | 0x | vendor id | product id | ...
Signed-off-by: Andre Heider
---
devices.txt | 2 ++
iwinfo_nl80211.c | 4 +++-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/devices.txt b/devices.txt
index b01e4ac..8796276
Determine if parent device of the phy belongs to the "usb" subsystem
and skip those expensive lookups accordingly. Those don't even make any
sense for usb devices.
With a 5.15 kernel the mtd lookup even spams dmesg with:
"mtdblock: MTD device 'factory' is NAND, please consider using UBI block
In this case the specified backend couldn't be found.
Signed-off-by: Andre Heider
---
iwinfo_cli.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/iwinfo_cli.c b/iwinfo_cli.c
index dca86cf..d8851d7 100644
--- a/iwinfo_cli.c
+++ b/iwinfo_cli.c
@@ -972,7 +972,7 @@ int main(int
Add USB PID/VID as found on e.g. Comfast CF-953AX.
Signed-off-by: Andre Heider
---
devices.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/devices.txt b/devices.txt
index 8796276..7674f85 100644
--- a/devices.txt
+++ b/devices.txt
@@ -202,3 +202,4 @@
0x1ae9 0x0310 0x1ae9 0x0
Hi,
I have another idea that might simplify the mess of dealing with
PKG_RELEASE handling.
1. we use AUTORELEASE for all packages in master
2. when creating a release branch, all PKG_RELEASE lines are changed to
something like 22.03-1
3. we write a script that can automatically edit a series
