Member
caspat
Posts: 298
Registered: ‎01-12-2010
Posts: 298
Kudos: 3
Registered: 01-12-2010

Re: Authentication not valid

i update it to 5.3.5. same probleme...
Pat
New Member
jqzuniga
Posts: 12
Registered: ‎09-29-2010
Posts: 12
Registered: 09-29-2010

Re: Authentication not valid

I have the same problem with two Rocket M5, they went down yesterday for three hours, suddenly they went up, and in the log the same error several times. any help will be appreciated.


Jan 17 7:48:45 hostapd: ath0: STA 00:27:22:16:ed:8d IEEE 802.11: associated
Jan 17 7:48:48 hostapd: ath0: STA 00:27:22:16:ed:8d WPA: PTK: Failed to receive EAPOL-Key msg 2/4 response, all tries exhausted.
Jan 17 7:48:48 hostapd: ath0: STA 00:27:22:16:ed:8d IEEE 802.11: deauthenticated due to local deauth request
Jan 17 7:48:48 hostapd: ath0: STA 00:27:22:16:ed:8d IEEE 802.11: disassociated
Jan 17 7:48:48 wireless: ath0 Sending deauth to 00:27:22:16:ed:8d. Reason: Unspecified (15).
Jan 17 7:48:48 wireless: ath0 Expired node:00:27:22:16:ED:8D
New Member
jqzuniga
Posts: 12
Registered: ‎09-29-2010
Posts: 12
Registered: 09-29-2010

Re: Authentication not valid

Hello; any updates on this matter. Regards.
New Member
ff-rauter
Posts: 28
Registered: ‎05-16-2011
Posts: 28
Kudos: 5
Registered: 05-16-2011

Failed to receive EAPOL-Key

I have the same issue in a very noisy enviroment. CPE (NanoBridgeM5) disconnect from Sector (RocketM5) for undefined reason.

Logfile on BS says the same.
Feb 1 08:31:47 hostapd: ath0: STA 00:27:22:34:1b:4c WPA: group key handshake completed (RSN)
Feb 1 09:31:47 hostapd: ath0: STA 00:27:22:34:1b:4c WPA: group key handshake completed (RSN)
Feb 1 10:19:18 hostapd: ath0: STA 00:27:22:34:1b:4c IEEE 802.1X: authenticated - EAP type: 25 (PEAP)
Feb 1 10:19:21 hostapd: ath0: STA 00:27:22:34:1b:4c WPA: PTK: Failed to receive EAPOL-Key msg 4/4 response, all tries exhausted.
Feb 1 10:19:21 hostapd: ath0: STA 00:27:22:34:1b:4c IEEE 802.11: deauthenticated due to local deauth request
Feb 1 10:19:21 hostapd: ath0: STA 00:27:22:34:1b:4c RADIUS: stopped accounting session 4D716EFE-00000002
Feb 1 10:19:21 hostapd: ath0: STA 00:27:22:34:1b:4c IEEE 802.11: disassociated
Feb 1 10:19:21 wireless: ath0 Sending deauth to 00:27:22:34:1b:4c. Reason: Unspecified (15).
Feb 1 10:19:21 wireless: ath0 Expired node:00:27:22:34:1B:4C

In my situation the CPE connects so another Sector from us, with link quality is much worse. I use same SSID on all BS.

Are there any fixes? Does a replace of the CPE really fix the problem?

Best Regards
Regular Member
lboyd
Posts: 379
Registered: ‎01-16-2011
Posts: 379
Kudos: 41
Registered: 01-16-2011

Re: Authentication not valid

I have two Rocket M2 in the same location. One runs our private network using AirMax and the other is our HotSpot.

3 times today I've had to reboot the radio that's in AirMax mode becouse the clients are disconnecting and not coming back online.

Authenticatio not valid (2)

I have 8 clients on this radio.

Leo
Newbie
SloMusti
Posts: 6
Registered: ‎11-28-2010
Posts: 6
Registered: 11-28-2010

Re: Authentication not valid

I am having the same issue with Rocket M2 on 5.3.5 with non-ubnt clients in b-only mode. They are deauthenticated about 5-10minutes after connecting. They do connect again, however there is no communication with them anymore and the tx/rx rates are stuck at 0/0.
Dec 19 20:47:01 wireless: ath0 Registered node:xx:xx:xx:xx:xx:xx
Dec 19 20:48:47 wireless: ath0 Sending deauth to xx:xx:xx:xx:xx:xx. Reason: Unspecified (1).
Dec 19 20:48:47 wireless: ath0 Expired node:xx:xx:xx:xx:xx:xx
Dec 19 20:48:48 wireless: ath0 Registered node:xx:xx:xx:xx:xx:xx
Dec 19 20:48:49 wireless: ath0 Sending deauth to xx:xx:xx:xx:xx:xx. Reason: Unspecified (1).
Dec 19 20:48:49 wireless: ath0 Expired node:xx:xx:xx:xx:xx:xx
Dec 19 20:48:53 wireless: ath0 Registered node:xx:xx:xx:xx:xx:xx
Established Member
TechnoKiwi
Posts: 1,602
Registered: ‎09-01-2010
Posts: 1602
Kudos: 114
Solutions: 4
Registered: 09-01-2010

Re: Authentication not valid

Last time I saw issues that were appearing from users like this was on the Unifi forum when an updated firmware had QOS changes that did not work on some bigger networks...It went on for over 2 months before fixed.

Nothing like this obviously..., QOS etc
What im saying is,,, Is it possible to go back to the firmware before the one you run now? a stable firmware?

maybe well off... good luck finding the solution. :icon_idea:
INTERNATIONAL Wi-Fi Hotspot Provider www.maiwifi.com
Using only the best firmware ~ airOS with our hotspot tab
DOWNLOAD FREE Firmware & install on any airMAX radio
Newbie
SloMusti
Posts: 6
Registered: ‎11-28-2010
Posts: 6
Registered: 11-28-2010

Re: Authentication not valid

I have tried 4 older firmwares, down to 5.2.5, no luck whatsoever.
Veteran Member
Josh_SPITwSPOTS
Posts: 16,788
Registered: ‎11-20-2011
Posts: 16788
Kudos: 4802
Solutions: 111
Registered: 11-20-2011

Re: Authentication not valid

I've seen this problem before myself on some 4.0.1 equipment.

Changing both devices to no encryption, saving, rebooting, and then turning encryption back on, saving, and rebooting fixed the problem in every case I've seen.
Josh Reynolds :: Chief Information Officer :: www.spitwspots.com
Ubiquiti Carrier Wireless Admin, Trainer
Member
kabelfrei
Posts: 119
Registered: ‎07-14-2008
Posts: 119
Kudos: 5
Registered: 07-14-2008

Re: Authentication not valid

Hello,
We have the "authentication Not valid" issue also on one Ap. It apears after we connect the 11 cpe, also only this cpe has this issue (or the last connected cpe, i will test) Last thing we can do is change the cpe, but i am Not sure if this helps?
Firmware on ap (rm5) and cpe (5m loco) is 5.5.2.
##edit: We disconnected one unused loco too see if it works with 10 locos, but no change.

3 18:39:02 wireless: ath0 Sending deauth to 00:27:22:c4:7f:55. Reason: Authentication is not valid (2).
Sep 3 18:39:02 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:c4:7f:55 rx_packets=300 rx_bytes=46443 tx_packets=338 tx_bytes=28724
Sep 3 18:39:02 wireless: ath0 Expired node:00:27:22:C4:7F:55
###REBOOT Power Off/On####
Sep 3 19:00:16 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:c4:7f:55)
Sep 3 19:00:16 wireless: ath0 Registered node:00:27:22:C4:7F:55
Sep 3 19:00:16 hostapd: ath0: STA 00:27:22:c4:7f:55 IEEE 802.11: associated
###NEXT DISCONNET###
Sep 3 19:26:17 hostapd: ath0: STA 00:27:22:c4:7f:55 IEEE 802.11: disassociated
Sep 3 19:26:17 wireless: ath0 Sending deauth to 00:27:22:c4:7f:55. Reason: Authentication is not valid (2).
Sep 3 19:26:17 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:c4:7f:55 rx_packets=3282 rx_bytes=554122 tx_packets=3320 tx_bytes=1850687
Sep 3 19:26:17 wireless: ath0 Expired node:00:27:22:C4:7F:55
###REBOOT POWER OFF/ON###
Sep 3 20:56:15 hostapd: ath0: STA 00:27:22:c4:7f:55 IEEE 802.11: associated
Sep 3 20:56:15 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:c4:7f:55)
Sep 3 20:56:15 wireless: ath0 Registered node:00:27:22:C4:7F:55
Sep 3 20:56:15 hostapd: ath0: STA 00:27:22:c4:7f:55 WPA: pairwise key handshake completed (RSN)
###NEXT DISCONNECT###
Sep 3 21:21:17 wireless: ath0 Sending deauth to 00:27:22:c4:7f:55. Reason: Authentication is not valid (2).
Sep 3 21:21:17 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:c4:7f:55 rx_packets=1144 rx_bytes=185698 tx_packets=1363 tx_bytes=303065
Sep 3 21:21:17 wireless: ath0 Expired node:00:27:22:C4:7F:55

Thanks
Member
kabelfrei
Posts: 119
Registered: ‎07-14-2008
Posts: 119
Kudos: 5
Registered: 07-14-2008

Re: Authentication not valid

Bumpbumpbump
Ubiquiti Employee
UBNT-Edmundas
Posts: 3,620
Registered: ‎05-13-2009
Posts: 3620
Kudos: 452
Solutions: 32
Registered: 05-13-2009

Re: Authentication not valid

Hello,

We have the "authentication Not valid" issue also on one Ap. It apears after we connect the 11 cpe, also only this cpe has this issue (or the last connected cpe, i will test) Last thing we can do is change the cpe, but i am Not sure if this helps?

Firmware on ap (rm5) and cpe (5m loco) is 5.5.2.

##edit: We disconnected one unused loco too see if it works with 10 locos, but no change.


3 18:39:02 wireless: ath0 Sending deauth to 00:27:22:c4:7f:55. Reason: Authentication is not valid (2).
Sep 3 18:39:02 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:c4:7f:55 rx_packets=300 rx_bytes=46443 tx_packets=338 tx_bytes=28724
Sep 3 18:39:02 wireless: ath0 Expired node:00:27:22:C4:7F:55

###REBOOT Power Off/On####
Sep 3 19:00:16 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:c4:7f:55)
Sep 3 19:00:16 wireless: ath0 Registered node:00:27:22:C4:7F:55
Sep 3 19:00:16 hostapd: ath0: STA 00:27:22:c4:7f:55 IEEE 802.11: associated

###NEXT DISCONNET###
Sep 3 19:26:17 hostapd: ath0: STA 00:27:22:c4:7f:55 IEEE 802.11: disassociated
Sep 3 19:26:17 wireless: ath0 Sending deauth to 00:27:22:c4:7f:55. Reason: Authentication is not valid (2).
Sep 3 19:26:17 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:c4:7f:55 rx_packets=3282 rx_bytes=554122 tx_packets=3320 tx_bytes=1850687
Sep 3 19:26:17 wireless: ath0 Expired node:00:27:22:C4:7F:55

###REBOOT POWER OFF/ON###

Sep 3 20:56:15 hostapd: ath0: STA 00:27:22:c4:7f:55 IEEE 802.11: associated
Sep 3 20:56:15 wireless: ath0 MLME-AUTH.indication(addr=00:27:22:c4:7f:55)
Sep 3 20:56:15 wireless: ath0 Registered node:00:27:22:C4:7F:55
Sep 3 20:56:15 hostapd: ath0: STA 00:27:22:c4:7f:55 WPA: pairwise key handshake completed (RSN)

###NEXT DISCONNECT###
Sep 3 21:21:17 wireless: ath0 Sending deauth to 00:27:22:c4:7f:55. Reason: Authentication is not valid (2).
Sep 3 21:21:17 wireless: ath0 STA-TRAFFIC-STAT mac=00:27:22:c4:7f:55 rx_packets=1144 rx_bytes=185698 tx_packets=1363 tx_bytes=303065
Sep 3 21:21:17 wireless: ath0 Expired node:00:27:22:C4:7F:55



Thanks


White Signal/Noise levels are for this Station from AP and from Station sides?

-Edmundas
New Member
c3po
Posts: 12
Registered: ‎03-21-2012
Posts: 12
Registered: 03-21-2012

Re: Authentication not valid

Seen this same behavior on test link between two NanoBridge's (5ghz) after returning this weekend. Link was working perfect last week, came back this morning and the units weren't agreeing on the 4 way handshake. Disabled WPA2-AES to no encryption and enabled MAC ACL. Link still wouldn't come up. Disabled MAC authentication and the link came back up. Both units are on 5.5.2. Tried rebooting both ends to no avail. Haven't tried enabling WPA2-AES on them again in fear of them not associating again. Have to climb a ladder and get back to the Station WDS side to switch encryption off to make the link come back up. Haven't tried going down firmware versions to 5.5 or 5.3.5 yet. Issue looks old so i doubt its due to the new version?? There isn't much noise between the link either.
New Member
c3po
Posts: 12
Registered: ‎03-21-2012
Posts: 12
Registered: 03-21-2012

Re: Authentication not valid

White Signal/Noise levels are for this Station from AP and from Station sides?

-Edmundas



For the Access Point WDS side: Signal is -38, noise is -93.

On the Station WDS side: Signal is -37, noise is -93.


Snippet from syslog.

Sep 4 07:22:24 --- wireless: ath0 MLME-AUTH.indication(addr=dc:9f:db:10:f9:53)
Sep 4 07:22:24 --- wireless: ath0 Registered node:manvery-happy:C:9F:manvery-happy:B:10:F9:53
Sep 4 07:22:24 --- hostapd: ath0: STA dc:9f:db:10:f9:53 IEEE 802.11: associated
Sep 4 07:22:27 --- hostapd: ath0: STA dc:9f:db:10:f9:53 WPA: PTK: Failed to receive EAPOL-Key msg 2/4 response, all tries exhausted.
Sep 4 07:22:27 --- wireless: ath0 Sending deauth to dc:9f:db:10:f9:53. Reason: 4-way keying handshake timeout (15).
Sep 4 07:22:27 --- hostapd: ath0: STA dc:9f:db:10:f9:53 IEEE 802.11: deauthenticated due to local deauth request
Sep 4 07:22:27 --- wireless: ath0 STA-TRAFFIC-STAT mac=dc:9f:db:10:f9:53 rx_packets=0 rx_bytes=0 tx_packets=4 tx_bytes=428
Sep 4 07:22:27 --- wireless: ath0 Expired node:manvery-happy:C:9F:manvery-happy:B:10:F9:53
Sep 4 07:22:27 --- hostapd: ath0: STA dc:9f:db:10:f9:53 IEEE 802.11: disassociated
Sep 4 07:23:01 --- wireless: ath0 MLME-AUTH.indication(addr=dc:9f:db:10:f9:53)
Established Member
TechnoKiwi
Posts: 1,602
Registered: ‎09-01-2010
Posts: 1602
Kudos: 114
Solutions: 4
Registered: 09-01-2010

Re: Authentication not valid

Haven't tried going down firmware versions to 5.5 or 5.3.5 yet. Issue looks old so i doubt its due to the new version?? There isn't much noise between the link either.


This is an older thread so you are lucky you still can downgrade to v5.3.5
On all new AP's this is now not possible... :icon_confused:
INTERNATIONAL Wi-Fi Hotspot Provider www.maiwifi.com
Using only the best firmware ~ airOS with our hotspot tab
DOWNLOAD FREE Firmware & install on any airMAX radio
Member
kabelfrei
Posts: 119
Registered: ‎07-14-2008
Posts: 119
Kudos: 5
Registered: 07-14-2008

Re: Authentication not valid

White Signal/Noise levels are for this Station from AP and from Station sides?

-Edmundas


WDS-AP: -74/-90

WDS-STA: -76/-90

I know that these values are not really good but i don't see a connection to the "Authentication not valid" log entry. If it logs something like "Authentication timeout"....

Also that the CPE must be Power cycled to get functional again.

The other CPEs had much better Signals (> -60).


thanks
Member
kabelfrei
Posts: 119
Registered: ‎07-14-2008
Posts: 119
Kudos: 5
Registered: 07-14-2008

Re: Authentication not valid

Any news ?
Ubiquiti Employee
UBNT-Edmundas
Posts: 3,620
Registered: ‎05-13-2009
Posts: 3620
Kudos: 452
Solutions: 32
Registered: 05-13-2009

Re: Authentication not valid

WDS-AP: -74/-90

WDS-STA: -76/-90

I know that these values are not really good but i don't see a connection to the "Authentication not valid" log entry. If it logs something like "Authentication timeout"....

Also that the CPE must be Power cycled to get functional again.

The other CPEs had much better Signals (> -60).


thanks


"Authentication becomes not valid" when AP/STA fails to exchange WPA keys, then AP drops that Station and it has to reauthenticate. It may happen due to poor connection between AP/STA. Does it happen on previous airOS versions (v5.5, v5.3.5)?

-Edmundas
Member
kabelfrei
Posts: 119
Registered: ‎07-14-2008
Posts: 119
Kudos: 5
Registered: 07-14-2008

Re: Authentication not valid


"Authentication becomes not valid" when AP/STA fails to exchange WPA key

It should not...I totally agree with you.


then AP drops that Station and it has to reauthenticate.It may happen due to poor connection between AP/STA.

It only reauthenticate after power cycle.



Does it happen on previous airOS versions (v5.5, v5.3.5)?


v5.5 --> Yes
v5.3.5 --> I don't know

thanks
Ubiquiti Employee
UBNT-Edmundas
Posts: 3,620
Registered: ‎05-13-2009
Posts: 3620
Kudos: 452
Solutions: 32
Registered: 05-13-2009

Re: Authentication not valid


It only reauthenticate after power cycle.


Just to confirm if I have missed that. You have to reboot Station, as it never tries to connect back to AP (even after couple hours)?

-Edmundas