<?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: Two user two roles one ssid in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9302#M1822</link>
    <description>No, client isolation whitelists can be applied per-WLAN, not per-user. (Assuming you mean client isolation whitelist, I don't know of another whitelist policy in ZD.)&amp;nbsp;</description>
    <pubDate>Tue, 24 May 2016 21:28:09 GMT</pubDate>
    <dc:creator>jay_files</dc:creator>
    <dc:date>2016-05-24T21:28:09Z</dc:date>
    <item>
      <title>Two user two roles one ssid</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9299#M1819</link>
      <description>Can i do two users two roles and asign it to one wlan 
&lt;BR /&gt;
I have simple network setup zd1200, one vlan and 3 AP R700</description>
      <pubDate>Fri, 20 May 2016 17:55:40 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9299#M1819</guid>
      <dc:creator>bandar_aldawees</dc:creator>
      <dc:date>2016-05-20T17:55:40Z</dc:date>
    </item>
    <item>
      <title>Re: Two user two roles one ssid</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9300#M1820</link>
      <description>Yes, go to Configure &amp;gt; Roles, and create a Role that allows access to the WLANs you want. Then repeat for another Role.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Once Roles are created, go to Configure &amp;gt; Users and create Users with the proper Role selected.</description>
      <pubDate>Tue, 24 May 2016 19:11:48 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9300#M1820</guid>
      <dc:creator>jay_files</dc:creator>
      <dc:date>2016-05-24T19:11:48Z</dc:date>
    </item>
    <item>
      <title>Re: Two user two roles one ssid</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9301#M1821</link>
      <description>Graet. What about whitelist polcy can i asign it just for one user  and the other user no. With the same  ssid (wlan) .</description>
      <pubDate>Tue, 24 May 2016 21:02:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9301#M1821</guid>
      <dc:creator>bandar_aldawees</dc:creator>
      <dc:date>2016-05-24T21:02:15Z</dc:date>
    </item>
    <item>
      <title>Re: Two user two roles one ssid</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9302#M1822</link>
      <description>No, client isolation whitelists can be applied per-WLAN, not per-user. (Assuming you mean client isolation whitelist, I don't know of another whitelist policy in ZD.)&amp;nbsp;</description>
      <pubDate>Tue, 24 May 2016 21:28:09 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9302#M1822</guid>
      <dc:creator>jay_files</dc:creator>
      <dc:date>2016-05-24T21:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: Two user two roles one ssid</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9303#M1823</link>
      <description>Yes  it is , so there is no why to isolate one user  , what about vlan two user different vlan will it could be done like that</description>
      <pubDate>Tue, 24 May 2016 21:34:10 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Two-user-two-roles-one-ssid/m-p/9303#M1823</guid>
      <dc:creator>bandar_aldawees</dc:creator>
      <dc:date>2016-05-24T21:34:10Z</dc:date>
    </item>
  </channel>
</rss>

