<?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 Mac Address problems in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/mac-address-problems/m-p/164431#M98704</link>
    <description>&lt;P&gt;I have to 350 ap's running. One goes into a switch over a trunk port and the other into a second switch over a trunk port. When a client is associated to one AP but then loses association for what ever reason and then associates with the other AP what happens to the mac address of this client in the original switches mac table. This will think that the client is on one AP but it really is now in the other AP connected to the other switch. Does the original switch flush this mac address after a certain period of time?&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 15:42:36 GMT</pubDate>
    <dc:creator>bernards</dc:creator>
    <dc:date>2021-07-04T15:42:36Z</dc:date>
    <item>
      <title>Mac Address problems</title>
      <link>https://community.cisco.com/t5/wireless/mac-address-problems/m-p/164431#M98704</link>
      <description>&lt;P&gt;I have to 350 ap's running. One goes into a switch over a trunk port and the other into a second switch over a trunk port. When a client is associated to one AP but then loses association for what ever reason and then associates with the other AP what happens to the mac address of this client in the original switches mac table. This will think that the client is on one AP but it really is now in the other AP connected to the other switch. Does the original switch flush this mac address after a certain period of time?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 15:42:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mac-address-problems/m-p/164431#M98704</guid>
      <dc:creator>bernards</dc:creator>
      <dc:date>2021-07-04T15:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: Mac Address problems</title>
      <link>https://community.cisco.com/t5/wireless/mac-address-problems/m-p/164432#M98705</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the client roams then there will be an exchange of the clients details between the 2 AP's using Inter AP protocol IAPP and any packets sent to the old AP will be forwarded to the new AP via the ethernet side&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the client simply disassociates then associated to the new AP then it has not roamed. So this information is not exchanged This would happen if your 2 cells dont overlap.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you look in the logs you can see a roam message when a client roams.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using Non Cisco clients then they may not be able to roam.  The standards on this are very close to be finalised now so in the future this will be the case for all clients&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 18 May 2003 23:22:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mac-address-problems/m-p/164432#M98705</guid>
      <dc:creator>derwin</dc:creator>
      <dc:date>2003-05-18T23:22:08Z</dc:date>
    </item>
  </channel>
</rss>

