<?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: Rogue Classifications in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333966#M216440</link>
    <description>When you added the client to mac filter did the drops stop/decrease?</description>
    <pubDate>Tue, 20 Feb 2018 02:33:28 GMT</pubDate>
    <dc:creator>jeetkulkarni</dc:creator>
    <dc:date>2018-02-20T02:33:28Z</dc:date>
    <item>
      <title>Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333932#M216438</link>
      <description>&lt;P&gt;Kindly let me know what are the implications to the Cisco WLC detecting rogue client and putting a "Threat" label against it? Does it block the client from accessing the networks or simply puts a label and let the client access if it can. This is related to the bug identified here -&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf31881" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf31881&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We currently have valid Lenovo X1 laptops showing in Rogue clients in threat list. Most of the clients have network drops and intermittent wireless connection issues.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 15:16:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333932#M216438</guid>
      <dc:creator>jeetkulkarni</dc:creator>
      <dc:date>2021-07-05T15:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333945#M216439</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;I had a similar experience and in my case the client was unable to connect. I had to add client mac address on the Mac filter as work around.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;I think you could debug this client and see if the drop cause is related to the rogue classification or not.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2018 01:34:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333945#M216439</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2018-02-20T01:34:25Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333966#M216440</link>
      <description>When you added the client to mac filter did the drops stop/decrease?</description>
      <pubDate>Tue, 20 Feb 2018 02:33:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333966#M216440</guid>
      <dc:creator>jeetkulkarni</dc:creator>
      <dc:date>2018-02-20T02:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333970#M216441</link>
      <description>&lt;P&gt;In my situation it was not drop but client did not join the network.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2018 02:42:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333970#M216441</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2018-02-20T02:42:41Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333974#M216442</link>
      <description>Sure, we have similar issues wherein the client does not join the network. In some instances it just looses network connectivity in the middle of no where. Does it sound familiar?</description>
      <pubDate>Tue, 20 Feb 2018 02:49:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333974#M216442</guid>
      <dc:creator>jeetkulkarni</dc:creator>
      <dc:date>2018-02-20T02:49:35Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333981#M216443</link>
      <description>&lt;P&gt;Yes it does.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Try to add classify those clients as friendly on rogue policy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;If possible, run a debug for those dropping ones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Most important, upgrade the wlc just to make sure you are not under a bug.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2018 03:07:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3333981#M216443</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2018-02-20T03:07:04Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3334629#M216444</link>
      <description>I've updated WLC to version 8.3.151.0 for now, clients seem to be connecting OK but still too early to confirm.</description>
      <pubDate>Tue, 20 Feb 2018 21:32:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3334629#M216444</guid>
      <dc:creator>jeetkulkarni</dc:creator>
      <dc:date>2018-02-20T21:32:36Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3334752#M216445</link>
      <description>&lt;P&gt;Should be enough. Inexplicable behavior usually is bug and upgrade is the way to go.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2018 02:49:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3334752#M216445</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2018-02-21T02:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: Rogue Classifications</title>
      <link>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3337495#M216446</link>
      <description>&lt;P&gt;The behavior is still seen, we now have a TAC case open!&lt;/P&gt;</description>
      <pubDate>Sun, 25 Feb 2018 22:47:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rogue-classifications/m-p/3337495#M216446</guid>
      <dc:creator>jeetkulkarni</dc:creator>
      <dc:date>2018-02-25T22:47:20Z</dc:date>
    </item>
  </channel>
</rss>

