<?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 Static NAT to IP that is not local to ASA? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938156#M436076</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Help please..&amp;nbsp; I am working on this now and not yet concerned with the static NAT but can't get simple internal static route to work.&amp;nbsp; I need ASA inside 10.10.10.0/24 to route to 10.10.100.0/24 voice network conencted via 10.10.10.254 on my L3 switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did this command:&lt;/P&gt;&lt;PRE style="white-space: pre-wrap; color: #222222; background-color: rgba(255, 255, 255, 0.917969);"&gt;&lt;SPAN style="font-family: 'courier new', monospace;"&gt;route inside 10.10.100.0 255.255.255.0 10.10.10.254&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and now I can ping 10.10.100.1 from ASA but not from 10.10.10.0 network because I think ACL is needed to allow route between subnets but I don't know what it should like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 May 2012 19:02:23 GMT</pubDate>
    <dc:creator>Brandon Svec</dc:creator>
    <dc:date>2012-05-25T19:02:23Z</dc:date>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938152#M436072</link>
      <description>&lt;P&gt;All, I have a doubt about a configuration I am requesting.&amp;nbsp; I know just a little about ASA myself, but am working with a contractor on this project and he is not sure this can be done or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My applciation is this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- ASA with internet and some public IP.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Exisiting internal LAN of 10.10.10.0/24.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- New voice VLAN 10.10.100.0 on L3 SGE switch doing inter-vlan route between 10.10.100.0/24 and 10.10.10.0/24 via 10.10.10.1 (ASA internal interface) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- ASA will have static route to 10.10.100.0/24 via 10.10.10.254 (data VLAN interface on my L3 switch)&amp;nbsp; This much is a known working configuration for me to allow voice and data vlans to route and require very little of firewall contractor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I need static NAT of a public IP to my IP PBX on 10.10.100.1.&amp;nbsp; The doubt I have is if they try to configure this the ASA will not want to make a NAT to 10.10.100.1 because that network does not exist anywhere in the ASA config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to make this work or will it be required/better to use an extra interface no the ASA and make it 10.10.100.0/24 and have the ASA do inter-vlan routing instead of the switch?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Brandon&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:10:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938152#M436072</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2019-03-11T23:10:44Z</dc:date>
    </item>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938153#M436073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What you are trying to configure is achievable. Voice VLAN does not need to be a subnet on the ASA as long as you have a route to that subnet as you have configured on the ASA, it would be fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please share what you have tried to configure and the error message when you are trying to configure it and it does not take it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For inbound access from the internet, you would need static NAT configured as well as access-list on the outside interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2012 00:50:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938153#M436073</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2012-05-24T00:50:52Z</dc:date>
    </item>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938154#M436074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks very much for the reply.&amp;nbsp; I agree with you, but the person working on the firewall led me to think otherwise..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The implementation will not happen untill Friday when they move their ASA to a new location where I have already installed the switch and IP PBX.&amp;nbsp; So I won't be able to try anything until then, but thank you for clearing my doubt about if static NAT can work to a subnet not on the ASA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2012 03:23:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938154#M436074</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2012-05-24T03:23:33Z</dc:date>
    </item>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938155#M436075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Brandon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agreewith Jeniffer, this can be done using the same inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ASA will be involved on this as it will have a route to that particular PBX on it's inside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you need to make sure is that the layer 3 device connecting to 10.10.10 and 10.10.100 does not do any nat between them so the ASA can handle that.&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;Julio&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DO rate all the helpful posts&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2012 05:51:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938155#M436075</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-05-24T05:51:29Z</dc:date>
    </item>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938156#M436076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Help please..&amp;nbsp; I am working on this now and not yet concerned with the static NAT but can't get simple internal static route to work.&amp;nbsp; I need ASA inside 10.10.10.0/24 to route to 10.10.100.0/24 voice network conencted via 10.10.10.254 on my L3 switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did this command:&lt;/P&gt;&lt;PRE style="white-space: pre-wrap; color: #222222; background-color: rgba(255, 255, 255, 0.917969);"&gt;&lt;SPAN style="font-family: 'courier new', monospace;"&gt;route inside 10.10.100.0 255.255.255.0 10.10.10.254&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and now I can ping 10.10.100.1 from ASA but not from 10.10.10.0 network because I think ACL is needed to allow route between subnets but I don't know what it should like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2012 19:02:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938156#M436076</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2012-05-25T19:02:23Z</dc:date>
    </item>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938157#M436077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your 10.10.10.0 network should have default gateway as the switch 10.10.10.254 instead of the ASA. Then the switch should have default gateway pointing towards the ASA.&lt;/P&gt;&lt;P&gt;Reason is because ASA will drop the packet if it does not see the complete session for security reason.&lt;/P&gt;&lt;P&gt;If you change your host in 10.10.10.0/24 network default gateway to the switch, it will work just fine.&lt;/P&gt;&lt;P&gt;Let me know how it goes or if you have any further question.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2012 23:47:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938157#M436077</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2012-05-25T23:47:41Z</dc:date>
    </item>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938158#M436078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply.&amp;nbsp; Since I don't have access to the ASA myself I now have to wait until Tuesday to go back and test things..&amp;nbsp; I appreciate your input and will update when resolved or if I still need help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 May 2012 17:29:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938158#M436078</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2012-05-26T17:29:46Z</dc:date>
    </item>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938159#M436079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The inside static route is now working, thank you.&amp;nbsp; Back to my original question about static NAT.&amp;nbsp; I just need a public IP to pass all traffic to an internal IP that is on the 10.10.100.0/24 network not directly conencted to the ASA.&amp;nbsp; I am thinking this would be the command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (outside,inside) 10.10.100.1 222.222.222.222 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does that seem correct and can you provide an example of what the ACL would look like?&amp;nbsp; I want to just allow all traffic now for the purpose of remote IP phones and some admin and mobile apps using various ports.&amp;nbsp; Once it is tested working I will let the firewall vendor layer security on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;Brandon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 May 2012 15:24:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938159#M436079</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2012-05-29T15:24:44Z</dc:date>
    </item>
    <item>
      <title>Static NAT to IP that is not local to ASA?</title>
      <link>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938160#M436080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It should be:&lt;/P&gt;&lt;P&gt;static (inside,outside) 222.222.222.222 10.10.100.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above static statement works bidirectionally.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also if the traffic is originated from the Internet, you would need to configure access-list and apply that to your outside interface.&lt;/P&gt;&lt;P&gt;Eg:&lt;/P&gt;&lt;P&gt;access-list outside-acl permit ip any host 222.222.222.222&lt;/P&gt;&lt;P&gt;access-group outside-acl in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you already have an existing access-list applied to the outside interface, just add the permit statement to the existing access-list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 May 2012 19:29:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-nat-to-ip-that-is-not-local-to-asa/m-p/1938160#M436080</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2012-05-29T19:29:42Z</dc:date>
    </item>
  </channel>
</rss>

