Wireless Access

Reply
Occasional Contributor II
Posts: 28
Registered: ‎05-10-2016

Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

[ Edited ]

I am currently in the process of setting up a 7010, with an existing configuration. Most devices connecting to the AP-205 work perfectly fine, except android phones, when attempting to connect through 802.1x.

The Android phones connect perfectly fine when connecting through the public Virtual AP (which has no authentication), and every other device works fine on both the 802.1x (iphones and laptops) and the public VAP.

The error message that appears is "ap currently not in use. internet connection slow"

 

Anyone encounter this issue before?

 

EDIT: I was able to find a different Android device to test with this, a Nexus that is running android 6.0.1. The other 2 android devices that did not work are both Samsung Galaxy S5's running 5.1.1

Guru Elite
Posts: 20,993
Registered: ‎03-29-2007

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

http://thedroidguy.com/2016/02/galaxy-s4-ap-currently-not-in-use-internet-connection-slow-error-other-issues-1055115#Problem3



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 28
Registered: ‎05-10-2016

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

The android was able to connect to the virtual AP in question when I set a static IP. However, it had no internet access, and did not show up in the clients list on the mobility controller.

 

Also for testing purposes, I upgraded one of the android devices from 5.1.1 to 6.0.1, however this did not resolve the issue.

Aruba Employee
Posts: 57
Registered: ‎07-24-2014

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

Hi,

Is enforce dhcp enabled in AAA profile?

Thanks!
Occasional Contributor II
Posts: 28
Registered: ‎05-10-2016

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

No, it is not.

Guru Elite
Posts: 20,993
Registered: ‎03-29-2007

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

Well,

 

There are plenty of Android Devices that connect using 802.1x on an Aruba Network from 4.x to 5.x to 6.x, so it works in many setups.  The question is, what is wrong with your setup?  You might have to open a TAC case or let us look at your logs to understand what is going wrong.  Otherwise, we will just end up guessing what your problem is, which could take alot of time.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 28
Registered: ‎05-10-2016

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

What is the best way to go about grabbing a log file for this?

Guru Elite
Posts: 20,993
Registered: ‎03-29-2007

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

- Find out the mac address of the device.

- on the commandline of the controller, type:

config t

logging level debugging user-debug <mac address of device>

- Try to connect the device

- On the controller commandline type "show log user-debug all" and take a look at that log



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 28
Registered: ‎05-10-2016

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

Here is a pastebin of the log: http://pastebin.com/tFUYHByr

Guru Elite
Posts: 20,993
Registered: ‎03-29-2007

Re: Android not connecting to AP-205, controller is 7010, other devices work (802.1x EAP only)

<NOTI> |AP SLS-HQ1@192.168.0.134 stm|  Disassoc from sta: fc:c2:de:16:ba:4a: AP 192.168.0.134-f0:5c:19:f7:05:81-SLS-HQ1 Reason STA has left and is disassociated

 

The controller is getting the disassociation from the client.  If it is just 802.1x on android, you need to only specify the user identity and password.  Do not specify a CA certificate or any other settings.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: