<?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: Hot Spot Walled Garden DNS Entries in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8458#M1617</link>
    <description>I have this same problem.  Does Ruckus have a fix for this ?</description>
    <pubDate>Mon, 26 Aug 2013 11:45:28 GMT</pubDate>
    <dc:creator>dennis_arafiles</dc:creator>
    <dc:date>2013-08-26T11:45:28Z</dc:date>
    <item>
      <title>Hot Spot Walled Garden DNS Entries</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8457#M1616</link>
      <description>I'm having trouble with the the hot spot services walled garden. If I white list a domain by its DNS entry (e.g. &lt;A href="http://www.apple.com" rel="nofollow"&gt;www.apple.com&lt;/A&gt; or apple.com) unauthenticated traffic still get's blocked to those URLs. 
&lt;BR /&gt;&lt;BR /&gt;
I'd like to white list Apple, because when an iOS device joins an open Wi-Fi network it checks for captive portals by opening &lt;A href="http://www.apple.com" rel="nofollow"&gt;www.apple.com&lt;/A&gt; in a pop up window. If the portal intercepts the request, then the portal's login page will display. A user must authenticate with the network at this step. You cannot close this popup and still be connected to the network. 
&lt;BR /&gt;&lt;BR /&gt;
This pop up workflow happens to break the way my javascript login works, so I need to prevent it by allowing traffic through to apple for unauthenticated users.</description>
      <pubDate>Mon, 29 Jul 2013 17:11:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8457#M1616</guid>
      <dc:creator>rotoole</dc:creator>
      <dc:date>2013-07-29T17:11:20Z</dc:date>
    </item>
    <item>
      <title>Re: Hot Spot Walled Garden DNS Entries</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8458#M1617</link>
      <description>I have this same problem.  Does Ruckus have a fix for this ?</description>
      <pubDate>Mon, 26 Aug 2013 11:45:28 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8458#M1617</guid>
      <dc:creator>dennis_arafiles</dc:creator>
      <dc:date>2013-08-26T11:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: Hot Spot Walled Garden DNS Entries</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8459#M1618</link>
      <description>Nope.
&lt;BR /&gt;&lt;BR /&gt;
The Ruckus captive portal will only do a one time IP lookup of any DNS entry in the white list. If you are trying to white list a cloud based web service that could come from many different IPs, then you are out of luck. It was simply not designed to handle that case correctly. 
&lt;BR /&gt;&lt;BR /&gt;
I got it working by using Squid to do the captive portal. You can write squid rules to handle FQDN's, respond with 302's, manipulate IP tables, and check authorization. It's non trivial though.
&lt;BR /&gt;&lt;BR /&gt;
Hope that helps.</description>
      <pubDate>Mon, 26 Aug 2013 17:02:42 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8459#M1618</guid>
      <dc:creator>rotoole</dc:creator>
      <dc:date>2013-08-26T17:02:42Z</dc:date>
    </item>
    <item>
      <title>Re: Hot Spot Walled Garden DNS Entries</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8460#M1619</link>
      <description>We're experiencing a similar problem when trying to authenticate a user via the Facebook API.  @rotoole, might you share with us more details on your work-around.  We've dabbled in several of the concepts you've mentioned but still unsuccessful.  Thanks</description>
      <pubDate>Tue, 27 May 2014 02:05:28 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8460#M1619</guid>
      <dc:creator>bc_chamberlin</dc:creator>
      <dc:date>2014-05-27T02:05:28Z</dc:date>
    </item>
    <item>
      <title>Re: Hot Spot Walled Garden DNS Entries</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8461#M1620</link>
      <description>BC, my company makes a solution, if you are interested. There are several approaches that will work either HTTP proxy based or RADIUS based. There are some other companies that also provide out of the box solutions. Just depends what you're looking to accomplish. Happy to chat, if you like: &lt;A href="mailto:ryan@stad.io" rel="nofollow"&gt;ryan@stad.io&lt;/A&gt;</description>
      <pubDate>Tue, 27 May 2014 15:58:54 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hot-Spot-Walled-Garden-DNS-Entries/m-p/8461#M1620</guid>
      <dc:creator>rotoole</dc:creator>
      <dc:date>2014-05-27T15:58:54Z</dc:date>
    </item>
  </channel>
</rss>

