<?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: Guest Access Exceptions in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997319#M127890</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, it was the order and I got it working!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the ideas and help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Jul 2008 14:41:21 GMT</pubDate>
    <dc:creator>svillardi</dc:creator>
    <dc:date>2008-07-07T14:41:21Z</dc:date>
    <item>
      <title>Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997313#M127881</link>
      <description>&lt;P&gt;Finally got Guest Access to work but need to set up exceptions.  Users get DHCP and DNS from local server and then are allow http and https access to the internet only.  Local http / https is blocked by a rule to all on an internal Class B subnet.  Rules look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;permit 0.0.0.0 any udp dhcp client in&lt;/P&gt;&lt;P&gt;permit any 0.0.0.0. udp dhcp server out&lt;/P&gt;&lt;P&gt;permit range any udp dns in&lt;/P&gt;&lt;P&gt;permit any range udp dns out&lt;/P&gt;&lt;P&gt;deny range range tcp http in&lt;/P&gt;&lt;P&gt;deny range range tcp http out&lt;/P&gt;&lt;P&gt;deny range range tcp https in&lt;/P&gt;&lt;P&gt;deny range range tcp https out&lt;/P&gt;&lt;P&gt;allow range any tcp http in&lt;/P&gt;&lt;P&gt;allow any range tcp http out&lt;/P&gt;&lt;P&gt;allow range any tcp https in&lt;/P&gt;&lt;P&gt;allow any range tcp https out &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem: Users may want to get to our websites that resolve differently locally.  Global dns might point &lt;A class="jive-link-custom" href="http://www.website.com" target="_blank"&gt;www.website.com&lt;/A&gt; to 100.100.100.100, but internally &lt;A class="jive-link-custom" href="http://www.website.com" target="_blank"&gt;www.website.com&lt;/A&gt; points to 10.10.10.10.  This is a Class C subnet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I created a permit rule for the local sites, but it's not working.  I think the order is the problem, but I don't know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be really appreciated. Thank you kindly.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 23:07:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997313#M127881</guid>
      <dc:creator>svillardi</dc:creator>
      <dc:date>2021-07-03T23:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997314#M127882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Yes it could be the order, but it is difficult to say without the real ranges here.&lt;/P&gt;&lt;P&gt;Try to review your ACL, if you deny something that is allowed afterwards, it will be blocked. So if you say:&lt;/P&gt;&lt;P&gt;deny 10.0.0.0 tcp http in&lt;/P&gt;&lt;P&gt;allow 10.1.0.0 tcp http in, it will be blocked... the first rule to match the packet you receive is applied, and the system stops there, without checking the other lines...&lt;/P&gt;&lt;P&gt;hth&lt;/P&gt;&lt;P&gt;J&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jul 2008 09:06:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997314#M127882</guid>
      <dc:creator>jeromehenry_2</dc:creator>
      <dc:date>2008-07-04T09:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997315#M127883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Aside from your ACL problems, most people will point Guest Networks towards a public DNS server, not a private / internal one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Two reasons for this;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First, it helps prevent guests from getting information about your internal network&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Second, it ensures they go 'out' and 'back in' again - ie, public DNS will only ever return public IP addresses, therefore ensuring Guest Users don't encounter the problem you describe.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2008 10:22:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997315#M127883</guid>
      <dc:creator>Richard Atkin</dc:creator>
      <dc:date>2008-07-07T10:22:04Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997316#M127885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Where can I get a list of trustworthy public DNS sites?  I don't want to pick the first search response of Google.  &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2008 11:24:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997316#M127885</guid>
      <dc:creator>svillardi</dc:creator>
      <dc:date>2008-07-07T11:24:31Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997317#M127886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Using the ones provided by your ISP will normally provide good results...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2008 12:41:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997317#M127886</guid>
      <dc:creator>Richard Atkin</dc:creator>
      <dc:date>2008-07-07T12:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997318#M127888</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your help.  We get our DNS from our parent company and this is out of spec--I can't ask them who their DNS provider is.  Any other suggestion?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2008 14:13:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997318#M127888</guid>
      <dc:creator>svillardi</dc:creator>
      <dc:date>2008-07-07T14:13:43Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997319#M127890</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, it was the order and I got it working!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the ideas and help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2008 14:41:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997319#M127890</guid>
      <dc:creator>svillardi</dc:creator>
      <dc:date>2008-07-07T14:41:21Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997320#M127891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Excellent, glad to help!&lt;/P&gt;&lt;P&gt;And a 5 for you to give us our feedback, this thread might be useful to others!&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2008 19:32:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997320#M127891</guid>
      <dc:creator>jeromehenry_2</dc:creator>
      <dc:date>2008-07-07T19:32:53Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Access Exceptions</title>
      <link>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997321#M127892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We had the same issue. We are using the FWSM. Our servers have an internal IP address and sit in a DMZ of the firewall as do the wireless users. Along with the internal ACL:'s we added a wireless view on our external DNS which also resides on another DMZ within the FWSM. This view takes just the subnet of those wireless users and points them to a different ip for specific name resolutions. This way I give the wireless users web access only to the internal address of the web server  keeping them internal to the FWSM. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jul 2008 13:11:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-access-exceptions/m-p/997321#M127892</guid>
      <dc:creator>michael.lussier</dc:creator>
      <dc:date>2008-07-08T13:11:03Z</dc:date>
    </item>
  </channel>
</rss>

