<?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: CISCO ASA5510 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa5510/m-p/727043#M1003916</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"There is an Access-list for tcp traffic. The Hit counter for that is 0. That mean traffic can reach outside interface but cannot access inside interface,,,,"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember that outside is less secure then inside therefore you need an access list TO ALLOW outside traffic to inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to have an access list like this&lt;/P&gt;&lt;P&gt;access-list OUTSIDE_TO_INSIDE extended permit tcp any any &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then apply it to outside!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group OUTSIDE_TO_INSIDE in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you should have hits on the counters otherwise the access list isnt working &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Jun 2007 21:16:01 GMT</pubDate>
    <dc:creator>Rodrigo Gurriti</dc:creator>
    <dc:date>2007-06-06T21:16:01Z</dc:date>
    <item>
      <title>CISCO ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa5510/m-p/727041#M1003914</link>
      <description>&lt;P&gt;|May 31 2007 18:59:20|106001: Inbound TCP connection denied from 10.0.0.0/1891 to 192.168.0.0/23 flags SYN  on interface Outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am receiving this error for both tcp and icmp traffics. I can ping from 10.0.0.0 network to the outside interface, but I cannot ping/telnet the 192.168.0.0 network. There is an Access-list for tcp traffic. The Hit counter for that is 0. That mean traffic can reach outside interface but cannot access inside interface,,,,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any clues? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:23:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa5510/m-p/727041#M1003914</guid>
      <dc:creator>arafat009</dc:creator>
      <dc:date>2019-03-11T10:23:35Z</dc:date>
    </item>
    <item>
      <title>Re: CISCO ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa5510/m-p/727042#M1003915</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is a connection-related message. This message occurs when an attempt to connect to an inside address is denied by your security policy. Possible TCP_flags values correspond to the flags in the TCP header that were present when the connection was denied. For example, a TCP packet arrived for which no connection state exists in the PIX Firewall, and it was dropped. The TCP_flags in this packet are FIN and ACK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The TCP_flags are as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;?ACK?The acknowledgment number was received. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;?FIN?Data was sent. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;?PSH?The receiver passed data to the application. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;?RST?The connection was reset. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;?SYN?Sequence numbers were synchronized to start a connection. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;?URG?The urgent pointer was declared valid. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try this link:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_62/syslog/pixemsgs.htm#wp1022675" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_62/syslog/pixemsgs.htm#wp1022675&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jun 2007 19:33:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa5510/m-p/727042#M1003915</guid>
      <dc:creator>thomas.chen</dc:creator>
      <dc:date>2007-06-06T19:33:07Z</dc:date>
    </item>
    <item>
      <title>Re: CISCO ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa5510/m-p/727043#M1003916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"There is an Access-list for tcp traffic. The Hit counter for that is 0. That mean traffic can reach outside interface but cannot access inside interface,,,,"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember that outside is less secure then inside therefore you need an access list TO ALLOW outside traffic to inside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to have an access list like this&lt;/P&gt;&lt;P&gt;access-list OUTSIDE_TO_INSIDE extended permit tcp any any &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then apply it to outside!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group OUTSIDE_TO_INSIDE in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you should have hits on the counters otherwise the access list isnt working &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jun 2007 21:16:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa5510/m-p/727043#M1003916</guid>
      <dc:creator>Rodrigo Gurriti</dc:creator>
      <dc:date>2007-06-06T21:16:01Z</dc:date>
    </item>
  </channel>
</rss>

