<?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 Header CRC errors on Radio0-802.11G interface in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/header-crc-errors-on-radio0-802-11g-interface/m-p/691900#M191310</link>
    <description>&lt;P&gt;We are receiving numerous CRC errors on the Radio interface for a Cisco 1310. It is a point-to-point bridge connection; both Root and Non-root are generating the errors.&lt;/P&gt;&lt;P&gt;Description (Lifetime-Last 5 seconds)&lt;/P&gt;&lt;P&gt;Header CRC Errors 15088213-125&lt;/P&gt;&lt;P&gt;Protocol Defers 732-1&lt;/P&gt;&lt;P&gt;Invalid Header 353065-1&lt;/P&gt;&lt;P&gt;Energy Detect Defers 4371-2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What needs to be changed? Is this common between bridges? I'm guessing this is affecting the other sites as well (similar config). Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;</description>
    <pubDate>Sat, 03 Jul 2021 20:10:26 GMT</pubDate>
    <dc:creator>augsupport</dc:creator>
    <dc:date>2021-07-03T20:10:26Z</dc:date>
    <item>
      <title>Header CRC errors on Radio0-802.11G interface</title>
      <link>https://community.cisco.com/t5/wireless/header-crc-errors-on-radio0-802-11g-interface/m-p/691900#M191310</link>
      <description>&lt;P&gt;We are receiving numerous CRC errors on the Radio interface for a Cisco 1310. It is a point-to-point bridge connection; both Root and Non-root are generating the errors.&lt;/P&gt;&lt;P&gt;Description (Lifetime-Last 5 seconds)&lt;/P&gt;&lt;P&gt;Header CRC Errors 15088213-125&lt;/P&gt;&lt;P&gt;Protocol Defers 732-1&lt;/P&gt;&lt;P&gt;Invalid Header 353065-1&lt;/P&gt;&lt;P&gt;Energy Detect Defers 4371-2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What needs to be changed? Is this common between bridges? I'm guessing this is affecting the other sites as well (similar config). Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 20:10:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/header-crc-errors-on-radio0-802-11g-interface/m-p/691900#M191310</guid>
      <dc:creator>augsupport</dc:creator>
      <dc:date>2021-07-03T20:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: Header CRC errors on Radio0-802.11G interface</title>
      <link>https://community.cisco.com/t5/wireless/header-crc-errors-on-radio0-802-11g-interface/m-p/691901#M191311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It may be due to signal bounce/propagation.  you can try moving the AP to another location and see if the CRC still increase.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The access point is always listening for wireless frames, meaning that if it detects energy, it tries to translate what it hears into 802.11 frames.  This could come from clients that are associated to a different AP, it could be from other APs, or any other 802.11 device that is operating on the frequency that the AP is using.  Theenergy could also come from wireless phones and other non-802.11 devices.  In short, there are a lot of possible sources that can generate traffic.&lt;/P&gt;&lt;P&gt;As a result of the signals that the access point detects, some of them are immediately discarded as "Header CRC errors."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Nov 2006 16:25:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/header-crc-errors-on-radio0-802-11g-interface/m-p/691901#M191311</guid>
      <dc:creator>sbilgi</dc:creator>
      <dc:date>2006-11-07T16:25:17Z</dc:date>
    </item>
  </channel>
</rss>

