<?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 Same-security interface permit intra-interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261929#M809637</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Juan, Ive seen couple of similar threads before on this issue, quick searched  this one thread, try this solution which should do the trick.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Security&amp;amp;topic=Firewalling&amp;amp;topicID=.ee6e1fa&amp;amp;fromOutline=true&amp;amp;CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cc1d776/4" target="_blank"&gt;http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Security&amp;amp;topic=Firewalling&amp;amp;topicID=.ee6e1fa&amp;amp;fromOutline=true&amp;amp;CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cc1d776/4&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>Sun, 13 Sep 2009 20:25:38 GMT</pubDate>
    <dc:creator>JORGE RODRIGUEZ</dc:creator>
    <dc:date>2009-09-13T20:25:38Z</dc:date>
    <item>
      <title>ASA Same-security interface permit intra-interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261928#M809632</link>
      <description>&lt;P&gt;I would like to know how to use this command and any other related commands I need to make traffic enter and leave the same interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic network topology layout: &lt;/P&gt;&lt;P&gt;Internal network of ASA is 10.0.0.0/16&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Networks inside the ASA I need to reach 172.16.2.0/24, 10.255.255.0/24, and 10.0.5.0/24 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I executed the same-security interface permit intra-interface without any luck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I then created a static (inside,inside) 10.0.0.0 10.0.0.0 and I'm able to ping 10.255.255.x/24 I made sure the access-list on the inside interface allow source 10.0.0.0/16 to reach 10.255.255.0/24. I also made sure NAT exemption is configured too for this one network I'm working with but when I try to perform a TCP session to a host (10.0.120.20) that uses the ASA as a default gateway (10.0.100.244) I get the message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sep 13 2009 15:27:11 ASA02 : %ASA-6-106015: Deny TCP (no connection) from 10.0.120.20/3389 to 10.255.255.20/1141 flags SYN ACK  on interface insid&lt;/P&gt;&lt;P&gt;E&lt;/P&gt;&lt;P&gt;Can someone assist me with this configuration using the same-security interface permit intra-interface &lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Juan &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:14:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261928#M809632</guid>
      <dc:creator>juan-ruiz</dc:creator>
      <dc:date>2019-03-11T16:14:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Same-security interface permit intra-interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261929#M809637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Juan, Ive seen couple of similar threads before on this issue, quick searched  this one thread, try this solution which should do the trick.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Security&amp;amp;topic=Firewalling&amp;amp;topicID=.ee6e1fa&amp;amp;fromOutline=true&amp;amp;CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cc1d776/4" target="_blank"&gt;http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;forum=Security&amp;amp;topic=Firewalling&amp;amp;topicID=.ee6e1fa&amp;amp;fromOutline=true&amp;amp;CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cc1d776/4&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>Sun, 13 Sep 2009 20:25:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261929#M809637</guid>
      <dc:creator>JORGE RODRIGUEZ</dc:creator>
      <dc:date>2009-09-13T20:25:38Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Same-security interface permit intra-interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261930#M809644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This the suggested link help you resolve this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2009 20:48:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261930#M809644</guid>
      <dc:creator>mikewillis</dc:creator>
      <dc:date>2009-10-29T20:48:24Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Same-security interface permit intra-interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261931#M809665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What the syslog tells you there is that the ASA sees the SYN-ACK but it hasn't seen the SYN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are both hosts behind the ASA?&lt;/P&gt;&lt;P&gt;If yes, why do you want traffic to hit the ASA (same security intra command)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the ASA doesn't see then TCP SYN and it is routed directly between the hosts and then it sees the SYN-ACK it will be dropped due to stateful inspection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2009 20:57:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261931#M809665</guid>
      <dc:creator>Panos Kampanakis</dc:creator>
      <dc:date>2009-10-29T20:57:58Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Same-security interface permit intra-interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261932#M809673</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Both hosts are behind the ASA, however one host is behind a router which sits behind the ASA. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The combination of the stateful inspection command, the the static route pointing to itself has seemed to fix everything. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2009 21:00:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-same-security-interface-permit-intra-interface/m-p/1261932#M809673</guid>
      <dc:creator>mikewillis</dc:creator>
      <dc:date>2009-10-29T21:00:41Z</dc:date>
    </item>
  </channel>
</rss>

