-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPi4: Wifi cannot connect to ac accesspoint (no VHT Capabilities) #3378
Comments
Which country/regulatory domain are you in? Your wpa_supplicant.conf appears to have no "country=XX" line. |
This is the output of "iw reg get": The wifi accesspoint is configured for Germany, too. |
My 4B has no difficulty connecting to an "ac" AP, and I suspect millions of other 4B and 3B+ users (they both use the same WiFi controller) are in the same position. I can think of four potential explanations for the difference:
Please try connecting to your AP using the WiFi post-installation wizard on a fresh Raspbian download. If your AP is configured to require non-standard settings, please explain exactly which settings in your wpa_supplicant.conf are absolutely necessary. |
According to my googling, VHT is another name for IEEE 802.11ac. Per https://www.electronicdesign.com/technologies/communications/article/21798297/understanding-ieee-80211ac-vht-wireless:
|
So it appears, but that doesn't really move us forward. @HardResetSolution How did you create that Wireshark capture? Does it require a monitor-mode device? |
I had the chance to check interoparbility with 2 further wifi accesspoints. The 3 testet devices show the following behaviour: FRITZ!Box 7590 -> PI sends no VHT Capabilities For this test I used the WiFi post-installation wizard on a fresh Raspbian download. wpa_supplicant.config is the following: ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev network={ For the FRITZ!Box I could create the capture via the accesspoint itself. For Asus and Netgear I used a wifi sniffer (monitor mode). @pelwell Which accesspoint did you use and how did you make sure the Raspberry PI is using "ac" and not "n"? |
We have a Ubiquiti in-house WiFi network, and there's Netgear Nighthawk R7000 on my desk, and the 4B connects to both in the 5G band. Both are "ac" capable APs, but it is possible that these connections are "n" only - it's coming up with a 40MHz channel width. |
I could check a few more accesspoints, but I'm not sure whether that will help us. |
Ubuntu has https://packages.ubuntu.com/eoan/iw which can show the bandwidth of a connection this way (on one of my rpi4B devices connected to a Ubiquiti nano-HD):
(I must be connected through ac since I'm connected via an 80MHz channel.) |
I see the same behaviour with my FRITZ!Box 7590 router. In the attached capture you can see, that in packet 4 (region "DE") the VHT-Capabillities are missing but in packet 15 (region "US") they are included. This looks like a proof for misbehaviour of the PI for me. |
I also had problems that my 4er Pi's had not connected to the AC grid. The problem is probably due to the reception performance of the Pi's. Using DD-WRT router software, I can set the transmission power separately, if I reduce the transmission power in the N 2.4 GHz network by -2 dB then the Pi's choose the AC network instead of the N 2.4 GHz network. So just think that the Pi's choose the stronger network and therefore always choose the stronger N 2.4 GHz network. Perhaps it should be improved in the firmware that the AC network is given priority even if it is minimally weaker than the N network |
I did a check, which country-codes result in an ac connection with FRITZ!Box 7590. connection with ac: connection with only n: |
You can download a trial clm_blob file that may improve the connection options - it's available from https://drive.google.com/file/d/1Qoc90FCTO17d69PbBqUhkJKgqDMmdOui/view?usp=sharing Make a backup of your old clm_blob and install the new one using:
Reboot to use the new clm_blob. N.B. This clm_blob is not suitable for use on a 3B+, so don't try this on a card that might be used on one. |
I just tested the file, and no better. The PI4 only connects in 2.4ghz g (signal -32 db ; tx: 48 mbit/s ; rx: 24 mbit/s) Thie PI4 does not want to connect in 5ghz - 80mhz (802.11a, 802.11n, 802.11ac). Pi4 is installed next to the router (freebox france) should an option be activated?
|
What does |
[updated with country code : fr]
|
And how about |
|
$ iw reg get
|
Thanks. I'm looking at this area at the moment, so I'll try with your configuration as well. |
thanks. I updated the comment for iw phy0 channels. |
I can't see an obvious reason why it wouldn't connect. Does the AP appear in scan results in the 5G band? You could try adding |
I did not understand how to use cmdline.txt |
DFS is Dynamic Frequency Selection (radar detection and avoidance), and AUTO-BW is Auto Bandwidth (choose a sensible channel width - 20, 40, 80). |
Edit cmdline.txt with your favourite editor - |
I cannot deactivate a band, but I can change the ssid. I just tested, and the pi4 still connects on the 2,4Ghz band and does not detect the AP in 5Ghz band. i added the
|
[ 6.970542] brcmfmac: brcmf_cfg80211_reg_notifier: Firmware rejected country setting |
That is to be expected with the 813-byte blob. You should get different results with the original 14036-byte blob. |
Thanks - I understand. |
i relaunch and examine the two frequencies of my AP
the channel with config of 80Mhz (VHT80) is not present !! Only 20MHz an HT40+. |
The old blob doesn't declare any VHT-80 channels, and causes other problems for some regions (KR, for example). The new mini-blob should help with many of those problems, but for some reason it is not working for you. |
can the channel code 'fr' be the cause (with new mini blob) ? should i test with another code? |
As I understand it, the mini-blob should reject all country codes and learn from the environment. You can try a different CC, but it should make no difference. |
inside your |
country=fr or country=FR ore country=US are same reg
BUT with country=US, it's work on 5Ghz mode AC !!!!! With the same ssid for two bands.. the final configuration
|
While I can't help but notice a difference:
|
The 43455 is connected over a 4-bit SDIO link usually running at ~42MHz. That gives a theoretical throughput limit of 168Mbps, but that is half-duplex and assuming no commands and no pauses. Given that, ~100Mbps is about what I would expect. |
lol, so ac or not is not supposed to matter anyway? (other than "compatibility") imo the foundation should state that cap :P |
An individual Pi may not be able to max out the AC bandwidth, but each packet will be sent at full rate which will leave larger gaps for others to transmit in - there is an advantage. |
There's now an updated clm_blob that should give access to the 80MHz channels: https://drive.google.com/file/d/1AN7lC_kMJGGg5AJLhSRtlTRgIh9qJlaI/view?usp=sharing
|
Might be worth announcing this on the forum. |
@tomty89 - I don't know how wise it is to ship these untested. Plus, including these is ultimately up to @kmihelich |
@pelwell Can you give me a hint on how to install the blob? |
I don't understand - the download link (https://drive.google.com/file/d/1AN7lC_kMJGGg5AJLhSRtlTRgIh9qJlaI/view?usp=sharing) is for brcmfmac43455-sdio.clm_blob. |
OK, my fault. FireFox for Android replaced the file extension from clm_blob to bin for some reason. |
Thanks for the hint to the firmware blob! |
At this point it is looking very likely that the updated blob will be in the next image. |
I cheered too soon. The Raspberry PI is now only able to connect to APs that use channels lower than 52 which are only channels 36, 40, 44 and 48. APs on different channels are not seen/found by the Raspberry PI. iw reg get: It does not matter which country I configure in wpa_supplicant.conf. I tried DE, US and UG. |
Try this one instead: https://drive.google.com/file/d/1J8DdbsrZcSkDYKUPsdy2RvncttSwQdBH/view?usp=sharing Note that you will need to rename it from brcmfmac43456-sdio.clm_blob to brcmfmac43455-sdio.clm_blob before (or when) copying it /lib/firmware/brcm. |
Thanks pelwell. I did some testing and set up a comparison between original, 43455 and 34456 blob. original blob:
brcmfmac43455-sdio.clm_blob:
brcmfmac43456-sdio.clm_blob:
|
I have a Pi 4 here running with the renamed 43455 clm_blob, configured to be in WiFi region "DE", and it's happily connected on channel 11. |
Well strange, I put a second Pi 4 in my testsetup and this one can connect with all 2,4 GHz channels. You said that the updated blob will be in the next image. Do you have a clue, when this will be released? Or can you say when the blob will be part of regular updates via apt? |
The next image is due in a matter of weeks, rather than months. The relevant apt package might be updated before then, but probably not. |
With the latest build from https://downloads.raspberrypi.org/raspios_armhf/images/raspios_armhf-2021-03-25/2021-03-04-raspios-buster-armhf.zip the PI can connect using "ac" as expected. |
The Raspberry Pi 4 is not able to connect to wifi accesspoints with wifi standard "ac".
This is because the Raspberry PI 4 is not sending any VHT Capabilities.
My wifi router is running with 5 GHz mixed standard "n+ac" (WI-Fi 5) accesspoint and the Raspberry PI 4 is always connecting with n standard.
To reproduce
Use the following wpa_supplicant config and connect to accesspoint.
wpa_supplicant.config:
ctrl_interface=/run/wpa_supplicant
p2p_disabled=1
network={
ssid="MySSID"
psk="MySecurePsk"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
auth_alg=OPEN
pbss=2
}
Expected behaviour
The Raspberry PI 4 should send VHT Capabilities and connect with wifi standard ac
Actual behaviour
The Raspberry PI 4 does not send VHT Capabilities and connects with wifi standard n
Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
Raspberry Pi 4 4 GB RAM
Which OS and version (
cat /etc/rpi-issue
)?Raspberry Pi reference 2019-06-08
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, d942d5487c035ecd568c1a3049d8b00b14132678, stage5
Which firmware version (
vcgencmd version
)?Sep 24 2019 17:34:30
Copyright (c) 2012 Broadcom
version cd3add54955f8fa065b414d8fc07c525e7ddffc8 (clean) (release) (start)
Which kernel version (
uname -a
)?Linux hostname 4.19.75-v7l+ solved issue of mirroring screen after rotation. #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux
Logs
Find attached a Wireshark capture of the association request with missing VHT Capabilities...
wireshark_capture.zip
dmesg:
dmesg.txt
The text was updated successfully, but these errors were encountered: