<?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 MU/client report with AP3912i in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/mu-client-report-with-ap3912i/m-p/44873#M3835</link>
    <description>I've a "special" setup which looks like that....&lt;BR /&gt;
&lt;BR /&gt;
AP3912i --&amp;gt; wired port#3 connects an AP3801i and MUs are connected to this AP with a bridge@AP topology.&lt;BR /&gt;
&lt;BR /&gt;
Everything works but the thing that bugs me is that the MUs are shown as 802.3 clients in the client report.&lt;BR /&gt;
&lt;BR /&gt;
That isn't completely wrong because the MAC is bridge@AP on the AP3801i to port#3 of the AP3912i but I thought that the 802.11 information would take precedence over the 802.3 information in the report.&lt;BR /&gt;
&lt;BR /&gt;
example&amp;gt;  the first line show the AP3801i connected to P3 of the AP3912, the other 2 clients are connected via wireless to the AP3801i but are shown as wired on the AP3912i&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="e3eb65980c4a4a87ac2e5e97bf1ce2a5_RackMultipart20180201-59433-ixg3gs-AP3912_clients_8023_inline.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/6009iE7B035E6120ACB0E/image-size/large?v=v2&amp;amp;px=999" role="button" title="e3eb65980c4a4a87ac2e5e97bf1ce2a5_RackMultipart20180201-59433-ixg3gs-AP3912_clients_8023_inline.png" alt="e3eb65980c4a4a87ac2e5e97bf1ce2a5_RackMultipart20180201-59433-ixg3gs-AP3912_clients_8023_inline.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
-Ron&lt;BR /&gt;</description>
    <pubDate>Thu, 01 Feb 2018 18:21:00 GMT</pubDate>
    <dc:creator>Ronald_Dvorak</dc:creator>
    <dc:date>2018-02-01T18:21:00Z</dc:date>
    <item>
      <title>MU/client report with AP3912i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/mu-client-report-with-ap3912i/m-p/44873#M3835</link>
      <description>I've a "special" setup which looks like that....&lt;BR /&gt;
&lt;BR /&gt;
AP3912i --&amp;gt; wired port#3 connects an AP3801i and MUs are connected to this AP with a bridge@AP topology.&lt;BR /&gt;
&lt;BR /&gt;
Everything works but the thing that bugs me is that the MUs are shown as 802.3 clients in the client report.&lt;BR /&gt;
&lt;BR /&gt;
That isn't completely wrong because the MAC is bridge@AP on the AP3801i to port#3 of the AP3912i but I thought that the 802.11 information would take precedence over the 802.3 information in the report.&lt;BR /&gt;
&lt;BR /&gt;
example&amp;gt;  the first line show the AP3801i connected to P3 of the AP3912, the other 2 clients are connected via wireless to the AP3801i but are shown as wired on the AP3912i&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="e3eb65980c4a4a87ac2e5e97bf1ce2a5_RackMultipart20180201-59433-ixg3gs-AP3912_clients_8023_inline.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/6009iE7B035E6120ACB0E/image-size/large?v=v2&amp;amp;px=999" role="button" title="e3eb65980c4a4a87ac2e5e97bf1ce2a5_RackMultipart20180201-59433-ixg3gs-AP3912_clients_8023_inline.png" alt="e3eb65980c4a4a87ac2e5e97bf1ce2a5_RackMultipart20180201-59433-ixg3gs-AP3912_clients_8023_inline.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
-Ron&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Feb 2018 18:21:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/mu-client-report-with-ap3912i/m-p/44873#M3835</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2018-02-01T18:21:00Z</dc:date>
    </item>
    <item>
      <title>RE: MU/client report with AP3912i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/mu-client-report-with-ap3912i/m-p/44874#M3836</link>
      <description>Please open a GTAC case.</description>
      <pubDate>Thu, 01 Feb 2018 19:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/mu-client-report-with-ap3912i/m-p/44874#M3836</guid>
      <dc:creator>Doug</dc:creator>
      <dc:date>2018-02-01T19:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: MU/client report with AP3912i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/mu-client-report-with-ap3912i/m-p/44875#M3837</link>
      <description>If a client in my scenario is moviing from the AP3801i to another AP (AP3825e in the below example) that has a direct CAPWAP connection the port/protocol is still 802.3 even the MU is clearly connected via 802.11 (screenshot below).&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="01077ae7b16945b4b016e01afaf503c7_RackMultipart20180205-111641-lxnl84-AP3912_clients_8023_02_inline.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/2471i76E9AE2B143936F7/image-size/large?v=v2&amp;amp;px=999" role="button" title="01077ae7b16945b4b016e01afaf503c7_RackMultipart20180205-111641-lxnl84-AP3912_clients_8023_02_inline.png" alt="01077ae7b16945b4b016e01afaf503c7_RackMultipart20180205-111641-lxnl84-AP3912_clients_8023_02_inline.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Feb 2018 01:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/mu-client-report-with-ap3912i/m-p/44875#M3837</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2018-02-06T01:57:00Z</dc:date>
    </item>
  </channel>
</rss>

