EricMN
Posts: 16
Joined: Sun Sep 24, 2017 2:33 am

[solved] hostapd often fails to run at boot on Pi3B+, but not Pi3B.

Wed Apr 18, 2018 5:49 am

I'm following the instructions here to make the pi boot at a wireless AP.

https://www.raspberrypi.org/documentati ... s-point.md

But about 50% of the time, on a Pi 3B+ (the brand new one), hostapd seems to fail at boot and I see no wireless AP. If I take the same microSD card and stick it in a Pi3B, I don't have the same problem. It seems like on a Pi3, the wirless AP comes up most or all of the time.

On the Pi3B+, I see this when I run

cat /var/log/syslog | grep hostapd

Apr 17 16:25:00 raspberrypi hostapd: wlan0: STA 30:ae:a4:1b:e5:ec IEEE 802.11: associated
Apr 17 16:25:00 raspberrypi hostapd: wlan0: STA 30:ae:a4:1b:e5:ec RADIUS: starting accounting session 5AD665F9-00000001
Apr 17 16:25:00 raspberrypi hostapd: wlan0: STA 30:ae:a4:1b:e5:ec WPA: pairwise key handshake completed (RSN)
Apr 17 16:26:58 raspberrypi hostapd[387]: Starting advanced IEEE 802.11 management: hostapd.
Apr 17 16:31:44 raspberrypi hostapd[361]: Starting advanced IEEE 802.11 management: hostapderror: unexpectedly disconnected from boot status daemon
Apr 17 16:31:45 raspberrypi hostapd[361]: .
Apr 17 16:33:26 raspberrypi hostapd: wlan0: STA 08:21:ef:d8:28:5c IEEE 802.11: associated
Apr 17 16:33:26 raspberrypi hostapd: wlan0: STA 08:21:ef:d8:28:5c RADIUS: starting accounting session 5AD667C0-00000000
Apr 17 16:33:26 raspberrypi hostapd: wlan0: STA 08:21:ef:d8:28:5c WPA: pairwise key handshake completed (RSN)
Apr 17 16:33:46 raspberrypi hostapd: wlan0: STA 30:ae:a4:1b:e5:ec IEEE 802.11: associated
Apr 17 16:33:46 raspberrypi hostapd: wlan0: STA 30:ae:a4:1b:e5:ec RADIUS: starting accounting session 5AD667C0-00000001
Apr 17 16:33:46 raspberrypi hostapd: wlan0: STA 30:ae:a4:1b:e5:ec WPA: pairwise key handshake completed

Not sure if there's some kind of race condition going on with competing services? This is on the latest (march) Raspbian Stretch.

EricMN
Posts: 16
Joined: Sun Sep 24, 2017 2:33 am

Re: [solved] hostapd often fails to run at boot on Pi3B+, but not Pi3B.

Tue May 01, 2018 3:21 am

So I solved this by fixing a previous issue with systemd-timesyncd.service competing with the RTC time set mechanism. It seems like once this was solved, hostapd runs fine on the Pi3B+. Only thing I can think of is that on the Pi3, the timesyncd and RTC conflict wasn't happening in a way that caused hostapd to crash, but did so on the Pi3B+ for whatever reason.

elliotp
Posts: 2
Joined: Sun May 27, 2018 7:21 pm

Re: [solved] hostapd often fails to run at boot on Pi3B+, but not Pi3B.

Sun May 27, 2018 7:23 pm

Hi,

Could i trouble you for some further information on how you resolved this? I have the exact same issue.

Thanks,

Elliot

elliotp
Posts: 2
Joined: Sun May 27, 2018 7:21 pm

Re: [solved] hostapd often fails to run at boot on Pi3B+, but not Pi3B.

Sun May 27, 2018 7:48 pm

Scratch that, i believe my specific issue is related to the wpa_supplicant.conf attempting to apply to the wlan interface of my intended AP.

Disabled this with:

nohook wpa_supplicant

Under the interface in /etc/dhcpcd.conf

Thanks!

Return to “Troubleshooting”