<?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 Guest Wireless Internet Firewall Rules in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413900#M28771</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There really&amp;nbsp; isn't one a sample nor best practices for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It all depends on what you are looking to do.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMO, the guest network should only be blocked from reaching to the internal network.&amp;nbsp; Other than that leave it open, but maybe QoS/AVC and mark them as lower priority so they can't utilize a lot of your interwebz bandwidth.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH, &lt;BR /&gt;Steve &lt;BR /&gt; &lt;BR /&gt;------------------------------------------------------------------------------------------------ &lt;BR /&gt;Please remember to rate useful posts, and mark questions as answered&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Jan 2014 15:45:26 GMT</pubDate>
    <dc:creator>Stephen Rodriguez</dc:creator>
    <dc:date>2014-01-07T15:45:26Z</dc:date>
    <item>
      <title>Guest Wireless Internet Firewall Rules</title>
      <link>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413899#M28770</link>
      <description>&lt;P&gt;Good morning - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am hoping to find a sample, guide, best practices, and practical example of a set of Internet firewall rules for wireless guest users. Common current services and applications for tablets (Skype, Apple services, etc) must work and I would also like to identify commonly blocked outbound ports for wireless guest users. The service should have a more open ruleset but still be secure. Even if I could find a good starting point. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks! &lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 06:54:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413899#M28770</guid>
      <dc:creator>John Capobianco</dc:creator>
      <dc:date>2021-07-05T06:54:24Z</dc:date>
    </item>
    <item>
      <title>Guest Wireless Internet Firewall Rules</title>
      <link>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413900#M28771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There really&amp;nbsp; isn't one a sample nor best practices for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It all depends on what you are looking to do.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMO, the guest network should only be blocked from reaching to the internal network.&amp;nbsp; Other than that leave it open, but maybe QoS/AVC and mark them as lower priority so they can't utilize a lot of your interwebz bandwidth.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH, &lt;BR /&gt;Steve &lt;BR /&gt; &lt;BR /&gt;------------------------------------------------------------------------------------------------ &lt;BR /&gt;Please remember to rate useful posts, and mark questions as answered&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2014 15:45:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413900#M28771</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2014-01-07T15:45:26Z</dc:date>
    </item>
    <item>
      <title>Guest Wireless Internet Firewall Rules</title>
      <link>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413901#M28772</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Thank you for the reply. We are using the WLC to rate limit guest bandwidth and are approaching this to have a near-wide-open access to the internet on the guest network. Just trying to see if there are commonly blocked ports or blocked services applied or if we simply use Layer-7 aware / application aware services to block things like Torrents but allow Skype for example. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2014 16:01:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413901#M28772</guid>
      <dc:creator>John Capobianco</dc:creator>
      <dc:date>2014-01-07T16:01:36Z</dc:date>
    </item>
    <item>
      <title>Guest Wireless Internet Firewall Rules</title>
      <link>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413902#M28773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'd stick with Layer 7 aware services.&amp;nbsp; That way you can drop or mark down bandwidth hogs, but still let the users get where they need to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem with FW/ACL is you never know what a user is going to need.&amp;nbsp; I had a customer years ago that had changed the ports her VPN used.&amp;nbsp; If you didn't know what they were, they never would be able to connect.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH, &lt;BR /&gt;Steve &lt;BR /&gt; &lt;BR /&gt;------------------------------------------------------------------------------------------------ &lt;BR /&gt;Please remember to rate useful posts, and mark questions as answered&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2014 16:23:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-wireless-internet-firewall-rules/m-p/2413902#M28773</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2014-01-07T16:23:15Z</dc:date>
    </item>
  </channel>
</rss>

