<?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 Google Expedition R700 with SmartZone 100 in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25716#M7005</link>
    <description>&lt;P&gt;We are running 3 SmartZone 100 Controllers&lt;/P&gt;&lt;P&gt;We currently have 855 APs, all model &lt;/P&gt;&lt;P&gt;Firmware 3.2.1.0.245&lt;/P&gt;&lt;P&gt;Everything is running very well for our school district.&amp;nbsp; We are now looking into using Google Expedition.&amp;nbsp; The WLAN that the devices connect to:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Tunnels back to controller&lt;/LI&gt;&lt;LI&gt;Client Isolation is turned off (very important)&lt;/LI&gt;&lt;LI&gt;Currently Open, but we've tried as PSK&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Little bit about Google Expedition.&amp;nbsp; The app is based on MDNS. (Yes another multicast wireless question).&amp;nbsp; A user will start the app on one device and select to be the leader.&amp;nbsp; The device then communicates out using MDNS.&amp;nbsp; Then students start up their app on their device and select to be a follower. They start communicating out with MDNS to find and communicate with the leader.&lt;/P&gt;&lt;P&gt;Problem:&lt;/P&gt;&lt;P&gt;The devices work very when they all connect to the WLAN on the same AP.&amp;nbsp; However when a device connects to the same&amp;nbsp;WLAN on a different AP then they&amp;nbsp;can't partake in the expedition.&amp;nbsp; They can't see the leader and the leader can't see them. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;This forum post is 3 years old.&amp;nbsp; Is this still the expected solution for users to try?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://forums.ruckuswireless.com/ruckuswireless/topics/multicast_traffic_originating_on_one_ap_does_not_reliably_reach_a_client_on_another_ap_on_the_same_wlan" rel="nofollow" title="Link: https://forums.ruckuswireless.com/ruckuswireless/topics/multicast_traffic_originating_on_one_ap_does_not_reliably_reach_a_client_on_another_ap_on_the_same_wlan"&gt;https://forums.ruckuswireless.com/ruckuswireless/topics/multicast_traffic_originating_on_one_ap_does...&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;If&amp;nbsp;we do turn off directed-multicast as what the above link suggests:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;If we do this does that mean that all Multicast traffic on the vlan will be sent out to all the APs&lt;/LI&gt;&lt;LI&gt;If #1 is true, is it possible to setup a filter for what multicast traffic we want&lt;/LI&gt;&lt;LI&gt;If it's a total disaster and we want to revert back to directed-multicast, what commands do we run.&amp;nbsp; (Assuming instead of &lt;B&gt;no qos directed-multicast&lt;/B&gt;﻿ we just type &lt;B&gt;qos directed-multicast&lt;/B&gt;﻿).&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;-B&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Apr 2017 15:44:05 GMT</pubDate>
    <dc:creator>bw447</dc:creator>
    <dc:date>2017-04-05T15:44:05Z</dc:date>
    <item>
      <title>Google Expedition R700 with SmartZone 100</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25716#M7005</link>
      <description>&lt;P&gt;We are running 3 SmartZone 100 Controllers&lt;/P&gt;&lt;P&gt;We currently have 855 APs, all model &lt;/P&gt;&lt;P&gt;Firmware 3.2.1.0.245&lt;/P&gt;&lt;P&gt;Everything is running very well for our school district.&amp;nbsp; We are now looking into using Google Expedition.&amp;nbsp; The WLAN that the devices connect to:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Tunnels back to controller&lt;/LI&gt;&lt;LI&gt;Client Isolation is turned off (very important)&lt;/LI&gt;&lt;LI&gt;Currently Open, but we've tried as PSK&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Little bit about Google Expedition.&amp;nbsp; The app is based on MDNS. (Yes another multicast wireless question).&amp;nbsp; A user will start the app on one device and select to be the leader.&amp;nbsp; The device then communicates out using MDNS.&amp;nbsp; Then students start up their app on their device and select to be a follower. They start communicating out with MDNS to find and communicate with the leader.&lt;/P&gt;&lt;P&gt;Problem:&lt;/P&gt;&lt;P&gt;The devices work very when they all connect to the WLAN on the same AP.&amp;nbsp; However when a device connects to the same&amp;nbsp;WLAN on a different AP then they&amp;nbsp;can't partake in the expedition.&amp;nbsp; They can't see the leader and the leader can't see them. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;This forum post is 3 years old.&amp;nbsp; Is this still the expected solution for users to try?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://forums.ruckuswireless.com/ruckuswireless/topics/multicast_traffic_originating_on_one_ap_does_not_reliably_reach_a_client_on_another_ap_on_the_same_wlan" rel="nofollow" title="Link: https://forums.ruckuswireless.com/ruckuswireless/topics/multicast_traffic_originating_on_one_ap_does_not_reliably_reach_a_client_on_another_ap_on_the_same_wlan"&gt;https://forums.ruckuswireless.com/ruckuswireless/topics/multicast_traffic_originating_on_one_ap_does...&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;If&amp;nbsp;we do turn off directed-multicast as what the above link suggests:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;If we do this does that mean that all Multicast traffic on the vlan will be sent out to all the APs&lt;/LI&gt;&lt;LI&gt;If #1 is true, is it possible to setup a filter for what multicast traffic we want&lt;/LI&gt;&lt;LI&gt;If it's a total disaster and we want to revert back to directed-multicast, what commands do we run.&amp;nbsp; (Assuming instead of &lt;B&gt;no qos directed-multicast&lt;/B&gt;﻿ we just type &lt;B&gt;qos directed-multicast&lt;/B&gt;﻿).&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;-B&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Apr 2017 15:44:05 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25716#M7005</guid>
      <dc:creator>bw447</dc:creator>
      <dc:date>2017-04-05T15:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: Google Expedition R700 with SmartZone 100</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25717#M7006</link>
      <description>Yes, that is our solution for MDNS based applications (including Bonjour), to allow&lt;BR /&gt;you to see other devices that span the VLAN you're on from the AP, to the wired&lt;BR /&gt;network too.&amp;nbsp; We advise schools using Bonjour to limit broadcast domains to &lt;BR /&gt;reduce the overhead created by the multicast on top of normal broadcast traffic.&lt;BR /&gt;That might mean one VLAN for a few classes, etc...&amp;nbsp; You might want to reach &lt;BR /&gt;out to your local VAR or Ruckus SE if this would require much re-design.</description>
      <pubDate>Thu, 06 Apr 2017 18:25:50 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25717#M7006</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-04-06T18:25:50Z</dc:date>
    </item>
    <item>
      <title>Re: Google Expedition R700 with SmartZone 100</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25718#M7007</link>
      <description>&lt;P&gt;@Michael Thanks for the info.&amp;nbsp; We will give this a try.&lt;/P&gt;&lt;P&gt;UPDATE&lt;/P&gt;&lt;P&gt;After opening a ticket and doing more testing the following was found.&lt;/P&gt;&lt;P&gt;(First, the link above was for ZoneDiretor, not SmartZone)&lt;/P&gt;&lt;P&gt;The engineer on the phone help setup the directed multicast setting.&amp;nbsp; After doing a test the app still didn't work.&lt;/P&gt;&lt;P&gt;We then changed the WLAN from being tunneled back to the controller to just dropped off onto a local vlan.&amp;nbsp; Once we did that the app worked as expected.&amp;nbsp; &lt;/P&gt;&lt;P&gt;We also tried it again by dropping onto the local vlan and without the directed multicast setting.&amp;nbsp; This setting worked as well.&lt;/P&gt;&lt;P&gt;It looks like the problem is when a WLAN tunnels back to the controller.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Apr 2017 15:49:45 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25718#M7007</guid>
      <dc:creator>bw447</dc:creator>
      <dc:date>2017-04-07T15:49:45Z</dc:date>
    </item>
    <item>
      <title>Re: Google Expedition R700 with SmartZone 100</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25719#M7008</link>
      <description>Glad to get your update, thanks!&amp;nbsp; &lt;BR /&gt;Don't tunnel your WLANs that need local multicast, got it.</description>
      <pubDate>Tue, 11 Apr 2017 22:18:32 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Google-Expedition-R700-with-SmartZone-100/m-p/25719#M7008</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-04-11T22:18:32Z</dc:date>
    </item>
  </channel>
</rss>

