<?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 The WLC only does the proxy in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516786#M28721</link>
    <description>&lt;P&gt;The WLC only does the proxy for the Web-auth, after the user has successfully authenticated there is no more proxy. &amp;nbsp;Be careful when setting up web filtering for Web-auth if the web page the station is trying to hit can not be resolved by DNS then the Web-auth page will fail to come up.&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2014 12:25:24 GMT</pubDate>
    <dc:creator>jmeachum</dc:creator>
    <dc:date>2014-06-05T12:25:24Z</dc:date>
    <item>
      <title>Locking down guest wireless network</title>
      <link>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516783#M28718</link>
      <description>&lt;P&gt;I have a Cisco 5508 WLC with a guest network set up on it. The WLAN uses local authentication and grants access through an ASA to the Internet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just found out that the customer now wants to limit where wireless clients can go on the Internet by URL, etc. Since the wireless clients have to use the WLC as a proxy in order to join the network, I am not sure the best way to accomplish this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How is this typically done in a reasonable and economical manner?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 07:57:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516783#M28718</guid>
      <dc:creator>Colin Higgins</dc:creator>
      <dc:date>2021-07-05T07:57:07Z</dc:date>
    </item>
    <item>
      <title>You will need a content</title>
      <link>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516784#M28719</link>
      <description>&lt;P&gt;You will need a content filter. &amp;nbsp;If there is not too many users/bandwidth then you could use a Meraki MX60 ($495 list) or MX80 ($1995) to filter the traffic.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2014 01:54:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516784#M28719</guid>
      <dc:creator>jmeachum</dc:creator>
      <dc:date>2014-06-05T01:54:28Z</dc:date>
    </item>
    <item>
      <title>Since the wireless users have</title>
      <link>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516785#M28720</link>
      <description>&lt;P&gt;Since the wireless users have to use the WLC for a proxy, how would the Meraki filter URLs?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can it do wccp? Some kind of transparent proxy function?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2014 03:32:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516785#M28720</guid>
      <dc:creator>Colin Higgins</dc:creator>
      <dc:date>2014-06-05T03:32:09Z</dc:date>
    </item>
    <item>
      <title>The WLC only does the proxy</title>
      <link>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516786#M28721</link>
      <description>&lt;P&gt;The WLC only does the proxy for the Web-auth, after the user has successfully authenticated there is no more proxy. &amp;nbsp;Be careful when setting up web filtering for Web-auth if the web page the station is trying to hit can not be resolved by DNS then the Web-auth page will fail to come up.&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2014 12:25:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516786#M28721</guid>
      <dc:creator>jmeachum</dc:creator>
      <dc:date>2014-06-05T12:25:24Z</dc:date>
    </item>
    <item>
      <title>Hi,For this case we have</title>
      <link>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516787#M28722</link>
      <description>&lt;P&gt;&lt;SPAN style="font-size:14px;"&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size:14px;"&gt;For this case we have option &amp;nbsp;&lt;SPAN style="color: rgb(0, 0, 0); line-height: normal;"&gt;CPU ACLs&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size:14px;"&gt;&lt;SPAN style="color: rgb(0, 0, 0); line-height: normal;"&gt;this feature were introduced with WLC firmware release 4.0.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size:14px;"&gt;&lt;SPAN style="color: rgb(0, 0, 0); line-height: normal;"&gt;Go through below link for further configuration detail.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size:14px;"&gt;http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wlan-security/71978-acl-wlc.html#cpuacl&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jun 2014 11:06:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/locking-down-guest-wireless-network/m-p/2516787#M28722</guid>
      <dc:creator>abwahid</dc:creator>
      <dc:date>2014-06-10T11:06:13Z</dc:date>
    </item>
  </channel>
</rss>

