<?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 Gust access using WCS in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/gust-access-using-wcs/m-p/895895#M128024</link>
    <description>&lt;P&gt;Can someone exactly clarify the mechanisam involved in guest accessing Internet ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How does he ge automatically get the config parameters such as proxy address atc ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 03 Jul 2021 21:55:01 GMT</pubDate>
    <dc:creator>nkariyawasam</dc:creator>
    <dc:date>2021-07-03T21:55:01Z</dc:date>
    <item>
      <title>Gust access using WCS</title>
      <link>https://community.cisco.com/t5/wireless/gust-access-using-wcs/m-p/895895#M128024</link>
      <description>&lt;P&gt;Can someone exactly clarify the mechanisam involved in guest accessing Internet ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How does he ge automatically get the config parameters such as proxy address atc ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 21:55:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/gust-access-using-wcs/m-p/895895#M128024</guid>
      <dc:creator>nkariyawasam</dc:creator>
      <dc:date>2021-07-03T21:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Gust access using WCS</title>
      <link>https://community.cisco.com/t5/wireless/gust-access-using-wcs/m-p/895896#M128025</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"It Depends" to use a quote from Neil Reid. You can configure guest access several ways. The mobility controller anchor methd is one of the most commonly used. This requires you to configure a guest ssid that utilizes a mobility anchor controller that resides outside the firewall. The traffic on this ssid is tunneled to the mobility anchor controller on an EoIP tunnel. Refer to the Mobility Anchor Configuration guide&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/wireless/technology/guest_access/technical/reference/4.1/GAccess_41.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/wireless/technology/guest_access/technical/reference/4.1/GAccess_41.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, this requires a dedicated controller but is the most effective method.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Nov 2007 15:33:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/gust-access-using-wcs/m-p/895896#M128025</guid>
      <dc:creator>dennischolmes</dc:creator>
      <dc:date>2007-11-10T15:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: Gust access using WCS</title>
      <link>https://community.cisco.com/t5/wireless/gust-access-using-wcs/m-p/895897#M128026</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Proxy can be pushed down via dhcp option.  Guest access however will not work if proxy is configured.  Users will not get a login page.... they will have to turn off proxy and then open a browser to get the login page.  Login to the network or hit accept and then the user will have to turn on proxy.  No work around yet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Nov 2007 14:21:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/gust-access-using-wcs/m-p/895897#M128026</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2007-11-12T14:21:55Z</dc:date>
    </item>
  </channel>
</rss>

