<?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: RTS/CTS and Fragmentation Thresholds in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300363#M193768</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cisco never answered (not like I really expected them to).  The answer to the question is that Cisco rebrands Atheros cards, and the Atheros reference drivers and client utilities don't have this functionality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;visit &lt;A class="jive-link-custom" href="http://www.cwnp.com/phpBB2/index.php" target="_blank"&gt;http://www.cwnp.com/phpBB2/index.php&lt;/A&gt; for quicker replies to technical topical by much more experienced people.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Oct 2005 23:17:09 GMT</pubDate>
    <dc:creator>ccie</dc:creator>
    <dc:date>2005-10-10T23:17:09Z</dc:date>
    <item>
      <title>RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300361#M193766</link>
      <description>&lt;P&gt;Why does the CB21AG card not support these settings like the 350 and CB20A cards do?  These settings are VERY important in my environment.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 16:40:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300361#M193766</guid>
      <dc:creator>ccie</dc:creator>
      <dc:date>2021-07-04T16:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300362#M193767</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you ever get a response of find the answer to this?  I am in the same boat.  Lots of hidden nodes and lots of AP's on the same channel.  I am wondering if Cisco is getting out of the client card market.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Oct 2005 17:15:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300362#M193767</guid>
      <dc:creator>jcosgrove</dc:creator>
      <dc:date>2005-10-10T17:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300363#M193768</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cisco never answered (not like I really expected them to).  The answer to the question is that Cisco rebrands Atheros cards, and the Atheros reference drivers and client utilities don't have this functionality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;visit &lt;A class="jive-link-custom" href="http://www.cwnp.com/phpBB2/index.php" target="_blank"&gt;http://www.cwnp.com/phpBB2/index.php&lt;/A&gt; for quicker replies to technical topical by much more experienced people.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Oct 2005 23:17:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300363#M193768</guid>
      <dc:creator>ccie</dc:creator>
      <dc:date>2005-10-10T23:17:09Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300364#M193769</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just got my first response from TAC on this.  I asked how do I set the fragmentation and RTS threshold on the cb21ag card.  The response was that I set these on the AP and I should not adjust these because they are set to optimum.  I asked for the case to be escalated to someone who actually knows what and why I need to set these.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I feel like I am dealing in the "Black Arts" when asking questions about building large scale 802.11 wireless networks and dealing with these issues.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Oct 2005 11:26:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300364#M193769</guid>
      <dc:creator>jcosgrove</dc:creator>
      <dc:date>2005-10-11T11:26:36Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300365#M193770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are very few people at Cisco that know anything about 802.11 - trust me.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Oct 2005 13:09:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300365#M193770</guid>
      <dc:creator>ccie</dc:creator>
      <dc:date>2005-10-11T13:09:08Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300366#M193771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not near my laptop, so I can't verify this, but I believe that if you bring up the "Network Connections" | &lt;SELECT the="" wireless="" nic=""&gt; | Properties | Advanced&lt;/SELECT&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are a number of properties you can set (like powersave modes, long or sort preambles, etc). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps the frag threshold and CTS/RTS time settings are available there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FWIW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2005 14:40:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300366#M193771</guid>
      <dc:creator>scottmac</dc:creator>
      <dc:date>2005-10-12T14:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300367#M193772</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are sadly mistaken.  You just aren't talking to the right people.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2006 03:34:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300367#M193772</guid>
      <dc:creator>jakew</dc:creator>
      <dc:date>2006-08-31T03:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300368#M193773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You should also be honest about your agenda.  Are you the Devin Akin, CTO of Planet3?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2006 03:38:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300368#M193773</guid>
      <dc:creator>jakew</dc:creator>
      <dc:date>2006-08-31T03:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300369#M193774</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That post was a year ago, and at that point, my statement was spot on.  Today, I would definitely say that more Cisco engineers are up-to-speed on 802.11 1) than ever before, and 2) as much or more than any of their competitors.  That's a long way to come in 1 year, so my congratulations.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2006 11:16:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300369#M193774</guid>
      <dc:creator>intouchmin</dc:creator>
      <dc:date>2006-08-31T11:16:26Z</dc:date>
    </item>
    <item>
      <title>Re: RTS/CTS and Fragmentation Thresholds</title>
      <link>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300370#M193775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I work a lot of wireless and I have to agree.  There was a time back when I posted this message that it was like a mystery if you called and wanted to discuss anything beyond a basic AP configuration and forget about RF issues.  Now things are starting to get better.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2006 11:46:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/rts-cts-and-fragmentation-thresholds/m-p/300370#M193775</guid>
      <dc:creator>jcosgrove</dc:creator>
      <dc:date>2006-08-31T11:46:34Z</dc:date>
    </item>
  </channel>
</rss>

