<?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: Alternative to NAT ? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/alternative-to-nat/m-p/1558167#M658174</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure what you are trying to achieve. If you are just working on the&lt;/P&gt;&lt;P&gt;routing part, it will certainly work as long as you bypass the NAT on the&lt;/P&gt;&lt;P&gt;firewall (I am assuming that the Router A and Router B are on two different&lt;/P&gt;&lt;P&gt;interfaces of the ASA). Since you are using pre-8.3 code, you can configure&lt;/P&gt;&lt;P&gt;"no nat-control" and the ASA will not impose any NAT requirements. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as your first question about Lifesize, I think it does support NAT.&lt;/P&gt;&lt;P&gt;In Lifesize, there is an option to enable/disable NAT support. You need to&lt;/P&gt;&lt;P&gt;disable NAT aware feature (feature that tells Lifesize device to use public&lt;/P&gt;&lt;P&gt;IP when going to internet). Then you configure static NAT on the firewall&lt;/P&gt;&lt;P&gt;along with H.323/SIP inspects. That will make sure that your traffic goes to&lt;/P&gt;&lt;P&gt;internet without any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&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;NT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Sep 2010 16:47:15 GMT</pubDate>
    <dc:creator>Nagaraja Thanthry</dc:creator>
    <dc:date>2010-09-07T16:47:15Z</dc:date>
    <item>
      <title>Alternative to NAT ?</title>
      <link>https://community.cisco.com/t5/network-security/alternative-to-nat/m-p/1558166#M658164</link>
      <description>&lt;P&gt;Hello All&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using a SA 5520 with the following version&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt; mso-layout-grid-align: none;"&gt;&lt;SPAN style=": ; color: #000000; font-size: 10pt; sans-serif&amp;amp;quot: ; mso-ansi-language: EN-CA; font-family: &amp;amp;quot; , &amp;amp;quot: ; Arial&amp;amp;quot: ; "&gt;Cisco Adaptive Security Appliance Software Version 8.0(3)&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt; mso-layout-grid-align: none;"&gt;&lt;SPAN style=": ; color: #000000; font-size: 10pt; sans-serif&amp;amp;quot: ; font-family: &amp;amp;quot; , &amp;amp;quot: ; Arial&amp;amp;quot: ; "&gt;Device Manager Version 6.0(3)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a new device which will be used for the multiple video conference ( MCU ) its from lifesize. The issue is it doesn't support the NATTINg feature and I have make the MCU unit public at the same it should also be available to Internet user. When I am trying to use a static route something like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Router in Building A has public IP 1.1.1.1&lt;BR /&gt;Private LAN in Building A is 192.168.1.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Router in Building B has public IP 2.2.2.2&lt;BR /&gt;Private LAN in Building B is 192.168.2.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Router A&amp;nbsp; I put a static route that says:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip route 192.168.2.0 255.255.255.0 2.2.2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and then vice versa on Router B.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I'm pretty sure this won't work (and it hasn't in my tests), but I've never really understood why not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is without using the NAT. Is there something out there which can used to change the public - &amp;gt; private and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Soofi&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:36:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/alternative-to-nat/m-p/1558166#M658164</guid>
      <dc:creator>soofiahtesham</dc:creator>
      <dc:date>2019-03-11T18:36:20Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative to NAT ?</title>
      <link>https://community.cisco.com/t5/network-security/alternative-to-nat/m-p/1558167#M658174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure what you are trying to achieve. If you are just working on the&lt;/P&gt;&lt;P&gt;routing part, it will certainly work as long as you bypass the NAT on the&lt;/P&gt;&lt;P&gt;firewall (I am assuming that the Router A and Router B are on two different&lt;/P&gt;&lt;P&gt;interfaces of the ASA). Since you are using pre-8.3 code, you can configure&lt;/P&gt;&lt;P&gt;"no nat-control" and the ASA will not impose any NAT requirements. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as your first question about Lifesize, I think it does support NAT.&lt;/P&gt;&lt;P&gt;In Lifesize, there is an option to enable/disable NAT support. You need to&lt;/P&gt;&lt;P&gt;disable NAT aware feature (feature that tells Lifesize device to use public&lt;/P&gt;&lt;P&gt;IP when going to internet). Then you configure static NAT on the firewall&lt;/P&gt;&lt;P&gt;along with H.323/SIP inspects. That will make sure that your traffic goes to&lt;/P&gt;&lt;P&gt;internet without any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&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;NT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Sep 2010 16:47:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/alternative-to-nat/m-p/1558167#M658174</guid>
      <dc:creator>Nagaraja Thanthry</dc:creator>
      <dc:date>2010-09-07T16:47:15Z</dc:date>
    </item>
  </channel>
</rss>

