<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: BYOD - Android Onboarding Issues in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561041#M536089</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jason, i got single ssid on boarding. Can you explain more your point? I did not understand what you try to explain...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Feb 2017 04:17:27 GMT</pubDate>
    <dc:creator>rchockeelopez</dc:creator>
    <dc:date>2017-02-20T04:17:27Z</dc:date>
    <item>
      <title>BYOD - Android Onboarding Issues</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561036#M536084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We got issues with some Android phones that is disconnecting the Wifi connection during the BYOD process when you try to navigate to Google Play.&lt;/P&gt;&lt;P&gt;&lt;IMG alt="BYOD Android Error.png" class="image-1 jive-image" src="/legacyfs/online/fusion/104723_BYOD Android Error.png" style="height: 407px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;Hope you can help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 23:04:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561036#M536084</guid>
      <dc:creator>rchockeelopez</dc:creator>
      <dc:date>2017-02-17T23:04:51Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD - Android Onboarding Issues</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561037#M536085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you provide device information and Android OS version? Also the version and patch of ISE as well. Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 23:17:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561037#M536085</guid>
      <dc:creator>howon</dc:creator>
      <dc:date>2017-02-17T23:17:23Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD - Android Onboarding Issues</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561038#M536086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my experience, WLC will drop the client session, if the ACL is not allowing to go to Google play store or to download the app via Google content delivery network . I would suggest either (1) pre-download and pre-install Cisco NSA app using another WLAN or connection or (2) update the ACL.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Feb 2017 01:21:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561038#M536086</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-02-19T01:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD - Android Onboarding Issues</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561039#M536087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;t&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;ake a look at this post for full ACEs and DNS ACL requirements.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/thread/62901"&gt;https://communities.cisco.com/thread/62901&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;flexconnect mode does not support URL ACLs&lt;/P&gt;&lt;P&gt;wlc version 8.2+ will allow up to&amp;nbsp; 20 DNS ACLs , eariler versions are limited to 10.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Feb 2017 08:42:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561039#M536087</guid>
      <dc:creator>ldanny</dc:creator>
      <dc:date>2017-02-19T08:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD - Android Onboarding Issues</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561040#M536088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Keep in mind if doing peap to eap-tls single ssid on boarding you can always allow internet but require on boarding once they try to access internal access &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then no acl issues &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Feb 2017 09:21:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561040#M536088</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-02-19T09:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD - Android Onboarding Issues</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561041#M536089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jason, i got single ssid on boarding. Can you explain more your point? I did not understand what you try to explain...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Feb 2017 04:17:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561041#M536089</guid>
      <dc:creator>rchockeelopez</dc:creator>
      <dc:date>2017-02-20T04:17:27Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD - Android Onboarding Issues</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561042#M536090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;instead of redirecting everything to ISE instead only redirect internal websites. Allow all the internet sites&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They connect with PEAP and are able to access internet (allows them access to app store as well)&lt;/P&gt;&lt;P&gt;When they want to get access to internal resources they are redirected by the REDIRECT ACL to ISE and are required to onboard.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This way don't have to deal with DNS based ACLs, cloud based services, etc since the whole internet is allowed and they can easily use the app store&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Feb 2017 08:41:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561042#M536090</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-02-20T08:41:22Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD - Android Onboarding Issues</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561043#M536091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have issues with Android 5.1 and 6.0. ISE has 2.1 and patch 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Feb 2017 21:59:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-android-onboarding-issues/m-p/3561043#M536091</guid>
      <dc:creator>rchockeelopez</dc:creator>
      <dc:date>2017-02-20T21:59:56Z</dc:date>
    </item>
  </channel>
</rss>

