<?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: 350 bridge problem in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/350-bridge-problem/m-p/137683#M194828</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a good line of sight? Are the bridges configured for the necessary power / bit rate to cover that distance? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 May 2003 13:31:48 GMT</pubDate>
    <dc:creator>d.nogueira</dc:creator>
    <dc:date>2003-05-09T13:31:48Z</dc:date>
    <item>
      <title>350 bridge problem</title>
      <link>https://community.cisco.com/t5/wireless/350-bridge-problem/m-p/137682#M194827</link>
      <description>&lt;P&gt;I have two 350 bridges running approx 2/3 miles with 21dbi yagi antennas. The uplink is continuously dropping with no pattern showing. The 350's are running the latest version of code. Tried with and without encryption, tried with the beacon rate at 2000 and also tried with variors options with regards to 'role in radio network'. No change what so ever. Both 350's are competely fine and work when using the small antennas in a back to back senario. This would suggest the cable of the yagi or the yagi itself could be damaged but this has been checked and verified ok. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 15:41:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/350-bridge-problem/m-p/137682#M194827</guid>
      <dc:creator>bernards</dc:creator>
      <dc:date>2021-07-04T15:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: 350 bridge problem</title>
      <link>https://community.cisco.com/t5/wireless/350-bridge-problem/m-p/137683#M194828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a good line of sight? Are the bridges configured for the necessary power / bit rate to cover that distance? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 May 2003 13:31:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/350-bridge-problem/m-p/137683#M194828</guid>
      <dc:creator>d.nogueira</dc:creator>
      <dc:date>2003-05-09T13:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: 350 bridge problem</title>
      <link>https://community.cisco.com/t5/wireless/350-bridge-problem/m-p/137684#M194829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1 change the data rate settings for 5.5 and 11.0 to yes. &lt;/P&gt;&lt;P&gt;2 check the transmission power.&lt;/P&gt;&lt;P&gt;3 make a link test  carrier should not be &amp;lt; 60%.&lt;/P&gt;&lt;P&gt;4 Try changing the channel.&lt;/P&gt;&lt;P&gt;5 Downgrade to 11.23 (best of all ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reset the device to factory defaults, this is bcoz when upgraded from 11.0 series firmware to 12.0 the device configuration tends to get corrupt in certain cases, hence resetting to default at both ends will resolve the same.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 May 2003 14:53:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/350-bridge-problem/m-p/137684#M194829</guid>
      <dc:creator>rsahney</dc:creator>
      <dc:date>2003-05-12T14:53:17Z</dc:date>
    </item>
  </channel>
</rss>

