03-13-2018 08:32 AM
After upgrade of stations and AP, the stations dont come back...
Problem with EAP:
Mar 7 12:35:54 wireless: ath0 Received auth from 80:2a:a8:3c:70:89. Status: Successful (0). Mar 7 12:35:54 wireless: ath0 Authenticated Station 80:2a:a8:3c:70:89 (Successful) Mar 7 12:35:54 wireless: ath0 Sending auth to 80:2a:a8:3c:70:89. Status: Successful (0). Mar 7 12:35:54 hostapd: ath0: STA 80:2a:a8:3c:70:89 IEEE 802.11: associated Mar 7 12:35:54 wireless: ath0 Received assoc_req from 80:2a:a8:3c:70:89. Mar 7 12:35:54 wireless: ath0 Sending assoc_resp to 80:2a:a8:3c:70:89. Status: Successful (0). Mar 7 12:35:54 wireless: ath0 Registered node:80:2A:A8:3C:70:89 Mar 7 12:35:55 hostapd: ath0: STA 80:2a:a8:3c:70:89 IEEE 802.1X: authentication failed - EAP type: 21 (TTLS) Mar 7 12:35:55 wireless: ath0 Sending disassoc to 80:2a:a8:3c:70:89. Reason: 802.1X authentication failure (23). Mar 7 12:35:55 wireless: ath0 Expired node:80:2A:A8:3C:70:89 Mar 7 12:35:55 hostapd: ath0: STA 80:2a:a8:3c:70:89 IEEE 802.11: disassociated
What is this problem? Where came from this data and time?
AP with firmware 8.5.1 and station with 8.5.0, this problem dont happens
03-15-2018 03:51 AM - edited 03-15-2018 03:51 AM
one more thing which is worth to check is if the system time is within the rage of the date attribute of the certificate used for the EAP-TTLS (valid from .. to). This is due to the fact that system startup date changes after firmware upgrade. We have an option in the system settings for system startup date which can be used as workaround (in case it is required).
05-18-2018 10:15 AM
I also have problems updating to version 8.5.1.
What happens is the following:
In the station I performed the update of the antenna but I do not return again.
then in the AP I made the update and I noticed that when the connection is restored, it asks for User, password, country code again and accept the terms and license agreements, this is a problem because the antenna apparently does not start until filling this information, I think that's what happened to my station, how can this be solved?
in the M5 radios this problem does not happen, it does the upgrade without requesting some information again.
Another thing is that in the previous versions this does not happen either. You can upgrade without problems like this.
05-23-2018 07:59 AM
Yes, all our firmwares are from ubnt.com, at this time I did another test with another antenna and the result is the same. I do not want to update clients for fear of losing connection with them again
06-06-2018 05:50 AM
...this is a problem because the antenna apparently does not start until filling this information...
If you could download /tmp/system.cfg via SSH when your device is showing the above screen after fw update, that would be great! If you can, please share it via a personal message. Thanks!
When you see the above screen after fw update, the radio is still working with your previous configuration. If you select the correct country on the page listed above then everything should work as before. Just make sure all other devices on this wireless link are showing the same country as you select here.
I also concede that v8.5.1 has slightly different countrycode handling in system config and we are going to improve it for the next beta.
06-11-2018 02:27 AM - edited 06-11-2018 02:28 AM
@UBNT-SNK, it's the same issue as I have described in the comment above: