<?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 NAT for traffic originating from ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-for-traffic-originating-from-asa/m-p/2582579#M203603</link>
    <description>&lt;P&gt;Hello folks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am facing a unique scenario. I have an ASA which is connected to an WAN network and it has private address on the outside interface. There are few PCs connected to the inside interface and the traffic from them is NAT-d&amp;nbsp;to an IP for internet access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This ASA also has botnet license, that means it needs to go internet periodically to download updates,&amp;nbsp;my question is it possible to force the ASA to use a different IP other than the outside interface IP&amp;nbsp;&amp;nbsp;while it sents traffic to internet ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in Advance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:06:50 GMT</pubDate>
    <dc:creator>Mike Anderson</dc:creator>
    <dc:date>2019-03-12T05:06:50Z</dc:date>
    <item>
      <title>NAT for traffic originating from ASA</title>
      <link>https://community.cisco.com/t5/network-security/nat-for-traffic-originating-from-asa/m-p/2582579#M203603</link>
      <description>&lt;P&gt;Hello folks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am facing a unique scenario. I have an ASA which is connected to an WAN network and it has private address on the outside interface. There are few PCs connected to the inside interface and the traffic from them is NAT-d&amp;nbsp;to an IP for internet access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This ASA also has botnet license, that means it needs to go internet periodically to download updates,&amp;nbsp;my question is it possible to force the ASA to use a different IP other than the outside interface IP&amp;nbsp;&amp;nbsp;while it sents traffic to internet ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in Advance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:06:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-for-traffic-originating-from-asa/m-p/2582579#M203603</guid>
      <dc:creator>Mike Anderson</dc:creator>
      <dc:date>2019-03-12T05:06:50Z</dc:date>
    </item>
    <item>
      <title>Hello Mike, You can indeed do</title>
      <link>https://community.cisco.com/t5/network-security/nat-for-traffic-originating-from-asa/m-p/2582580#M203604</link>
      <description>&lt;P&gt;Hello Mike,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can indeed do the PAT with another IP address, my question is, which will be the gateway of last resort?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is the Private IP address on the outside being NATed to a public IP address by a device in front of it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;with the --&amp;gt; Show xlate&amp;nbsp;&lt;/P&gt;&lt;P&gt;You will be able to monitor the translations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please don't forget to rate and mark as correct the helpful post!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;David Castro,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Nov 2014 15:29:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-for-traffic-originating-from-asa/m-p/2582580#M203604</guid>
      <dc:creator>David Johan Castro Fernandez</dc:creator>
      <dc:date>2014-11-20T15:29:13Z</dc:date>
    </item>
    <item>
      <title>Hi, The ASA to my</title>
      <link>https://community.cisco.com/t5/network-security/nat-for-traffic-originating-from-asa/m-p/2582581#M203606</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ASA to my understanding only uses its interface IP addresses to originate traffic/connections from itself.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I guess you are saying that the users behind the ASA are using some different NAT IP address (something other than the interface IP) for their Internet access?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I guess in that case you would need to make some additional NAT/ACL configurations on some device in front of the ASA to allow the ASA to get those updates from the Internet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or you could configure an additional interface on the ASA so you can use the IP address on the ASA that you want. This would require you to know the destination subnets/network from which the ASA gets the updates from though so you could configure static routes for those destination subnets/networks through that new interface. Probably not an ideal solution but still possible.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There have been many similiar questions in the past. Its a shame for example that you can not use multiple different public IP addresses on an ASA to build L2L VPN connections for example or just have multiple subnets gateways configured on a single interface (for some special situations). These seem to point to the situation that the ASA can not use any other IP address to originate connections "out of the box" other than those configured on the interfaces.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would surely make some migrations easier if it was possible &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;</description>
      <pubDate>Fri, 21 Nov 2014 07:22:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-for-traffic-originating-from-asa/m-p/2582581#M203606</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2014-11-21T07:22:43Z</dc:date>
    </item>
  </channel>
</rss>

