<?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 problems in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186426#M178966</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Mar 2013 20:56:50 GMT</pubDate>
    <dc:creator>aman.diwakar</dc:creator>
    <dc:date>2013-03-21T20:56:50Z</dc:date>
    <item>
      <title>BYOD: Android problems</title>
      <link>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186421#M178961</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have the following BOYD environment:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;WLC 5508 (7.4.100.0)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Cisco Identity Services Engine&lt;/SPAN&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Version&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 1.1.2.145&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Patch &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;Version&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 3&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During BOYD implementation we faced some problems with Androind devices:&lt;/P&gt;&lt;P&gt;1) The Netwrok Setup Assistant (NSA) download process corrupts during the self-provisioning process (captured on &lt;SPAN style="font-size: 10pt;"&gt;4.1.1 and &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;4.2.2 version&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2) If NSA is already installed, the network setup process (downloading profile, certificate) stops at last step: &lt;STRONG&gt;connecting to network, &lt;/STRONG&gt;meanwhile the connection itself successfully establishes. This bug is captured on 4.2.2 version, 4.1.1 is ok.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Google ACL is configured according to TrustSec docs and permits all traffic to google networks &lt;SPAN style="font-size: 10pt;"&gt;173.194.0.0/16 and &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;74.125.0.0/16.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 06:45:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186421#M178961</guid>
      <dc:creator>Jaaazman777</dc:creator>
      <dc:date>2021-07-04T06:45:13Z</dc:date>
    </item>
    <item>
      <title>BYOD: Android problems</title>
      <link>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186422#M178962</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello. I suggest you move your thread to Security -&amp;gt; NAC and AAA forums. They will probably help better there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: blue;"&gt;Rating useful replies is more useful than saying &lt;SPAN style="color: green;"&gt; "&lt;SPAN style="text-decoration: underline;"&gt;Thank you&lt;/SPAN&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Mar 2013 10:59:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186422#M178962</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2013-03-19T10:59:32Z</dc:date>
    </item>
    <item>
      <title>BYOD: Android problems</title>
      <link>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186423#M178963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello! &lt;/P&gt;&lt;P&gt;The problem with downloading &lt;SPAN style="font-size: 10pt;"&gt;Netwrok Setup Assistant (NSA) during the self-provisioning process&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt; is solved!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;The issue was about Google ACL on WLC: &lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;For test purpose we added &lt;STRONG&gt;permit ip any any&lt;/STRONG&gt; in the end of the &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;Google ACL. After that NSA was successfully downloaded.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Traffic capturing showed, that during NSA download, Android client established the connection to special network range, which belongs to local provider. In &lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;domaintools this net range has description: &lt;STRONG&gt;google &lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;after adding this range to Google ACL and deleting &lt;STRONG&gt;permit any any&lt;/STRONG&gt; rule, NSA was successfully downloaded.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In conclusion: Google play is georgaphicaly depended, we should take it into consideration. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Mar 2013 12:23:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186423#M178963</guid>
      <dc:creator>Jaaazman777</dc:creator>
      <dc:date>2013-03-19T12:23:48Z</dc:date>
    </item>
    <item>
      <title>BYOD: Android problems</title>
      <link>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186424#M178964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Great news that your issue is resolved.&lt;/P&gt;&lt;P&gt;+5 for solving your own probblem. &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amjad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: blue;"&gt;Rating useful replies is more useful than saying &lt;SPAN style="color: green;"&gt; "&lt;SPAN style="text-decoration: underline;"&gt;Thank you&lt;/SPAN&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Mar 2013 12:57:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186424#M178964</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2013-03-19T12:57:02Z</dc:date>
    </item>
    <item>
      <title>BYOD: Android problems</title>
      <link>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186425#M178965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;Thanks Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is really helpful, do we know what that undocumented range is?? We're running into the same issue.&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2013 19:16:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186425#M178965</guid>
      <dc:creator>aman.diwakar</dc:creator>
      <dc:date>2013-03-20T19:16:15Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD: Android problems</title>
      <link>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186426#M178966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 20:56:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/byod-android-problems/m-p/2186426#M178966</guid>
      <dc:creator>aman.diwakar</dc:creator>
      <dc:date>2013-03-21T20:56:50Z</dc:date>
    </item>
  </channel>
</rss>

