Hi Cjoseph
GOOD MORNING. :smileyhappy:
I know what disassoc is :) *AND MY DEVICE DOSENT CONNECTING TO ANY OTHER AP or SSID - it just keep trying connecting to this ARUBA AP*
that's not what causing the device not to connect this is just an output of the device re-trying to connect with out a success.
the device keep trying to connect - and the aruba keep see that assoc and then diassoc - becuase the devices (any device) stuck on connecting...... after i manully disconnect it and try to connect agian.
The device just cant connect to the AP....!!! after manuuley disconnect,that what i took out thoese logs.
and the debug showing that is device disassoc..Because ,after i manully disconnect i'am trying agian to connect with no success and the debug output is disassoc...
When did this start happening? Dunno - on daily base devices are connecting - but as long as they dont manually disconnect there is no issue.
If it never worked, was a case ever opened? It worked for years. . .without being noticed i guess.
The debug simply says that the client is disconnecting. Nothing really to report from that.
I know ...... i need u to read agian all what i wrote. . . DEVICE CONNETED WELL. I MANULLY DISCONNET IT. WAITING 2-3 SEC AND TRYING TO CONNET ...THE DEVICE WILL NOW CONNET.
If you are doing split tunnel captive portal, this is a RAP. Are you dropping broadcast and multicast for these VAPs?
yep - and i also tried without that config..same results
What is providing DHCP for these clients in this specific deployment?
Extranl DHCP. (UBUNTU SERVER) on a TRUNK PORT.
Thanks for u support...i need to solve this issue soon.
Hope that Some AirHeads assitance will show me the light in this issue.
Thanks agian.
Me