<?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: RE: Client Isolation - Extreme  Wireless controller in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/120750#M7559</link>
    <description>&lt;P&gt;Hi to all, we have to:&lt;/P&gt;&lt;P&gt;Permit only traffic destined to our gateway (MAC_Source/Mac_Dest)&lt;/P&gt;&lt;P&gt;Permit Broadcast (Mac_Dest ff:ff:ff:ff:ff:ff)&lt;/P&gt;&lt;P&gt;Deny all&lt;/P&gt;&lt;P&gt;With this all works fine.&lt;/P&gt;</description>
    <pubDate>Thu, 13 Nov 2025 11:53:48 GMT</pubDate>
    <dc:creator>Rey_Juan_Carlos</dc:creator>
    <dc:date>2025-11-13T11:53:48Z</dc:date>
    <item>
      <title>Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41189#M2903</link>
      <description>Hi Team,&lt;BR /&gt;
Does anybody have any ideas of how client isolation can be achieved   for users on the same SSID and in the same vlan &lt;B&gt;in Controller&lt;/B&gt;. I know other   manufacturers have a simple &lt;B&gt;Client isolation&lt;/B&gt; feature that will achieve   this but I can't find it in Extreme Controller.&lt;BR /&gt;
My ultimate goal is "Users have to communicate only gateway not others".&lt;BR /&gt;
Any ideas welcome..!!!&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Jan 2017 08:07:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41189#M2903</guid>
      <dc:creator>Boopaa</dc:creator>
      <dc:date>2017-01-12T08:07:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41190#M2904</link>
      <description>Hi Boopathy,&lt;BR /&gt;
&lt;BR /&gt;
Please find the steps below to block wireless client to client traffic on a WLAN.&lt;BR /&gt;
&lt;BR /&gt;
&lt;OL&gt; 
&lt;LI&gt;From the Controller/Appliance GUI  
&lt;/LI&gt;&lt;LI&gt;Select &lt;B&gt;WLAN&lt;/B&gt; Menu 
&lt;/LI&gt;&lt;LI&gt; Select desired WLAN to block MU to MU traffic  
&lt;/LI&gt;&lt;LI&gt; Click &lt;B&gt;Advanced&lt;/B&gt; button  
&lt;/LI&gt;&lt;LI&gt; Check the box in the CLient Behavior Window  Block MU to MU traffic (not supported on Bridged at AP topologies) 
&lt;/LI&gt;&lt;LI&gt;Click the &lt;B&gt;Apply&lt;/B&gt; Button 
&lt;/LI&gt;&lt;LI&gt; Click &lt;B&gt;Save&lt;/B&gt; Button &lt;/LI&gt;&lt;/OL&gt;Reference article below,&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-block-wireless-client-to-client-traffic-on-a-WLAN" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-block-wireless-client-to-client-tra...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Nathiya M&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Jan 2017 11:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41190#M2904</guid>
      <dc:creator>Nathiya_M</dc:creator>
      <dc:date>2017-01-12T11:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41191#M2905</link>
      <description>Thank you for the quick response and I will confirm soon..!!&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Jan 2017 11:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41191#M2905</guid>
      <dc:creator>Boopaa</dc:creator>
      <dc:date>2017-01-12T11:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41192#M2906</link>
      <description>Hi Boopathy,&lt;BR /&gt;
&lt;BR /&gt;
Please confirm, is it B@EWC or B@AP topology?&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Nathiya M</description>
      <pubDate>Thu, 12 Jan 2017 11:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41192#M2906</guid>
      <dc:creator>Nathiya_M</dc:creator>
      <dc:date>2017-01-12T11:13:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41193#M2907</link>
      <description>In the B@AP the "block MU to MU" does not work. You can create rule in Policy Role  and allow only traffic destined to your gateway MAC and Broadcasts all other can be blocked.</description>
      <pubDate>Thu, 12 Jan 2017 12:49:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41193#M2907</guid>
      <dc:creator>Zdeněk_Pala</dc:creator>
      <dc:date>2017-01-12T12:49:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41194#M2908</link>
      <description>Please check the policy rule configuration for B@AP setup,&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Block-MU-to-MU-enabled-but-users-can-still-communicate" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Block-MU-to-MU-enabled-but-users-can-sti...&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Nathiya M</description>
      <pubDate>Thu, 12 Jan 2017 13:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41194#M2908</guid>
      <dc:creator>Nathiya_M</dc:creator>
      <dc:date>2017-01-12T13:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41195#M2909</link>
      <description>MU to MU also doesn't work if the client are connected on the same AP.&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Jan 2017 20:45:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41195#M2909</guid>
      <dc:creator>Umut_Aydin</dc:creator>
      <dc:date>2017-01-12T20:45:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41196#M2910</link>
      <description>&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Block-MU-to-MU-enabled-but-users-can-still-communicate" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Block-MU-to-MU-enabled-but-users-can-sti...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Jan 2017 22:36:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41196#M2910</guid>
      <dc:creator>Craig_Guilmette</dc:creator>
      <dc:date>2017-01-12T22:36:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41197#M2911</link>
      <description>Helllo I have the same problem . I implemented - &lt;BR /&gt;
&lt;OL&gt; 
&lt;LI&gt;From the Controller/Appliance GUI 
&lt;/LI&gt;&lt;LI&gt;Select &lt;B&gt;WLAN&lt;/B&gt; Menu 
&lt;/LI&gt;&lt;LI&gt;Select desired WLAN to block MU to MU traffic 
&lt;/LI&gt;&lt;LI&gt;Click &lt;B&gt;Advanced&lt;/B&gt; button 
&lt;/LI&gt;&lt;LI&gt;Check the box in the CLient Behavior Window Block MU to MU traffic (not supported on Bridged at AP topologies) 
&lt;/LI&gt;&lt;LI&gt;Click the &lt;B&gt;Apply&lt;/B&gt; Button 
&lt;/LI&gt;&lt;LI&gt;Click &lt;B&gt;Save&lt;/B&gt; Button 
&lt;/LI&gt;&lt;/OL&gt; and Applyed the Rulles .&lt;BR /&gt;
&lt;BR /&gt;
The problem is solved only 1/2 . If 2 users are connected on the same ap everything is fine but if 1 ap is associated to wlc 1 and other ap-s is associated to second wlc 2 and 1 user is connected to 1 ap from wlc 1 and other users is connected to the ap from wlc 2 they can still comunicate&lt;BR /&gt;
&lt;BR /&gt;
PLease if you have other option let me know &lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Thank you</description>
      <pubDate>Wed, 26 Jun 2019 15:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41197#M2911</guid>
      <dc:creator>VDaniel</dc:creator>
      <dc:date>2019-06-26T15:30:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41198#M2912</link>
      <description>&lt;BLOCKQUOTE&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Block-MU-to-MU-enabled-but-users-can-still-communicate&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;
Have you read the above document? This is the way to block the users from talking to anybody except their default gateway.</description>
      <pubDate>Wed, 26 Jun 2019 19:34:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41198#M2912</guid>
      <dc:creator>Craig_Guilmette</dc:creator>
      <dc:date>2019-06-26T19:34:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41199#M2913</link>
      <description>Hello Craig&lt;BR /&gt;
I  did , the problem ist that the VNS is B@EWC NOT B@AP  - IS a Guest VNS</description>
      <pubDate>Wed, 26 Jun 2019 19:41:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41199#M2913</guid>
      <dc:creator>VDaniel</dc:creator>
      <dc:date>2019-06-26T19:41:00Z</dc:date>
    </item>
    <item>
      <title>RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41200#M2914</link>
      <description>&lt;BR /&gt;
It doesn't matter how the topology is forwarded..These ACL/Filter rules are applied to the guests role preventing the users from communicating with anybody on its subnet except the default gateway. Call our GTAC if you still need help after looking at the document again.</description>
      <pubDate>Wed, 26 Jun 2019 19:47:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/41200#M2914</guid>
      <dc:creator>Craig_Guilmette</dc:creator>
      <dc:date>2019-06-26T19:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/120531#M7557</link>
      <description>&lt;P&gt;Hi to all.&lt;/P&gt;&lt;P&gt;We have a large problem with this solution, in our scenario, we have multiple vlans for every user collective (with Radius Filter-Id) with &lt;A href="mailto:B@AP" target="_blank"&gt;B@AP&lt;/A&gt;&amp;nbsp;topologies, but if we have to make 1 rule to permit every Gateway and one rule to deny every network, we fill the capacity rules on the aps.&amp;nbsp;&lt;/P&gt;&lt;P&gt;¿Somebody have better solution?&lt;/P&gt;&lt;P&gt;Thanks a lot&lt;/P&gt;</description>
      <pubDate>Fri, 17 Oct 2025 09:12:22 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/120531#M7557</guid>
      <dc:creator>Rey_Juan_Carlos</dc:creator>
      <dc:date>2025-10-17T09:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: RE: Client Isolation - Extreme  Wireless controller</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/120750#M7559</link>
      <description>&lt;P&gt;Hi to all, we have to:&lt;/P&gt;&lt;P&gt;Permit only traffic destined to our gateway (MAC_Source/Mac_Dest)&lt;/P&gt;&lt;P&gt;Permit Broadcast (Mac_Dest ff:ff:ff:ff:ff:ff)&lt;/P&gt;&lt;P&gt;Deny all&lt;/P&gt;&lt;P&gt;With this all works fine.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Nov 2025 11:53:48 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/client-isolation-extreme-wireless-controller/m-p/120750#M7559</guid>
      <dc:creator>Rey_Juan_Carlos</dc:creator>
      <dc:date>2025-11-13T11:53:48Z</dc:date>
    </item>
  </channel>
</rss>

