<?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: WLAN with Access control L2 and L3 policy not working in SmartZone and Virtual SmartZone</title>
    <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/WLAN-with-Access-control-L2-and-L3-policy-not-working/m-p/77068#M4976</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/9096"&gt;@brian_koomen&lt;/a&gt;&amp;nbsp;, looks like either the L3 ACL or L2 ACL is missing an important entry. I would suggest try to use one at a moment on the WLAN and test to narrow down whether it is the L3 ACL or the L2 ACL ( first test with only applying the L3 ACL and then with L2 ACL alone and compare which scenario is working).&lt;BR /&gt;&lt;BR /&gt;As for L2 ACLs, make sure that Mac-address randomization feature of clients devices is also taken into consideration as it may cause issues because of dynamic mac-address.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Mon, 18 Mar 2024 00:04:59 GMT</pubDate>
    <dc:creator>Dilshad_Zafar</dc:creator>
    <dc:date>2024-03-18T00:04:59Z</dc:date>
    <item>
      <title>WLAN with Access control L2 and L3 policy not working</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/WLAN-with-Access-control-L2-and-L3-policy-not-working/m-p/76944#M4974</link>
      <description>&lt;P&gt;On a Smart Zone 100 controller with firmware:&amp;nbsp;&lt;SPAN&gt;6.1.1.0.959&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I am trying to setup a WLAN with a WPA password and with a L3 policy that restricts access to our corporate network and L2 policy that restrict access to only certain MAC Addresses.&lt;/P&gt;&lt;P&gt;The problem I am having.....When putting all this together, the client keeps saying the password is incorrect but I know it is correct.&amp;nbsp; &amp;nbsp;I can make the WLAN unsecure and the clients can get access.&lt;/P&gt;&lt;P&gt;I am not sure why this would be happening.&amp;nbsp; &amp;nbsp; If the system allows you configure it this way then it should work, right?&amp;nbsp; What am I missing?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2024 12:55:43 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/WLAN-with-Access-control-L2-and-L3-policy-not-working/m-p/76944#M4974</guid>
      <dc:creator>brian_koomen</dc:creator>
      <dc:date>2024-03-14T12:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: WLAN with Access control L2 and L3 policy not working</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/WLAN-with-Access-control-L2-and-L3-policy-not-working/m-p/77068#M4976</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/9096"&gt;@brian_koomen&lt;/a&gt;&amp;nbsp;, looks like either the L3 ACL or L2 ACL is missing an important entry. I would suggest try to use one at a moment on the WLAN and test to narrow down whether it is the L3 ACL or the L2 ACL ( first test with only applying the L3 ACL and then with L2 ACL alone and compare which scenario is working).&lt;BR /&gt;&lt;BR /&gt;As for L2 ACLs, make sure that Mac-address randomization feature of clients devices is also taken into consideration as it may cause issues because of dynamic mac-address.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2024 00:04:59 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/WLAN-with-Access-control-L2-and-L3-policy-not-working/m-p/77068#M4976</guid>
      <dc:creator>Dilshad_Zafar</dc:creator>
      <dc:date>2024-03-18T00:04:59Z</dc:date>
    </item>
  </channel>
</rss>

