<?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: MFP Anomaly in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913440#M220372</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Randy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry about that my friend! My eyes must have been half-closed when I sent that. My appologies &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take care,&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Jan 2008 19:21:00 GMT</pubDate>
    <dc:creator>Rob Huffman</dc:creator>
    <dc:date>2008-01-10T19:21:00Z</dc:date>
    <item>
      <title>MFP Anomaly</title>
      <link>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913437#M220369</link>
      <description>&lt;P&gt;Ever since upgrading my 4404 and WiSM controllers, I keep getting a bunch of MFP errors like the one below.  Is anyone else seeing the same thing ?  I have MFP set to optional.  It is occurring in multiple cities.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Randy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;----------------------------------   &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt; Message  &lt;/P&gt;&lt;P&gt;MFP Anomaly Detected - 582 'Invalid MIC' violation(s) have originated from the AP with BSS '00:1c:0e:40:ba:6f'. This was detected by the radio with Slot ID '1' of the AP with MAC '00:1a:e2:10:e0:80' when observing 'Beacon, Disassociation, and Deauthentication' frames.  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 22:11:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913437#M220369</guid>
      <dc:creator>rduke</dc:creator>
      <dc:date>2021-07-03T22:11:23Z</dc:date>
    </item>
    <item>
      <title>Re: MFP Anomaly</title>
      <link>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913438#M220370</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Randy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just thought you might want to see this recent post where these same errors are ocurring after an upgrade to 4.2.61.0. Maybe you could piggyback on this TAC Case;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Wireless%20-%20Mobility&amp;amp;topic=General&amp;amp;CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cbf0293/0#selected_message" target="_blank"&gt;http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Wireless%20-%20Mobility&amp;amp;topic=General&amp;amp;CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cbf0293/0#selected_message&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 03:43:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913438#M220370</guid>
      <dc:creator>Rob Huffman</dc:creator>
      <dc:date>2008-01-10T03:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: MFP Anomaly</title>
      <link>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913439#M220371</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Rob,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually that was my post, but thanks anyhow.  I did talk to Cisco about it yesterday since they were slow about getting back to me.  I had the call open since Dec 13th, but they said they are working on it so maybe we will see a fix.  In the meantime the workaround is to turn off MFP if you don't want to see the errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Randy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 14:01:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913439#M220371</guid>
      <dc:creator>rduke</dc:creator>
      <dc:date>2008-01-10T14:01:12Z</dc:date>
    </item>
    <item>
      <title>Re: MFP Anomaly</title>
      <link>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913440#M220372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Randy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry about that my friend! My eyes must have been half-closed when I sent that. My appologies &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take care,&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 19:21:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913440#M220372</guid>
      <dc:creator>Rob Huffman</dc:creator>
      <dc:date>2008-01-10T19:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: MFP Anomaly</title>
      <link>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913441#M220373</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Randy:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been seeing this as well and have chalked it up to Cisco's needing a serious refresh on their wireless IDS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have spent so much time cumulatively on trying to get them to resolve these false alarms that I ought to send them a bill!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Jan 2008 19:07:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913441#M220373</guid>
      <dc:creator>johnruffing</dc:creator>
      <dc:date>2008-01-28T19:07:57Z</dc:date>
    </item>
    <item>
      <title>Re: MFP Anomaly</title>
      <link>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913442#M220374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Randy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you been getting calls from users regarding loss of connection to the APs on the wireless network?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  We upgraded to 4.2.217 on our 4404 WLC two week ago.  The MFP messages started showing up then.  Also, users are only able to stay attached for about 30 min.  The must manually reconnect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Phil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Apr 2008 18:36:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913442#M220374</guid>
      <dc:creator>psiegling</dc:creator>
      <dc:date>2008-04-11T18:36:29Z</dc:date>
    </item>
    <item>
      <title>Re: MFP Anomaly</title>
      <link>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913443#M220375</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Phil,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was curious if you were still having issues with wireless clients staying connected for longer than 30 minutes? I am currently having a similar issue however I am not sure if it is really the same. Clients with certain Intel chipsets lose their DHCP information after 30 minutes (half of the 1 hour lease) and they have to disable/enable the wireless connection in order to reconnect.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 19:07:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mfp-anomaly/m-p/913443#M220375</guid>
      <dc:creator>s.clinard</dc:creator>
      <dc:date>2008-08-04T19:07:07Z</dc:date>
    </item>
  </channel>
</rss>

