<?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: SmartZone with NAT IP (without internal IP- in SmartZone and Virtual SmartZone</title>
    <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59457#M4437</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/125"&gt;@lienmonden&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Could you please confirm the vSZ version running? Also is the vSZ deployed on Cloud platform like AWS?&lt;BR /&gt;&lt;BR /&gt;We had a similar issue in the past where the ICX was receiving the private IP of the controller and has been fixed so that the ICX can only get the Public IP of the controller.&lt;BR /&gt;Please confirm the above information so that I can confirm the fix.&lt;/P&gt;</description>
    <pubDate>Thu, 25 May 2023 05:14:20 GMT</pubDate>
    <dc:creator>sanjay_kumar</dc:creator>
    <dc:date>2023-05-25T05:14:20Z</dc:date>
    <item>
      <title>SmartZone with NAT IP (without internal IP-</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59372#M4433</link>
      <description>&lt;P&gt;Hi Pack,&lt;/P&gt;&lt;P&gt;We have a local SmartZone (vSZ-H) that we host for our end customers. We use a control NAT IP for the end customers, so they can connect to our SmartZone. Once their AP's are connected, they also receive our internal IP as well on the AP/switch ("get scg ip" shows the internal IP and the NAT IP).&lt;/P&gt;&lt;P&gt;Is it possible to hide the internal IP? So when the AP/switch is connected, they&amp;nbsp;&lt;STRONG&gt;don't&amp;nbsp;&lt;/STRONG&gt;receive the internal IP - only the NAT IP which they use to make their connection.&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 09:01:00 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59372#M4433</guid>
      <dc:creator>lienmonden</dc:creator>
      <dc:date>2023-05-24T09:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: SmartZone with NAT IP (without internal IP-</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59457#M4437</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/125"&gt;@lienmonden&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Could you please confirm the vSZ version running? Also is the vSZ deployed on Cloud platform like AWS?&lt;BR /&gt;&lt;BR /&gt;We had a similar issue in the past where the ICX was receiving the private IP of the controller and has been fixed so that the ICX can only get the Public IP of the controller.&lt;BR /&gt;Please confirm the above information so that I can confirm the fix.&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2023 05:14:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59457#M4437</guid>
      <dc:creator>sanjay_kumar</dc:creator>
      <dc:date>2023-05-25T05:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: SmartZone with NAT IP (without internal IP-</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59465#M4438</link>
      <description>&lt;P&gt;Version = 6.1.1.0.959&lt;/P&gt;&lt;P&gt;vSZ is deployed in VMWare (ESXi), so no Cloud platform&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2023 07:42:56 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59465#M4438</guid>
      <dc:creator>lienmonden</dc:creator>
      <dc:date>2023-05-25T07:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: SmartZone with NAT IP (without internal IP-</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59967#M4458</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/125"&gt;@lienmonden&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;You would get the internal IP displayed in the output of "get scg" command, if you don't want that to be seen, the other way is configuring the NAT on the firewall instead vSZ, provided you allow all the ports that needs to be open for AP/Switch/vSZ communication on the firewall.&lt;/P&gt;&lt;P&gt;May the Force be with You!!!&lt;/P&gt;&lt;P&gt;Abilash PR&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jun 2023 11:30:09 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/59967#M4458</guid>
      <dc:creator>abilashpr</dc:creator>
      <dc:date>2023-06-03T11:30:09Z</dc:date>
    </item>
    <item>
      <title>Re: SmartZone with NAT IP (without internal IP-</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/60596#M4479</link>
      <description>&lt;P&gt;Hi Abilash,&lt;/P&gt;&lt;P&gt;We use NAT on the firewall like you say + NAT IP is configured on the SmartZone. Can we remove the NAT IP setting on the SmartZone?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 06:25:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/60596#M4479</guid>
      <dc:creator>lienmonden</dc:creator>
      <dc:date>2023-06-15T06:25:15Z</dc:date>
    </item>
    <item>
      <title>Re: SmartZone with NAT IP (without internal IP-</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/60598#M4480</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/125"&gt;@lienmonden&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since controller is behind NAT, we have to configure&amp;nbsp;Control NAT IP.&amp;nbsp;Please get output of "show interface" from the controller CLI and "get scg" from AP CLI.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 07:38:40 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/60598#M4480</guid>
      <dc:creator>Kiran_Raval</dc:creator>
      <dc:date>2023-06-15T07:38:40Z</dc:date>
    </item>
    <item>
      <title>Re: SmartZone with NAT IP (without internal IP-</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/60770#M4484</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/125"&gt;@lienmonden&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;There are two ways of deploying this, Lets assume you have Site A and Site B.&lt;/P&gt;&lt;P&gt;Type 1.&lt;/P&gt;&lt;P&gt;Run Site to Site VPN between the two Sites and NAT internal IP of SZ's and AP's so that their subnets are reachable across the Sites, Firewall Rules has to be configured accordingly.&lt;/P&gt;&lt;P&gt;Type - 2&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; Nat SZ/vSZ Internal IP on the Site 'A' Firewall's Public IP so that it could be reached on the Internet, you have to open ports for AP-Controller communication mentioned in Admin Guide.&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Now, you should be able to access vSZ using the Public IP A.A.A.A, on the Site 'B' Firewall you have to open ports for AP-Controller Communication mentioned in Admin Guide.&lt;/P&gt;&lt;P&gt;3. For this to work seamlessly you should configure rules on both Site's Firewall so that there are no reachability issues.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="abilashpr_0-1686865587911.png" style="width: 400px;"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/6932i2874696E24C9CB71/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="abilashpr_0-1686865587911.png" alt="abilashpr_0-1686865587911.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;In both these methods you don't have to configure NAT IP on the SZ/VSZ. If you have AP's deployed in the same site as vSZ/SZ you have to direct the AP to reach SZ/VSZ internal IP.&lt;/P&gt;&lt;P&gt;When Onboarding each site you have to configure rules on both Firewall's so there aren't any connectivity issues between each site.&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is lot of work that needs to be done on the firewall, just to hide your vSZ's internal IP on the AP and you should watch the latency too so that AP's don't lose any heart beats.&lt;/P&gt;&lt;P&gt;In your setup please check the connectivity of the vSZ from remote site by removing the NAT IP on the vSZ, if you don't set correct configurations on the firewall you may have connectivity issues.&lt;/P&gt;&lt;P&gt;I currently use Type 1 as I have few APs (less than 100) on the remote Sites.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps!!!&lt;/P&gt;&lt;P&gt;May the One Force be with You!!!&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Abilash&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 22:19:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/SmartZone-with-NAT-IP-without-internal-IP/m-p/60770#M4484</guid>
      <dc:creator>abilashpr</dc:creator>
      <dc:date>2023-06-15T22:19:30Z</dc:date>
    </item>
  </channel>
</rss>

