<?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: RDD second interface in RUCKUS Diagnostics Dashboard (RDD)</title>
    <link>https://community.ruckuswireless.com/t5/RUCKUS-Diagnostics-Dashboard-RDD/RDD-second-interface/m-p/32088#M91</link>
    <description>Hi Pavel,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;The RDD VM does not have that capability at this time. However, this could probably be handled outside the VM at the network layer.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Best Regards,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Aaron&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
    <pubDate>Fri, 26 Apr 2019 21:20:17 GMT</pubDate>
    <dc:creator>aaron_english_a</dc:creator>
    <dc:date>2019-04-26T21:20:17Z</dc:date>
    <item>
      <title>RDD second interface</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Diagnostics-Dashboard-RDD/RDD-second-interface/m-p/32087#M90</link>
      <description>Hi there,&lt;BR /&gt;Is it possible to add second interface for RDD? First interface for the Internet connection and second one for controller communication.&lt;BR /&gt;Or add custome routes?&lt;BR /&gt;&lt;BR /&gt;BR,&lt;BR /&gt;Pavel</description>
      <pubDate>Thu, 25 Apr 2019 15:55:51 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Diagnostics-Dashboard-RDD/RDD-second-interface/m-p/32087#M90</guid>
      <dc:creator>pavel_semenisc1</dc:creator>
      <dc:date>2019-04-25T15:55:51Z</dc:date>
    </item>
    <item>
      <title>Re: RDD second interface</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Diagnostics-Dashboard-RDD/RDD-second-interface/m-p/32088#M91</link>
      <description>Hi Pavel,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;The RDD VM does not have that capability at this time. However, this could probably be handled outside the VM at the network layer.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Best Regards,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Aaron&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Fri, 26 Apr 2019 21:20:17 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Diagnostics-Dashboard-RDD/RDD-second-interface/m-p/32088#M91</guid>
      <dc:creator>aaron_english_a</dc:creator>
      <dc:date>2019-04-26T21:20:17Z</dc:date>
    </item>
    <item>
      <title>Re: RDD second interface</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Diagnostics-Dashboard-RDD/RDD-second-interface/m-p/32089#M92</link>
      <description>Hi Aaron,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Yep, it's possible. But in our case (requirements of security department) we should use different VRF for Internet access and equipment management.&lt;BR /&gt;&lt;BR /&gt;Kind Regards,&lt;BR /&gt;Pavel</description>
      <pubDate>Mon, 29 Apr 2019 06:52:48 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Diagnostics-Dashboard-RDD/RDD-second-interface/m-p/32089#M92</guid>
      <dc:creator>pavel_semenisc1</dc:creator>
      <dc:date>2019-04-29T06:52:48Z</dc:date>
    </item>
  </channel>
</rss>

