0

I've got a Pi0W. I've also got a WPA2 Enterprise Wi-Fi network set up with TTLS. My other Pis (both Pi3B+) can connect with my current setup just fine.

The logs of my Pi0W are akind to the following:

Trying to associate with SSID 'MyWifiSsidName'
Associated with aa:bb:cc:dd:ee:ff
CTRL-EVENT-EAP-STARTED EAP authentication started
...
eap auth logs
...
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
CTRL-EVENT-CONNECTED - Connection to aa:bb:cc:dd:ee:ff completed [id=0 id_str=]
CTRL-EVENT-DISCONNECTED bssid=aa:bb:cc:dd:ee:ff reason=2 locally_generated=1
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB

And then it tries again with the same pattern. I see that the even-disconnected reason is 2, which apparently means "previous authentication no longer valid," but that has me scratching my head since it literally just authenticated, and that other Pis are having no issue with this setup.

It could potentially be due to the country codes? But I'm not sure why. All of my Wi-Fi related devices are set to GB (I've had issues using US with TTLS).

Any ideas?

  • what are you running on the zero? – abolotnov Sep 20 at 4:43
  • The RPiZ model and others do not have real time clock (RTC) ... maybe a problem with your certificate and the current raspberry time? Check your system time. – Ephemeral Sep 20 at 9:21
  • @abolotnov As in what OS? Rasbian Lite (no UI). Software and services? Nothing additional, yet. – Tim Morris Sep 20 at 15:38
  • @Ephemeral why would the TTLS process succeed if that were the case? Wouldn't it fail before it finishes connection? – Tim Morris Sep 20 at 15:39
  • @Ephemeral I just updated the system clock to be recent and the same issue persists. – Tim Morris Sep 21 at 2:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.