<?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: AP's with duplicate BSSIDs in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap-s-with-duplicate-bssids/m-p/3951992#M104215</link>
    <description>Should be fine.</description>
    <pubDate>Fri, 01 Nov 2019 22:41:36 GMT</pubDate>
    <dc:creator>Leo Laohoo</dc:creator>
    <dc:date>2019-11-01T22:41:36Z</dc:date>
    <item>
      <title>AP's with duplicate BSSIDs</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-with-duplicate-bssids/m-p/3951973#M104214</link>
      <description>&lt;P&gt;While testing &amp;nbsp;a new wifi analyzer app,&amp;nbsp; WinFi Lite 1.0&amp;nbsp; (winfi.exe), I sorted the BSSID list in mac order and discovered that the AP over my head and one across the hallway were announcing the same BSSIDs with different SSIDs.&amp;nbsp; Both are on the same WLC but in different AP Groups (similar ssids, different&amp;nbsp;sequence).&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wonder what the consequences are for roaming etc?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 18:14:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-with-duplicate-bssids/m-p/3951973#M104214</guid>
      <dc:creator>David Ritter</dc:creator>
      <dc:date>2021-07-05T18:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: AP's with duplicate BSSIDs</title>
      <link>https://community.cisco.com/t5/wireless/ap-s-with-duplicate-bssids/m-p/3951992#M104215</link>
      <description>Should be fine.</description>
      <pubDate>Fri, 01 Nov 2019 22:41:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-s-with-duplicate-bssids/m-p/3951992#M104215</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2019-11-01T22:41:36Z</dc:date>
    </item>
  </channel>
</rss>

