<?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 PIX rules &amp; return traffic... in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281085#M594551</link>
    <description>&lt;P&gt;Just confirming that if I allow a TCP conversation to originate on the Internal Interface, that the reply traffic will be allowed back thru the PIX, to the original sender?  What CLI command enables this, or how can I tell this is true?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, with UDP, since it's connectionless, and there's no acknowlegement, return traffic does not exist, correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-alex&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 07:14:39 GMT</pubDate>
    <dc:creator>abatson</dc:creator>
    <dc:date>2020-02-21T07:14:39Z</dc:date>
    <item>
      <title>PIX rules &amp; return traffic...</title>
      <link>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281085#M594551</link>
      <description>&lt;P&gt;Just confirming that if I allow a TCP conversation to originate on the Internal Interface, that the reply traffic will be allowed back thru the PIX, to the original sender?  What CLI command enables this, or how can I tell this is true?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, with UDP, since it's connectionless, and there's no acknowlegement, return traffic does not exist, correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-alex&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:14:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281085#M594551</guid>
      <dc:creator>abatson</dc:creator>
      <dc:date>2020-02-21T07:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: PIX rules &amp; return traffic...</title>
      <link>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281086#M594554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is just the default nature of a pix. By default, all connections from high security to low security connections are allowing, and their return traffic is allowed back in. This is true for both tcp and udp. There is udp return traffic - most DNS requests and replies are UDP based&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Feb 2004 15:11:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281086#M594554</guid>
      <dc:creator>mostiguy</dc:creator>
      <dc:date>2004-02-16T15:11:19Z</dc:date>
    </item>
    <item>
      <title>Re: PIX rules &amp; return traffic...</title>
      <link>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281087#M594557</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;By default there is no configuration changes to get the ASA working.  You can check con connection state with the "show xlate command" and the "show connection" commands.  Maybe this documnet will answer your questions....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a00800b6f0e.html#1008066" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a00800b6f0e.html#1008066&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Feb 2004 15:14:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281087#M594557</guid>
      <dc:creator>mike-greene</dc:creator>
      <dc:date>2004-02-16T15:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: PIX rules &amp; return traffic...</title>
      <link>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281088#M594558</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Alex,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As previous post suggestion, you can execute "show xlate" to verify that the translation is getting built up.  To check if the return traffic is back and if the connection is completed, you can execute "show conn" and see the connection flag "U".  U stands for up, so in case of TCP if 3-way handshake is established if the connection is established, you should see the flag U.  Here is the flags of connection originating from inside -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inside:         Outside    Flags &lt;/P&gt;&lt;P&gt;---------------------------------- &lt;/P&gt;&lt;P&gt; SYN      --&amp;gt;                  saA &lt;/P&gt;&lt;P&gt;         &amp;lt;--    SYN + ACK        A &lt;/P&gt;&lt;P&gt; ACK      --&amp;gt;                  U &lt;/P&gt;&lt;P&gt;         &amp;lt;--     Data          UI &lt;/P&gt;&lt;P&gt; Data     --&amp;gt;                  UIO &lt;/P&gt;&lt;P&gt; FIN      --&amp;gt;                  Uf &lt;/P&gt;&lt;P&gt;         &amp;lt;--    FIN + ACK      UfFR &lt;/P&gt;&lt;P&gt; ACK      --&amp;gt;                  UfFRr &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;Mynul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Feb 2004 17:17:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-rules-return-traffic/m-p/281088#M594558</guid>
      <dc:creator>mhoda</dc:creator>
      <dc:date>2004-02-16T17:17:45Z</dc:date>
    </item>
  </channel>
</rss>

