New ucoode based wifi-scripts break monitor mode

[Hostle]

Does the monitor mode in luci or monitor mode in general have any dependencies ? I have created a patch to enable it for the ipq5018. with my ..conifg the patch indeed enabled monitor mode

phy0-mon0 Link encap:UNSPEC  HWaddr 94-XX-XX-XX-XX-24-00-00-00-00-00-00-00-00-0 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                    
          RX packets:2005 errors:0 dropped:0 overruns:0 frame:0                 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0                  
          collisions:0 txqueuelen:1000                                          
          RX bytes:236713 (231.1 KiB)  TX bytes:0 (0.0 B)                       
                                                                                
phy1-ap0  Link encap:Ethernet  HWaddr 94:XX:XX:XX:XX:25                         
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                    
          RX packets:348 errors:0 dropped:0 overruns:0 frame:0                  
          TX packets:398 errors:0 dropped:0 overruns:0 carrier:0                
          collisions:0 txqueuelen:1000                                          
          RX bytes:115271 (112.5 KiB)  TX bytes:207256 (202.3 KiB)              
                                                                                
phy1-sta0 Link encap:Ethernet  HWaddr 96:XX:XX:XX:XX:25                         
          inet addr:192.168.2.185  Bcast:192.168.2.255  Mask:255.255.255.0      
          inet6 addr: fe80::9483:c4ff:fea4:a725/64 Scope:Link                   
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                    
          RX packets:12312 errors:0 dropped:0 overruns:0 frame:0                
          TX packets:10733 errors:0 dropped:0 overruns:0 carrier:0              
          collisions:0 txqueuelen:1000                                          
          RX bytes:8190736 (7.8 MiB)  TX bytes:5516145 (5.2 MiB)                
                                                                                
wan       Link encap:Ethernet  HWaddr 94:XX:XX:XX:XX:21                         
          UP BROADCAST MULTICAST  MTU:1500  Metric:1                            
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0                    
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0                  
          collisions:0 txqueuelen:1000                                          
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)  

but when i build with def config with just luci added ... monitor mode does not come up / work ??

I will do a diff on the configs, just hoping somebody has the answer before i start playing whack'a'mole with packages.

[Hostle]

Software & Package Dependencies
The essential software components and potential package dependencies are:

    kmod- packages (Kernel Modules): You need the correct kernel drivers for your specific wireless chipset (e.g., kmod-ath9k, kmod-mt76). These must be installed and loaded for the wireless interface to function at all.

    iw: This command-line utility is used in modern OpenWrt releases to configure wireless interfaces, including creating a new interface in monitor mode (e.g., iw phy phy0 interface add mon0 type monitor).

    wireless-tools: A suite of utilities that includes the older iwconfig command. It is often a dependency for other network tools.

    wpad-mini or wpad-basic: These packages provide the necessary daemons (hostapd and wpa_supplicant) for standard AP and client modes. While monitor mode itself is a different operational mode, these utilities manage general wireless functionality.

i am betting on wireless-tools ...

EDIT

nope!!

hostle@hostle-Satellite-L775:~/b3000-final/openwrt$ cat .config | grep wireless-tools
# CONFIG_PACKAGE_wireless-tools is not set

precisely why i am not a betting man ... whack'a'mole its just 3.8mb of packages to unset .. test ..repeat .

[brada4]

Well - monitor mode enabled contrary to chatbot assessment.

Example usage

[OpenWrt Wiki] Debugging

[Hostle]

this issue is not usage, my libesp-now library is communicating will all the esp32's perfectly. But to submit a patch it helps to provide all the required dependencies for the patch to work. I half handily added on the fly in my dev branch not thinking of possible dependencies. Now i am trying to apply the patch to a default config build and its not working ... not a peep. If i switch and load the working config, it works perfectly. So there is a mysterious dependency from one config to the other. problem is, the working config weighs 18.9mb and the def config only weighs 14.3mb ... that's alot. I have ruled out anything that would seem related but still no joy. i am up to 14.8mb ... few weeks i should have it

router

13:16:33.648 -> 
13:16:38.633 -> Packet received from: 78:xx:xx:xx:xx:68
13:16:38.633 -> Length incoming: 24
13:16:38.633 -> Length readings: 24
13:16:38.633 -> Board ID 1: 24 bytes
13:16:38.633 -> stype 2 
13:16:38.633 -> c value: 405.98
13:16:38.633 -> t value: 22.40 
13:16:38.633 -> h value: 29.90 
13:16:38.672 -> readingID value: 6 
13:16:38.672 -> 
13:16:43.612 -> Packet received from: 78:xx:xx:xx:xx:68
13:16:43.645 -> Length incoming: 24
13:16:43.645 -> Length readings: 24
13:16:43.645 -> Board ID 1: 24 bytes
13:16:43.645 -> stype 2 
13:16:43.645 -> c value: 406.78 
13:16:43.645 -> t value: 22.90 
13:16:43.645 -> h value: 28.00 
13:16:43.645 -> readingID value: 7 
13:16:43.645 -> 

esp32

13:15:32.689 --> 
13:15:45.689 -> Last Packet Send Status:	Delivery Success
13:15:50.671 -> 405.98
13:15:50.671 -> 22.40
13:15:50.671 -> 29.90
13:15:50.671 -> Sent with success
13:15:50.671 -> 
13:15:50.671 -> Last Packet Send Status:	Delivery Success
13:15:55.654 -> 406.78 
13:15:55.654 -> 22.90
13:16:55.654 -> 28.00
13:16:55.524 -> Sent with success
13:16:55.700 -> 

[brada4]

Modern tools can snoop wifi air using netlink messages. Old packages use patched pcap. one side needs nf-nl libraries, other pcap ones.

[Hostle]

drum-roll ...

 -*- wifi-scripts................................. Wi-Fi configuration scripts     │ │  
  ││           [*] Use new ucode based scripts  <-- this breaks monitor mode !!

the new ucode based scripts don't seem to account for monitor mode. Unsetting "Use new ucode based scripts" (which is now set by default) monitor mode restored