<?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: ASA5525: Separate NAT for TCP and UDP? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa5525-separate-nat-for-tcp-and-udp/m-p/4548855#M1087237</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/981166"&gt;@CiscoMedMed&lt;/a&gt; what is your objective here?&lt;/P&gt;
&lt;P&gt;Are you setting up NAT to publish a server on the internet or just provide outbound internet access?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If publishing a server on the internet, then create a static NAT based on the protocol and port.&lt;/P&gt;
&lt;P&gt;If that just for internet access, you create a dynamic PAT based on IP network on any port/protocol.&lt;/P&gt;</description>
    <pubDate>Wed, 09 Feb 2022 17:12:47 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2022-02-09T17:12:47Z</dc:date>
    <item>
      <title>ASA5525: Separate NAT for TCP and UDP?</title>
      <link>https://community.cisco.com/t5/network-security/asa5525-separate-nat-for-tcp-and-udp/m-p/4548849#M1087236</link>
      <description>&lt;P&gt;When creating a NAT object, advanced settings asks you to specify TCP or UDP protocol. Does that mean you should create one NAT with private/public pair for UDP and one for TCP?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="NATGrab1.png" style="width: 497px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/143460iE2B50D0841D17098/image-size/large?v=v2&amp;amp;px=999" role="button" title="NATGrab1.png" alt="NATGrab1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Feb 2022 17:08:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5525-separate-nat-for-tcp-and-udp/m-p/4548849#M1087236</guid>
      <dc:creator>CiscoMedMed</dc:creator>
      <dc:date>2022-02-09T17:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: ASA5525: Separate NAT for TCP and UDP?</title>
      <link>https://community.cisco.com/t5/network-security/asa5525-separate-nat-for-tcp-and-udp/m-p/4548855#M1087237</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/981166"&gt;@CiscoMedMed&lt;/a&gt; what is your objective here?&lt;/P&gt;
&lt;P&gt;Are you setting up NAT to publish a server on the internet or just provide outbound internet access?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If publishing a server on the internet, then create a static NAT based on the protocol and port.&lt;/P&gt;
&lt;P&gt;If that just for internet access, you create a dynamic PAT based on IP network on any port/protocol.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Feb 2022 17:12:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa5525-separate-nat-for-tcp-and-udp/m-p/4548855#M1087237</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-02-09T17:12:47Z</dc:date>
    </item>
  </channel>
</rss>

