<?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: Simple PIX question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177721#M589330</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to clarify the concept on this -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA allows traffic from inside to outside by default.  But, when you apply the ACL on the inside interface and then behavior is just like router ACL that is there is an explicit deny at the end of the ACL.  Thats the reason, permit is doing the job for you.  There is no issues with 6.2.2 and above with ACL.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps !  Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mynul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Sep 2003 22:14:37 GMT</pubDate>
    <dc:creator>mhoda</dc:creator>
    <dc:date>2003-09-26T22:14:37Z</dc:date>
    <item>
      <title>Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177714#M589318</link>
      <description>&lt;P&gt;I'm a PIX newbie, but I am trying to block 2 people from surfing the web.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are the commands I tried:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 105 deny tcp host &amp;lt;ip&amp;gt; any eq www&lt;/P&gt;&lt;P&gt;access-list 105 deny tcp host &amp;lt;ip&amp;gt; any eq www&lt;/P&gt;&lt;P&gt;access-group 105 in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After doing so, no one could surf the net.  What stupid mistake am I making?  Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:00:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177714#M589318</guid>
      <dc:creator>abruso</dc:creator>
      <dc:date>2020-02-21T07:00:39Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177715#M589320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sorry for the dup&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2003 20:35:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177715#M589320</guid>
      <dc:creator>bmuha</dc:creator>
      <dc:date>2003-09-25T20:35:50Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177716#M589322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;try something like this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;outbound &lt;A number=""&gt; deny 10.xxx.xxx.xxx 255.255.255.255 80 tcp&lt;/A&gt;&lt;/P&gt;&lt;P&gt;apply (if-name) &lt;THE num="" used="" above=""&gt; outgoing_dest&lt;/THE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--Brian &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2003 20:38:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177716#M589322</guid>
      <dc:creator>bmuha</dc:creator>
      <dc:date>2003-09-25T20:38:44Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177717#M589324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No one can surf the net because it&amp;#146;s an implicit entry at the end of your access-list which deny all traffic &amp;#147;deny ip any any&amp;#148; this is a standard behaviour for all access-list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After denying traffic for certain host add an entry which allows traffic for the rest of the hosts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 105 deny tcp host &lt;IP&gt; any eq www &lt;/IP&gt;&lt;/P&gt;&lt;P&gt;access-list 105 deny tcp host &lt;IP&gt; any eq www &lt;/IP&gt;&lt;/P&gt;&lt;P&gt;access-list 105 permit ip &lt;YOUR network="" and="" mask=""&gt; any&lt;/YOUR&gt;&lt;/P&gt;&lt;P&gt;access-group 105 in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- Bjorn&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2003 20:48:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177717#M589324</guid>
      <dc:creator>bjandersson</dc:creator>
      <dc:date>2003-09-25T20:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177718#M589326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well the outbound commands didn't work, but the access-list 105 permit statement did the trick.  I knew I had to do that on routers, but for some reason I thought the PIX didn't need the permit statement at the end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Sep 2003 21:52:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177718#M589326</guid>
      <dc:creator>abruso</dc:creator>
      <dc:date>2003-09-25T21:52:21Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177719#M589328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Abruso,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally, you wold not have to have a permit statement when inside users are initiating sessions to the outside, that is, if your securitylevels are configured correctly (default they are correct).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen some strange behaviour on version 6.2.2 and higher, where the PIX does seem to need the permit statement. But I think this is an error. As you can read on CCO about the ASA it normally should let them through when travveling from inside to outside, because if it sees no matchng rule it would apply the implicit rule. The implicit rule is not alwaays deny any any (as another guy stated in one of the replies), but it is depending on the securitylevels. If travelling from high to low security the implicit rule should be permit an any (if no other rule matches)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps in understanding.&lt;/P&gt;&lt;P&gt;Leo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2003 15:19:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177719#M589328</guid>
      <dc:creator>l.mourits</dc:creator>
      <dc:date>2003-09-26T15:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177720#M589329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's what I thought.  The security levels are set up correctly on the interfaces.  Inside is 100 and Outside is 0.  I'm not really sure why the permit statement was needed.  Oh well, as long as it works :).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2003 16:20:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177720#M589329</guid>
      <dc:creator>abruso</dc:creator>
      <dc:date>2003-09-26T16:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177721#M589330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to clarify the concept on this -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA allows traffic from inside to outside by default.  But, when you apply the ACL on the inside interface and then behavior is just like router ACL that is there is an explicit deny at the end of the ACL.  Thats the reason, permit is doing the job for you.  There is no issues with 6.2.2 and above with ACL.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps !  Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mynul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2003 22:14:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177721#M589330</guid>
      <dc:creator>mhoda</dc:creator>
      <dc:date>2003-09-26T22:14:37Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177722#M589331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hate to admit, but I have to agree with Mynul. If an ACL is applied, it does indeed adds an implicit "deny any any". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry for providing you with incorrect information. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only is no ACL is applied the default behaviour is depending on securitylevels, and all traffic from inside to outside would be permitted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Leo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2003 07:09:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/177722#M589331</guid>
      <dc:creator>l.mourits</dc:creator>
      <dc:date>2003-09-29T07:09:27Z</dc:date>
    </item>
  </channel>
</rss>

