<?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 using different IP range than on outside interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-using-different-ip-range-than-on-outside-interface/m-p/1923116#M458672</link>
    <description>&lt;P&gt;I have a need to use another class C subnet for outbound NAT purposes, but this new range isn't bound to the outside interface. Is this possible?&lt;/P&gt;&lt;P&gt;Outside interface IP: 1.1.1.1/24&lt;/P&gt;&lt;P&gt;Inside interfac ip: 10.1.1.x/24&lt;/P&gt;&lt;P&gt;New block: 192.168.1.0/24&lt;/P&gt;&lt;P&gt;New inside hosts needing nat on new range: 10.14.1.x/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So basically I want to use a range of ip's not bound to and interface to use as the PAT'd address when the packet leaves the ASA. What would this config look like?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 22:36:39 GMT</pubDate>
    <dc:creator>clark.d</dc:creator>
    <dc:date>2019-03-11T22:36:39Z</dc:date>
    <item>
      <title>NAT using different IP range than on outside interface</title>
      <link>https://community.cisco.com/t5/network-security/nat-using-different-ip-range-than-on-outside-interface/m-p/1923116#M458672</link>
      <description>&lt;P&gt;I have a need to use another class C subnet for outbound NAT purposes, but this new range isn't bound to the outside interface. Is this possible?&lt;/P&gt;&lt;P&gt;Outside interface IP: 1.1.1.1/24&lt;/P&gt;&lt;P&gt;Inside interfac ip: 10.1.1.x/24&lt;/P&gt;&lt;P&gt;New block: 192.168.1.0/24&lt;/P&gt;&lt;P&gt;New inside hosts needing nat on new range: 10.14.1.x/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So basically I want to use a range of ip's not bound to and interface to use as the PAT'd address when the packet leaves the ASA. What would this config look like?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:36:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-using-different-ip-range-than-on-outside-interface/m-p/1923116#M458672</guid>
      <dc:creator>clark.d</dc:creator>
      <dc:date>2019-03-11T22:36:39Z</dc:date>
    </item>
    <item>
      <title>Re: NAT using different IP range than on outside interface</title>
      <link>https://community.cisco.com/t5/network-security/nat-using-different-ip-range-than-on-outside-interface/m-p/1923117#M458673</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it is possible (atleast with 8.2) but only for inbound connections, otherwise you would have a routing problem since it does not support policy based routing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just configure it as you would do a normal static but with the address from the other net and it will work just fine.&lt;/P&gt;&lt;P&gt;do not forget to allow the traffic in an ACL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Feb 2012 09:40:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-using-different-ip-range-than-on-outside-interface/m-p/1923117#M458673</guid>
      <dc:creator>hobbe</dc:creator>
      <dc:date>2012-02-29T09:40:03Z</dc:date>
    </item>
  </channel>
</rss>

