<?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: Is this a valid acl in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946805#M917633</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If all the connections are originated from a 192.168.5.x address AND the device you are on is a stateful firewall you do not need to explicitily allow the return traffic back in with an acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Jun 2008 15:37:23 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2008-06-27T15:37:23Z</dc:date>
    <item>
      <title>Is this a valid acl</title>
      <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946799#M917622</link>
      <description>&lt;P&gt;Is this a valid ACL?&lt;/P&gt;&lt;P&gt;access-list OUTSIDE_access_in extended permit tcp host 160.83.89.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I want to allow this address incoming to any internal address?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 13:05:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946799#M917622</guid>
      <dc:creator>ericluoma</dc:creator>
      <dc:date>2019-03-11T13:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: Is this a valid acl</title>
      <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946800#M917626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe no need for keyword host as u permit the /24 subnet and make sure u apply that ACL inbound on the outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Belal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2008 16:50:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946800#M917626</guid>
      <dc:creator>balsheikh</dc:creator>
      <dc:date>2008-06-26T16:50:42Z</dc:date>
    </item>
    <item>
      <title>Re: Is this a valid acl</title>
      <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946801#M917629</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you say this address 160.83.89.0 do you mean the network in which case as previous poster said remove the "host" keyword.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it is just a particular host then remove the 255.255.255.0  portion of your access-list. BUT 160.83.89.0 cannot be used as a host address, so it's not entirely clear what you are trying to do.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2008 20:40:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946801#M917629</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-06-26T20:40:58Z</dc:date>
    </item>
    <item>
      <title>Re: Is this a valid acl</title>
      <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946802#M917630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to let in any address from that 160.83.89.0 subnet into my outside interface.  Is that possible to do or do I have to get exact IP's of individual PC's in that network range?  When it is requested from any of my internal IP's.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2008 11:39:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946802#M917630</guid>
      <dc:creator>ericluoma</dc:creator>
      <dc:date>2008-06-27T11:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Is this a valid acl</title>
      <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946803#M917631</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No you can use the subnet address if you want. In that case just remove the "host" keyword from your acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is a rather open rule though. You are saying any host on the 160.83.89.0/24 subnet can access any server on any tcp port. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also you wrote &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"When it is requested from any of my internal IP's."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this is a stateful firewall you are on then if the connection originated from one of your internal IP's to a host on the 160.83.89.0/24 subnet you don't need the acl rule because the traffic will automatically be let back in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if the connection is initiated from the 160.83.89.0/24 network or this is not a stateful firewall you do need the acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2008 15:27:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946803#M917631</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-06-27T15:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: Is this a valid acl</title>
      <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946804#M917632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My inside address is a 192.168.5.0 setup, so the traffic would be originating there.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2008 15:30:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946804#M917632</guid>
      <dc:creator>ericluoma</dc:creator>
      <dc:date>2008-06-27T15:30:17Z</dc:date>
    </item>
    <item>
      <title>Re: Is this a valid acl</title>
      <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946805#M917633</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If all the connections are originated from a 192.168.5.x address AND the device you are on is a stateful firewall you do not need to explicitily allow the return traffic back in with an acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2008 15:37:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946805#M917633</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2008-06-27T15:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: Is this a valid acl</title>
      <link>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946806#M917634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2008 15:39:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/is-this-a-valid-acl/m-p/946806#M917634</guid>
      <dc:creator>ericluoma</dc:creator>
      <dc:date>2008-06-27T15:39:20Z</dc:date>
    </item>
  </channel>
</rss>

