Repository navigation
Profiler don't broadcast SSID on 5 GHz #153
Replies: 7 comments 8 replies
|
Intel AX210 inside the Pro uses Location Aware Regulatory (LAR). It doesn’t respect the reg domain we configure, but it instead sets its reg domain automatically. It first needs to complete a scan, needs to hear a beacon from an existing AP and based on the country code in that beacon, it sets the reg domain. If you manually force the AX210 to scan and then start Profiler, that should unlock the 5 GHz channels and remove the “No IR” flag (the flag tells the adapter not to transmit). This should do the scan: |
|
Hi Jiri,
but this didn't change profiler and iw list output. |
|
I'm still having this same issue. Scanning on 2.4 GHz (Ch 1) seem to work, but I'm seeing nothing on 5 GHz (Ch 36). The entire 5 GHz (And 6 GHz for that matter) seems to be disabled?
|
|
Same problem most likely where the scan is not enabling any channels. From your attached logs: Which common regulatory are you near? The only other thing I can think of is if a newer driver (with an updated bundled regdb) would enable channels for monitor/injection. |
|
It should be using DK regulatory domains, which is ETSI.Sendt fra min iPhoneDen 13. feb. 2025 kl. 01.40 skrev jsz ***@***.***>:
Same problem most likely where the scan is not enabling any channels.
From your attached logs:
2025-02-12 21:56:24,749 [DEBUG] interface: initiating scan on wlan0 because checks found disabled or No IR on 5180
2025-02-12 21:56:24,750 [DEBUG] interface: run: ip link set wlan0 down
2025-02-12 21:56:24,850 [DEBUG] interface: run: iw dev wlan0 set type managed
2025-02-12 21:56:24,861 [DEBUG] interface: run: ip link set wlan0 up
2025-02-12 21:56:25,291 [DEBUG] interface: run: iw wlan0 scan
2025-02-12 21:56:28,443 [DEBUG] interface: finished scan on wlan0
2025-02-12 21:56:28,444 [DEBUG] interface: finish stage_interface
2025-02-12 21:56:28,444 [DEBUG] interface: run: iw phy0 interface add wlan0mon type monitor flags none
2025-02-12 21:56:28,484 [DEBUG] interface: run: ip link set wlan0mon up
2025-02-12 21:56:28,511 [DEBUG] interface: run: ip link set wlan0 down
2025-02-12 21:56:28,579 [DEBUG] interface: run: iw wlan0mon set freq 5180 HT20
2025-02-12 21:56:28,620 [WARNING] interface: No IR found in iw channel information for 36 (5180) which _may_ cause packet injection to fail! Problem with discovery? Try a different channel / frequency. Confirm we're beaconing via OTA capture from a different interface or device.
Which common regulatory are you near?
The only other thing I can think of is if a newer driver (with an updated bundled regdb) would enable channels for monitor/injection.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
I didn't solve this issue, tried with Intel BE200 and Mediatek MT7925 (as per Nick Turner recommendation to try something else than Intel). But You can try to work on channel 165, for some reason it works (sudo profiler -c 165). |
|
My system shows active channels in 5 Ghz however I cannot run Profiler on 5 GHz. No SSID is broadcast. 2.4 GHz works. BE200 - Ubuntu 24.04.2 / 6.11.0-24-generic Kernel.
Frequencies: |
|
What does running with --debug say? Any clues? |
|
Note - This is not a true WLAN-Pi, rather Profiler running on an Ubuntu build. As you see, it says Beacons have started but nothing is really in the air. root@HP-Pavilion-Desktop:/home/phil# profiler -i wlp1s0f0 -c 48 -s "WLANPI" --debug 2025-04-24 10:37:01,294 [DEBUG] start: beacon process |
|
In another pane or terminal, run Check to see if NetworkManager is managing the Wi-Fi interface (sub nmcli device status | grep wlan0
wlan0 wifi unmanaged --If is, try Check if wpa_supplicant has it: ps aux | grep "[w]pa_supplicant.*wlan0"
root 3314959 0.0 0.0 12300 4556 pts/8 S+ Apr17 0:00 sudo vim /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
root 3314962 0.0 0.0 13248 8032 pts/8 S+ Apr17 0:00 vim /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
root 3317398 0.0 0.1 13688 8564 ? Ss Apr17 0:06 /usr/sbin/wpa_supplicant -u -Dnl80211 -i wlan0 -c /etc/wpa_supplic |
|
If I completely kill NetworkManager and wpa-supplicant, I can get further. It acts like it is working. tcpdump does report that it thinks the beacons are working however they are not really in the air. I validated with OTA Sniff (Ekahau sidekick locked on channel). Reading the logs below - I do see this error: If I look at IW LIST Before I run the Profiler, I have good channels. phil@HP-Pavilion-Desktop: If I look at IW LIST WHile Profiler is running, it does show IR Disabled. phil@HP-Pavilion-Desktop: My setup - View status, kill stuff, run profiler and tcpdump:phil@HP-Pavilion-Desktop:~$ ps aux | grep "[w]pa_supplicant." phil@HP-Pavilion-Desktop:~$ nmcli device status (I also tried setting NetworkManager to unmanaged per your suggestion) sudo systemctl stop NetworkManager.service sudo systemctl stop wpa_supplicant phil@HP-Pavilion-Desktop:~$ nmcli device status phil@HP-Pavilion-Desktop:~$ sudo tcpdump -i wlp1s0f0mon | grep WLAN root@HP-Pavilion-Desktop:/home/phil# profiler -i wlp1s0f0 -c 48 -s "WLANPI" --debug 2025-04-25 09:02:24,026 [DEBUG] start: beacon process |
|
Looks like Rx is working (to some extent, but all 00 MAC addresses look suspicious), but Tx is not because of IR flags on the channel. The code is supposed to detect this and then perform a scan before staging the interface in monitor mode. That scan doesn't appear to be happening because of missing logs that would normally be there. Can you try 36 or 161? If the logs say "No IR" detected, profiler will not advertise anything. You can also try running with |
|
Same results on 36 and 161. However running it with -noAP worked for 5 GHz. It was able to hear the associations and parse the capabilities correctly. Pretty cool! Attempt at 6 GHz shows my Client MAC Probe Requests but did not appear to recognize the association. For me, this is all I needed however I am happy to continue to t-shoot the original issue if it benefits you or others. Especially 6 Ghz :-) Update - I tested an open (OWE) SSID on 6 GHz and it did capture and parse the Association. - iPhone 16
802.11k Not reported* - treat with caution, many clients lie about this |
|
Good to hear. I will have to dig into this on a Ubuntu machine and see if I can reproduce or figure out what is going on. I plan on enhancing the profiling soon and adding more details around Wi-Fi 6 and Wi-Fi 7 specifically. |
|
Sounds good, Josh. Happy to help any way I can. Also, I got 6 GHz PSK/SAE to work after several attempts. |
Uh oh!
There was an error while loading. Please reload this page.
I have an issue with Profiler on WLANPi Pro.
On 2,4 GHz it works fine, but on 5 GHz it starts, but don't broadcast Profiler SSID.
Info from CLI:
I noticed that [WARNING] is the difference between 2,4 and 5 Ghz mode and found that "no IR" parameter is similar to scanning on DFS channels - only passive mode, so probably Profiler will not broadcast anything.
iw list confirms that there is no IR parameter in whole 5 GHz!:
any ideas how to fix that? Changing RF Domain between PL, CZ and DE have the same result.
All reactions