<?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: Intra Interface communication on Inside interface on http? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/intra-interface-communication-on-inside-interface-on-http/m-p/1631075#M565240</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, you have an option to disable the TCP security feature (enable TCP state bypass) on the ASA to accomodate your requirement. However, as I said in the earlier post you referred to, it really defeats the purpose of having a firewall if you disable it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, it is definitely possible, and here is the configuration guide for your reference:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/conns_tcpstatebypass.html"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/conns_tcpstatebypass.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest that you configure the access-list to be as specific as possible to only cover the traffic that goes in and out of the ASA on that 1 interface, and apply the service-policy on that interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 Feb 2011 23:46:06 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2011-02-25T23:46:06Z</dc:date>
    <item>
      <title>Intra Interface communication on Inside interface on http?</title>
      <link>https://community.cisco.com/t5/network-security/intra-interface-communication-on-inside-interface-on-http/m-p/1631074#M565239</link>
      <description>&lt;P&gt;I have a setup on a client site very similiar to the attached diagram.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a route on the ASA to get to a remote site the other side of the router over MPLS cloud pointing to router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can ping to the remote site but cannot http to a device at the remote site.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I change the gateway of the client PC to the router everything works fine but this is not an option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is is this possible or are they trying to make something work that will not because going through ASA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;&lt;STRONG&gt;same-security-traffic permit&amp;nbsp; intra-interface&lt;/STRONG&gt; command is configured&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I found this info on another post:&amp;nbsp; &lt;/SPAN&gt;&lt;A href="https://community.cisco.com/thread/2009692" target="_blank"&gt;https://supportforums.cisco.com/thread/2009692?referring_site=kapi&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Unfortunately ASA firewall is a&amp;nbsp; security device, and a stateful firewall, hence it is keeping track of&amp;nbsp; the connection table, and incomplete TCP connection is deem to be not&amp;nbsp; secure (possibly an attack), unlike a router which is a routing device,&amp;nbsp; so it doesn't keep track of the connection table but just route traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ping&amp;nbsp; will definitely work, and UDP traffic will work to as they are&amp;nbsp; connectionless. The only traffic that won't work is TCP traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I get a client TCP connection to go into the ASA and back out the same interface and then over the router to remote site?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is my only option to configure another interface on firewall so traffic goes in inside and out interface-wan?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ASA is a 5505&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I set an acl on the inside interface to permit this http traffic and it gets hits on it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do I need to look at NAT if the ping works?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;BR /&gt;nat (inside) 0 access-list inside_nat0_outbound&lt;BR /&gt;nat (inside) 1 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure if this is over configured?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Roger&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:56:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intra-interface-communication-on-inside-interface-on-http/m-p/1631074#M565239</guid>
      <dc:creator>roger perkin</dc:creator>
      <dc:date>2019-03-11T19:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: Intra Interface communication on Inside interface on http?</title>
      <link>https://community.cisco.com/t5/network-security/intra-interface-communication-on-inside-interface-on-http/m-p/1631075#M565240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, you have an option to disable the TCP security feature (enable TCP state bypass) on the ASA to accomodate your requirement. However, as I said in the earlier post you referred to, it really defeats the purpose of having a firewall if you disable it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, it is definitely possible, and here is the configuration guide for your reference:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/conns_tcpstatebypass.html"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/conns_tcpstatebypass.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest that you configure the access-list to be as specific as possible to only cover the traffic that goes in and out of the ASA on that 1 interface, and apply the service-policy on that interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Feb 2011 23:46:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intra-interface-communication-on-inside-interface-on-http/m-p/1631075#M565240</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-02-25T23:46:06Z</dc:date>
    </item>
  </channel>
</rss>

