<?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 NATing on inside and outside interfaces? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nating-on-inside-and-outside-interfaces/m-p/2024133#M438347</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Muhammad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can do a static one to one to make this work&lt;/P&gt;&lt;P&gt;static (outside,inside) 192.168.1.9 112.1.1.5 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That will make it happen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Remember to rate all of the helpful posts&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Oct 2012 19:53:05 GMT</pubDate>
    <dc:creator>Julio Carvajal</dc:creator>
    <dc:date>2012-10-10T19:53:05Z</dc:date>
    <item>
      <title>NATing on inside and outside interfaces?</title>
      <link>https://community.cisco.com/t5/network-security/nating-on-inside-and-outside-interfaces/m-p/2024132#M438346</link>
      <description>&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/1/6/8/103861-nat%20que.JPG" alt="nat que.JPG" class="jive-image-thumbnail jive-image" height="370" onclick="" width="650" /&gt; &lt;/P&gt;&lt;P&gt;If&amp;nbsp; the source 192.168.114.1 is asking for destination ip 192.168.1.9 then the inside serial interface should be able to to tell that the source host with ip 192.168.114.1 is asking for 112.1.1.5 then it will be routed through serial1.&lt;/P&gt;&lt;P&gt;Now when the packet is coming to outside interface from source 112.1.1.5, then outside interface should be able to tell that the source is 192.168.1.9 but not 112.1.1.5 and it must be routed to the detination it is iasking for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Thanveer&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:56:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nating-on-inside-and-outside-interfaces/m-p/2024132#M438346</guid>
      <dc:creator>Muhammad Thanveer</dc:creator>
      <dc:date>2019-03-11T23:56:35Z</dc:date>
    </item>
    <item>
      <title>NATing on inside and outside interfaces?</title>
      <link>https://community.cisco.com/t5/network-security/nating-on-inside-and-outside-interfaces/m-p/2024133#M438347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Muhammad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can do a static one to one to make this work&lt;/P&gt;&lt;P&gt;static (outside,inside) 192.168.1.9 112.1.1.5 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That will make it happen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Remember to rate all of the helpful posts&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Oct 2012 19:53:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nating-on-inside-and-outside-interfaces/m-p/2024133#M438347</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-10-10T19:53:05Z</dc:date>
    </item>
  </channel>
</rss>

