I am sorry to post this since there are other posts about wireless problems since update 199 - I have looked through them all but nothing there seems to help. I have a Pi 3b, it has been running fine for over a year. I only just updated from 198 which was fine, in 199 the wireless is seen by clients but nothing can connect. I moved straight to 200 in case it was a problem that was fixed but no luck. I do not have special characters in WPA key, I’ve tried changing everything to very basic. Any suggestions? I am considering going back to 198 but this is not ideal.
(Yes, wireless is on green as well, bridged. It has always worked well).
Hello,
you have chosen ACS. Does your WiFi module support this?
Try setting the channel manually to check.
Selecting an/gn - Both bands don’t work at the same time, try setting gn or an
My setup worked for almost a year, and only stopped when I updated to 199. So I don’t think it’s a problem with my config. I did have the channel manually set, I have removed the wireless config and tried to set up from scratch, with basic options as shown.
For reference, I took a backup of my hostapd.conf that worked on versions below 199 (I have changed SSID and key - key had only alphanumeric characters):
Automatically generated configuration
DO NOT EDIT
logger_syslog=-1
logger_syslog_level=4
driver=nl80211
country_code=GB
country3=0x49
ieee80211d=1
ieee80211h=1
channel=0
local_pwr_constraint=3
spectrum_mgmt_required=1
enable_background_radar=1
wmm_enabled=1
hw_mode=g
ieee80211n=1
ht_capab=[DSSS_CCK-40] [SHORT-GI-20]
auth_algs=1
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
disassoc_low_ack=1
ssid2=“SomeSSID”
utf8_ssid=1
noscan=0
ieee80211w=0
wpa=2
wpa_passphrase=SomeKey
wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256
rsn_pairwise=CCMP
ssid_protection=1
extended_key_id=1
oce=7
interworking=1
access_network_type=0
internet=1
time_advertisement=2
multicast_to_unicast=1
It looks like the channel is set to auto, I suggest changing it.
I see that 201 is out on testing so tried upgrading to that. The missing pull down menus are there and the AP will start, but clients still cannot connect - so back to where I was with 200.
I’ve tried several older versions of IPFire now, ones that I know worked with the Pi3b - and no luck with the wireless. Is pakfire bringing in the newer version of hostapd even on a previous release? Is there somewhere I can get the older hostapd?
OK, figured out how to manually install hostapd-64d60bb4-68.ipfire and everything works as it used to now.
Back to update 200 with the latest hostapd, and it doesn’t work. In the earlier version I can confirm that setting 802.11g worked, hostapd.conf then had hw_mode=g and ieee80211n=1. There is no suitable wireless mode now for this hardware. Any suggestions?
OK. Pi 3b will work as AP if you set a/g mode with WPA 1/2. Not with WPA 2 or WPA 2/3. In previous releases it worked with WPA 2 and also I could set 40 MHz channels. Bit disappointing because it’s worked well for me for over a year but I guess it’s old niche hardware now.
What does wifi status show?
Have you tried channel 1 or 6?
Yes, channel makes no difference (also automatic). WPA2 will not work, modern Linux (or Mac) client just prompts for key again.
Try setting channel 6 and restarting the Raspberry if you can
Channel 6 - no different. WPA issues.
On my Raspberry Pi 4, I configured 802.11ac @ 20 MHz, 2.4 GHz band, auto channel, WPA2 encryption, and all my devices connect without any problems. But I don’t know if the Raspberry Pi 3B can use these settings.