<?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: Trying to connect Ubiquity M2 client radios to a Ruckus R600 in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31888#M8959</link>
    <description>Hi Scott,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Did you get this resolved?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I've previously used UBNT client devices (NanoBeam M5) with Ruckus APs and observed some anomolies.&amp;nbsp; The main one being DHCP traffic couldn't traverse the link, however if a client was given a static IP then all worked as expected.&amp;nbsp; Have you tried this?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I resolved the issue by enabling Tunnelling on a local ZD. Alternatively I did have some success with changing the config of the UBNT device to be a WDS client but this did result in the UBNT device not being available for remote management on the Ruckus side of the network.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I hope that helps,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Darrel.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
    <pubDate>Mon, 18 Mar 2019 11:40:59 GMT</pubDate>
    <dc:creator>DarrelRhodes</dc:creator>
    <dc:date>2019-03-18T11:40:59Z</dc:date>
    <item>
      <title>Trying to connect Ubiquity M2 client radios to a Ruckus R600</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31887#M8958</link>
      <description>Trying to connect Ubiquity M2 client radios to a Ruckus R600. The UBNT radios connect just fine but will not pass traffic. I can get into the radio interface once the client radio connects but nothing will pass through the lan side. So I put back my unifi aps and then the client radios begin to pass traffic again. Any thoughts on this or any ideas of what I could change on the Ruckus aps to get them to be able to use UBNT client client radios?&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Sat, 16 Mar 2019 20:16:07 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31887#M8958</guid>
      <dc:creator>scott_boucher_b</dc:creator>
      <dc:date>2019-03-16T20:16:07Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to connect Ubiquity M2 client radios to a Ruckus R600</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31888#M8959</link>
      <description>Hi Scott,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Did you get this resolved?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I've previously used UBNT client devices (NanoBeam M5) with Ruckus APs and observed some anomolies.&amp;nbsp; The main one being DHCP traffic couldn't traverse the link, however if a client was given a static IP then all worked as expected.&amp;nbsp; Have you tried this?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I resolved the issue by enabling Tunnelling on a local ZD. Alternatively I did have some success with changing the config of the UBNT device to be a WDS client but this did result in the UBNT device not being available for remote management on the Ruckus side of the network.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I hope that helps,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Darrel.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Mon, 18 Mar 2019 11:40:59 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31888#M8959</guid>
      <dc:creator>DarrelRhodes</dc:creator>
      <dc:date>2019-03-18T11:40:59Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to connect Ubiquity M2 client radios to a Ruckus R600</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31889#M8960</link>
      <description>See KBA-3332: Ruckus WDS with third party bridges.&amp;nbsp; &lt;A href="https://support.ruckuswireless.com/articles/000003332" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/articles/000003332"&gt;https://support.ruckuswireless.com/articles/000003332&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;From ZD CLI: remote_ap_cli –A “set qos directedDHCP disable”</description>
      <pubDate>Mon, 18 Mar 2019 23:11:48 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31889#M8960</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2019-03-18T23:11:48Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to connect Ubiquity M2 client radios to a Ruckus R600</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31890#M8961</link>
      <description>This was my thought too. Basically any time you have a wireless client on a Ruckus network that's acting as a bridge for multiple clients behind it, you probably want to turn off directed DHCP. Other examples include virtualization systems like VMWare/Parallels if you use the "bridge to wifi" feature to make guests appear on LAN.</description>
      <pubDate>Tue, 19 Mar 2019 17:23:51 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Trying-to-connect-Ubiquity-M2-client-radios-to-a-Ruckus-R600/m-p/31890#M8961</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2019-03-19T17:23:51Z</dc:date>
    </item>
  </channel>
</rss>

