BYOD: Android problems

[Jaaazman777]

Hello!

We have the following BOYD environment:

• WLC 5508 (7.4.100.0)
• Cisco Identity Services Engine
  • Version      : 1.1.2.145
  • Patch Version      : 3

During BOYD implementation we faced some problems with Androind devices:

1) The Netwrok Setup Assistant (NSA) download process corrupts during the self-provisioning process (captured on 4.1.1 and 4.2.2 version)

2) If NSA is already installed, the network setup process (downloading profile, certificate) stops at last step: connecting to network, meanwhile the connection itself successfully establishes. This bug is captured on 4.2.2 version, 4.1.1 is ok.

Google ACL is configured according to TrustSec docs and permits all traffic to google networks 173.194.0.0/16 and 74.125.0.0/16.

[Amjad Abdullah]

Hello. I suggest you move your thread to Security -> NAC and AAA forums. They will probably help better there.

Rating useful replies is more useful than saying "Thank you"

[Jaaazman777]

Hello!

The problem with downloading Netwrok Setup Assistant (NSA) during the self-provisioning process is solved!

The issue was about Google ACL on WLC:

• For test purpose we added permit ip any any in the end of the Google ACL. After that NSA was successfully downloaded.
• Traffic capturing showed, that during NSA download, Android client established the connection to special network range, which belongs to local provider. In domaintools this net range has description: google
• after adding this range to Google ACL and deleting permit any any rule, NSA was successfully downloaded.

In conclusion: Google play is georgaphicaly depended, we should take it into consideration.

[Amjad Abdullah]

Great news that your issue is resolved.

+5 for solving your own probblem.

Regards,

Amjad

Rating useful replies is more useful than saying "Thank you"

[aman.diwakar]

Thanks Guys,

This is really helpful, do we know what that undocumented range is?? We're running into the same issue.

[aman.diwakar]

We've figured out that problem is actually with Nexus and Android 4.2.2 showing the Agent hanging 4/5 of the way through, older version of android do not and are not affected . We have a case open, once the issue is resolved and a new agent released or workaround, I'll post it up here.