<?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 Wifi solution for gated community in FlexMaster</title>
    <link>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29235#M296</link>
    <description>I'm working on an opportunity for a gated community and would like to know if the following design idea will work. Deploy P300's on poles in strategic locations around the gated area then mesh a couple of R500 or 7372 towards these units. &lt;BR /&gt;&lt;BR /&gt;Following on this what is the max number of indoor AP's that I'll be able to mesh towards the P300 in a mulitpoint config? The manual is not very clear on this point</description>
    <pubDate>Mon, 27 Jul 2015 09:08:33 GMT</pubDate>
    <dc:creator>Julian_Daniels</dc:creator>
    <dc:date>2015-07-27T09:08:33Z</dc:date>
    <item>
      <title>Wifi solution for gated community</title>
      <link>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29235#M296</link>
      <description>I'm working on an opportunity for a gated community and would like to know if the following design idea will work. Deploy P300's on poles in strategic locations around the gated area then mesh a couple of R500 or 7372 towards these units. &lt;BR /&gt;&lt;BR /&gt;Following on this what is the max number of indoor AP's that I'll be able to mesh towards the P300 in a mulitpoint config? The manual is not very clear on this point</description>
      <pubDate>Mon, 27 Jul 2015 09:08:33 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29235#M296</guid>
      <dc:creator>Julian_Daniels</dc:creator>
      <dc:date>2015-07-27T09:08:33Z</dc:date>
    </item>
    <item>
      <title>Re: Wifi solution for gated community</title>
      <link>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29236#M297</link>
      <description>Julian,&lt;BR /&gt;&lt;BR /&gt;zd1200/ZD3k Controller is must for MESH.&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;P300 will NOT mesh with any Ruckus product as it can't be managed/controlled by a controller + its a p2p/mp product with 30 degree beamwidth&lt;BR /&gt;&lt;BR /&gt;if you still want to go with this deployment type better you got T300 which will meet ur needs.&lt;BR /&gt;&lt;BR /&gt;As far as limit on no's of MESH AP connecting to Root AP, there is no such restriction limit however it is highly recommended that hops shall be up to 3 for better and reliable performance.&lt;BR /&gt;&lt;BR /&gt;I think T300 will NOT mesh with ZF7372 as T300 is a 2*2 ac product whereas ZF7372 is a 2*2n product. Ruckus AP's meshes between same radio type.</description>
      <pubDate>Mon, 27 Jul 2015 11:34:08 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29236#M297</guid>
      <dc:creator>monnat_systems</dc:creator>
      <dc:date>2015-07-27T11:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: Wifi solution for gated community</title>
      <link>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29237#M298</link>
      <description>Monnat, so if I go with a T301 and ZD1200 solution, can you advise if the following is feasible?&lt;BR /&gt;&lt;BR /&gt;T300/301n/301s AP's mounted on poles in the gated community with meshed links towards R500 in the homes. What are the design considerations for these meshed links:&lt;BR /&gt;1. How many meshed links can I cater for from a single outdoor AP (T300), is there maximum number or will each link be considered as a client connection then I guess the answer is 500 mesh links...correct? &lt;BR /&gt;2. With this design the R500's will be positioned as a CPE being single hop away from the root AP.&lt;BR /&gt;3. Do we have a preferred partner for client CPE, since the R500 might not be very cost effective for this solution.</description>
      <pubDate>Mon, 27 Jul 2015 14:59:16 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29237#M298</guid>
      <dc:creator>Julian_Daniels</dc:creator>
      <dc:date>2015-07-27T14:59:16Z</dc:date>
    </item>
    <item>
      <title>Re: Wifi solution for gated community</title>
      <link>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29238#M299</link>
      <description>Hi Julian,&lt;BR /&gt;&lt;BR /&gt;Some clarification, it's 500 connection per AP, meaning 250 per radio. &amp;nbsp;MESH is only on the 5 GHz radio, and max number of association count if for non-encrypted station. &amp;nbsp;With a single wlan using AES you can connect 180 station, and MESH uses WPA2-PSK, so in theory the max number of MEHS is 180, but no other client can connect on the 5 GHz radio at that point. &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Monnat Systems is correct, keep the number of hop as low as possible, no more than 3 is recommended and the number of mesh link device as low as possible, consider the limitation that it is a shared medium, the more association the more overhead there is to consider. &amp;nbsp;For example of you associate 180 11ac station you won't get (867 Mbps @ 80 MHz/2(overhead) = 430 Mbps/180 clients) 2.4 Mbps per station, given that all things are equal. &amp;nbsp;If there are variation in client capability, distance, signal strength, etc. &amp;nbsp;Theory and real world deployment do not necessary line up well.&lt;BR /&gt;&lt;BR /&gt;As for MESH between protocol, 11n and 11ac should be able to mesh together. &amp;nbsp;I have an R500 mesh to a 7363 which is mesh to a 7363 root AP.</description>
      <pubDate>Mon, 27 Jul 2015 16:12:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/FlexMaster/Wifi-solution-for-gated-community/m-p/29238#M299</guid>
      <dc:creator>sid_sok</dc:creator>
      <dc:date>2015-07-27T16:12:15Z</dc:date>
    </item>
  </channel>
</rss>

