<?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: Bypass Guest Authentification for specified URLs/Hosts in Community and Online Support Services</title>
    <link>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9740#M316</link>
    <description>You have already mentioned the best solution, HotSpot, and walled garden entries.
&lt;BR /&gt;&lt;BR /&gt;
Guest Access is designed with inherent client isolation purpose built-in.  No one
&lt;BR /&gt;
gets Network access beyond ARP/DHCP/DNS, until they are Authenticated.</description>
    <pubDate>Wed, 22 Oct 2014 16:37:21 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2014-10-22T16:37:21Z</dc:date>
    <item>
      <title>Bypass Guest Authentification for specified URLs/Hosts</title>
      <link>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9739#M315</link>
      <description>I am searching for a way to allow unauthentificated clients in a Guest-WLAN to reach specified IPs.
&lt;BR /&gt;&lt;BR /&gt;
E.g.: The map of the campus is directly downloadable for everyone. If the client wants more, authentification is neccessary. 
&lt;BR /&gt;&lt;BR /&gt;
In a hotspot this can be done with the "walled garden" settings.
&lt;BR /&gt;&lt;BR /&gt;
I tried with IP based ACL, but it does not work.
&lt;BR /&gt;&lt;BR /&gt;
Does have anybody an idea about this?
&lt;BR /&gt;&lt;BR /&gt;
Thx
&lt;BR /&gt;&lt;BR /&gt;
Tobias</description>
      <pubDate>Wed, 22 Oct 2014 11:08:05 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9739#M315</guid>
      <dc:creator>tobias_brisach</dc:creator>
      <dc:date>2014-10-22T11:08:05Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass Guest Authentification for specified URLs/Hosts</title>
      <link>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9740#M316</link>
      <description>You have already mentioned the best solution, HotSpot, and walled garden entries.
&lt;BR /&gt;&lt;BR /&gt;
Guest Access is designed with inherent client isolation purpose built-in.  No one
&lt;BR /&gt;
gets Network access beyond ARP/DHCP/DNS, until they are Authenticated.</description>
      <pubDate>Wed, 22 Oct 2014 16:37:21 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9740#M316</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2014-10-22T16:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass Guest Authentification for specified URLs/Hosts</title>
      <link>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9741#M317</link>
      <description>But what I think the OP is saying, isn't hotspot functionality broken in 9.8?</description>
      <pubDate>Wed, 22 Oct 2014 17:13:37 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9741#M317</guid>
      <dc:creator>lonnie_3404113</dc:creator>
      <dc:date>2014-10-22T17:13:37Z</dc:date>
    </item>
    <item>
      <title>Re: Bypass Guest Authentification for specified URLs/Hosts</title>
      <link>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9742#M318</link>
      <description>So in the Guest-WLAN with all the nice built-in features, I do have no chance?
&lt;BR /&gt;&lt;BR /&gt;
Why there is a ACL to be configured? 
&lt;BR /&gt;&lt;BR /&gt;
&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c412135b77e24794b089_2ff7bd4a4a8e7512b3d369824da15a97_RuckusGuestACL_inline-507c5b1e-f481-429f-902b-f91515c97ffe-218859130.png1414077118"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/461iFD68937140FBBC74/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c412135b77e24794b089_2ff7bd4a4a8e7512b3d369824da15a97_RuckusGuestACL_inline-507c5b1e-f481-429f-902b-f91515c97ffe-218859130.png1414077118" alt="Image_ images_messages_5f91c412135b77e24794b089_2ff7bd4a4a8e7512b3d369824da15a97_RuckusGuestACL_inline-507c5b1e-f481-429f-902b-f91515c97ffe-218859130.png1414077118" /&gt;&lt;/span&gt; &lt;BR /&gt;&lt;BR /&gt;
If I create a new one (e.g. LOCAL-LAN) DHCP and DNS is already preconfigured.</description>
      <pubDate>Thu, 23 Oct 2014 15:14:43 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Community-and-Online-Support/Bypass-Guest-Authentification-for-specified-URLs-Hosts/m-p/9742#M318</guid>
      <dc:creator>tobias_brisach</dc:creator>
      <dc:date>2014-10-23T15:14:43Z</dc:date>
    </item>
  </channel>
</rss>

