<?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 Hi Mohammed, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/2796892#M173270</link>
    <description>&lt;P&gt;Hi Mohammed,&lt;/P&gt;
&lt;P&gt;When you say that in both the occasions you are trying to perform source NAT, then for Inbound NAT, ASA would be having a route for the mapped address pointing towards Outside. That could be the reason it would be going Identity.&lt;/P&gt;
&lt;P&gt;Please check your nat statement. You could also share the required nat statement if it doesn't work.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hope it helps.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Akshay Rastogi&lt;/P&gt;
&lt;P&gt;Remember to rate helpful posts.&lt;/P&gt;</description>
    <pubDate>Sun, 24 Jan 2016 03:18:02 GMT</pubDate>
    <dc:creator>Akshay Rastogi</dc:creator>
    <dc:date>2016-01-24T03:18:02Z</dc:date>
    <item>
      <title>NAT Issue</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/2796890#M173268</link>
      <description>&lt;P&gt;I have an issue with NAT. My setup is as follows:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;LAN ---&amp;gt; inside ifc&amp;nbsp; (ASA 9.5)&amp;nbsp; outside ifc -----&amp;gt;&amp;nbsp; Internet&amp;nbsp; --------&amp;gt; customer firewall&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have a VPN on the outside interface over the Internet to the customer. I am doing NAT on the inside ifc for outbound traffic and also NAT on the outside ifc for inbound traffic. On both occasions I am only NAT'ng the source address. My outbound NAT (inside ifc) is working fine. My inbound NAT is doing identity NAT (i.e. NAT to itself). I have tried both object and global nat and both are giving the same results.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:09:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/2796890#M173268</guid>
      <dc:creator>Mohammed Shafiq</dc:creator>
      <dc:date>2019-03-12T07:09:21Z</dc:date>
    </item>
    <item>
      <title>Could you be more specific as</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/2796891#M173269</link>
      <description>&lt;P&gt;Could you be more specific as to what is not working? &amp;nbsp;Could you past the chunk of your config relating to NAT please.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jan 2016 00:41:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/2796891#M173269</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-01-18T00:41:32Z</dc:date>
    </item>
    <item>
      <title>Hi Mohammed,</title>
      <link>https://community.cisco.com/t5/network-security/nat-issue/m-p/2796892#M173270</link>
      <description>&lt;P&gt;Hi Mohammed,&lt;/P&gt;
&lt;P&gt;When you say that in both the occasions you are trying to perform source NAT, then for Inbound NAT, ASA would be having a route for the mapped address pointing towards Outside. That could be the reason it would be going Identity.&lt;/P&gt;
&lt;P&gt;Please check your nat statement. You could also share the required nat statement if it doesn't work.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hope it helps.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Akshay Rastogi&lt;/P&gt;
&lt;P&gt;Remember to rate helpful posts.&lt;/P&gt;</description>
      <pubDate>Sun, 24 Jan 2016 03:18:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-issue/m-p/2796892#M173270</guid>
      <dc:creator>Akshay Rastogi</dc:creator>
      <dc:date>2016-01-24T03:18:02Z</dc:date>
    </item>
  </channel>
</rss>

