<?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: ASA block traffic when should be allowed. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-block-traffic-when-should-be-allowed/m-p/3894081#M924852</link>
    <description>&lt;P&gt;Access to ASDM is controlled not by an ACL but by the "http" command.&lt;/P&gt;
&lt;P&gt;Try:&lt;/P&gt;
&lt;P&gt;http 0.0.0.0 0.0.0.0 inside&lt;/P&gt;
&lt;P&gt;(or whatever interface you are trying to access from).&lt;/P&gt;
&lt;P&gt;You can substitute a more specific subnet or even host address for the 0.0.0.0/0 example.&lt;/P&gt;</description>
    <pubDate>Sat, 20 Jul 2019 12:29:22 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2019-07-20T12:29:22Z</dc:date>
    <item>
      <title>ASA block traffic when should be allowed.</title>
      <link>https://community.cisco.com/t5/network-security/asa-block-traffic-when-should-be-allowed/m-p/3892659#M924850</link>
      <description>I'm simply trying to access adsm and when doing show log I see that the traffic is getting block by an ACL. %ASA-3-710003: TCP access denied by ACL from 192.168.1.84/1092 to g0:192.168.1.180/443 %ASA-7-710005: TCP request discarded from 192.168.1.84/1092 to g0:192.168.1.180/443 So I then tried configuring an explicit rule to allow all( any any) to simply to access adsm. The issue still persists. The security-level is set to zero 0 on the interface, I've read that this should matter any more since an acl has been applied to the interface. The firewall rules. access-list OUTBOUND extended permit tcp host 192.168.1.84 host 192.168.1.180 access-list INBOUND extended permit tcp host 192.168.1.180 host 192.168.1.84 I've also tried applying these rules as well. access-list OUTBOUND extended permit tcp any4 any4 access-list INBOUND extended permit tcp any4 any4 access-group OUTBOUND out int g0 access-group INBOUND in int g0</description>
      <pubDate>Fri, 21 Feb 2020 17:19:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-block-traffic-when-should-be-allowed/m-p/3892659#M924850</guid>
      <dc:creator>JKOOP</dc:creator>
      <dc:date>2020-02-21T17:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: ASA block traffic when should be allowed.</title>
      <link>https://community.cisco.com/t5/network-security/asa-block-traffic-when-should-be-allowed/m-p/3894081#M924852</link>
      <description>&lt;P&gt;Access to ASDM is controlled not by an ACL but by the "http" command.&lt;/P&gt;
&lt;P&gt;Try:&lt;/P&gt;
&lt;P&gt;http 0.0.0.0 0.0.0.0 inside&lt;/P&gt;
&lt;P&gt;(or whatever interface you are trying to access from).&lt;/P&gt;
&lt;P&gt;You can substitute a more specific subnet or even host address for the 0.0.0.0/0 example.&lt;/P&gt;</description>
      <pubDate>Sat, 20 Jul 2019 12:29:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-block-traffic-when-should-be-allowed/m-p/3894081#M924852</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-07-20T12:29:22Z</dc:date>
    </item>
  </channel>
</rss>

