<?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: PIX NAT question.. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398067#M555853</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you can certainly do static translation for hosts on the inside (or any other high security zones) that do not belong to the same subnet of the inside interface(or high security zone). As long as your routing is configured correctly, you can translate addresses behind a firewall interface. &lt;/P&gt;&lt;P&gt;In your example, your inside interface is connected to a L3 switch or router that takes care of routing for the 10.210 subnet. On the PIX, you will need a static route that will route packets destined to 10.210.0.0/16 (i make assumption on the subnet mask)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route inside 10.210.0.0 255.255.0.0 &lt;NEXT-HOP address=""&gt;&lt;/NEXT-HOP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;NEXT-HOP address=""&gt; is the IP of the router/L3 switch interface &lt;/NEXT-HOP&gt;&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;Binh &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Oct 2004 00:25:41 GMT</pubDate>
    <dc:creator>hoangbp</dc:creator>
    <dc:date>2004-10-26T00:25:41Z</dc:date>
    <item>
      <title>PIX NAT question..</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398066#M555852</link>
      <description>&lt;P&gt;I have a pix running 5.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are my current NAT entries.&lt;/P&gt;&lt;P&gt;nat (inside) 1 0.0.0.0 0.0.0.0 0 0&lt;/P&gt;&lt;P&gt;static (inside,outside) 199.1.235.192 192.168.235.192 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (inside,outside) 199.1.235.135 192.168.235.135 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (inside,outside) 199.1.235.183 192.168.235.183 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This box has 2 interfaces 1 on the inside and 1 for the outside. The inside is on the 192.168 subnet and the outside is on the 199.1 subnet &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way to add a static entry that is not on the inside subnet?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for example: static (inside,outside) 199.1.235.160 10.210.0.16 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:42:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398066#M555852</guid>
      <dc:creator>syancy</dc:creator>
      <dc:date>2020-02-21T07:42:19Z</dc:date>
    </item>
    <item>
      <title>Re: PIX NAT question..</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398067#M555853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you can certainly do static translation for hosts on the inside (or any other high security zones) that do not belong to the same subnet of the inside interface(or high security zone). As long as your routing is configured correctly, you can translate addresses behind a firewall interface. &lt;/P&gt;&lt;P&gt;In your example, your inside interface is connected to a L3 switch or router that takes care of routing for the 10.210 subnet. On the PIX, you will need a static route that will route packets destined to 10.210.0.0/16 (i make assumption on the subnet mask)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route inside 10.210.0.0 255.255.0.0 &lt;NEXT-HOP address=""&gt;&lt;/NEXT-HOP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;NEXT-HOP address=""&gt; is the IP of the router/L3 switch interface &lt;/NEXT-HOP&gt;&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;Binh &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Oct 2004 00:25:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398067#M555853</guid>
      <dc:creator>hoangbp</dc:creator>
      <dc:date>2004-10-26T00:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: PIX NAT question..</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398068#M555854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Binh, but I am still confused. if I just add that line " route inside 10.210.0.0 255.255.0.0 &lt;NEXT-HOP address=""&gt;" that covers the routing.&lt;/NEXT-HOP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What do I do for the host connected to the switch which is connected directly to the PIX. What do I use as the hosts default gateway, how does the host even see the PIX. The host has adress on the 10 net but the interface that it must exit through is on the 192.168 net.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Oct 2004 02:20:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398068#M555854</guid>
      <dc:creator>syancy</dc:creator>
      <dc:date>2004-10-26T02:20:36Z</dc:date>
    </item>
    <item>
      <title>Re: PIX NAT question..</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398069#M555855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not to speak for Binh on this one, but I believe there was some confusiuon related to your original post.  I did not think you were referring to creating a static translation for a host on another subnet *but* with that host on the same L2 segment as the inside of your PIX.  We all assumed you were referring to creating a static translation for a host that was an L3 hop away (meaning, on the other side of a router that was inside the PIX).  So, Binh's original reply was correct with our incorrect (it seems anyway) assumption in mind.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, back to your problem.  There really is no way to accomplish what you are trying to do.  In a router scenerio, you would normally add a secondary address to the inside interface and assign it an address from the 10.210.0.0/16 range.  However, the PIX does not support secondary addresses.  The solution is to add a 2 interface L3 device (router of some sort) and assign it one address from the 10.210.0.0/16 range and another address from the range that the inside of your PIX sits on.  With this in place, Binh's post is dead on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, I will say that I have seen some OS's (not sure how they do this) allow you to assign a default gateway that is not in the same subnet as the hosts NIC address.  I have no idea how this works as it seems to go against the laws of subnetting but it does work.  Never spent much time getting into the ins and outs of which OS's work like this but I thought I would throw it out there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck and let us know if this is not clear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Oct 2004 12:58:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398069#M555855</guid>
      <dc:creator>scoclayton</dc:creator>
      <dc:date>2004-10-26T12:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: PIX NAT question..</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398070#M555856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My bad for making the wrong assumption regarding the original issue.&lt;/P&gt;&lt;P&gt;Scott,&lt;/P&gt;&lt;P&gt;Thanks for stepping in and clarify the issue. You are right on!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Binh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Oct 2004 13:18:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398070#M555856</guid>
      <dc:creator>hoangbp</dc:creator>
      <dc:date>2004-10-26T13:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: PIX NAT question..</title>
      <link>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398071#M555857</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What type of pix do you have from 515 towards you can configure VLAN Interfaces, if so you can add a VLAN interface that belongs to the 10.210.0.X network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Oct 2004 15:11:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-nat-question/m-p/398071#M555857</guid>
      <dc:creator>fausto-oliveira</dc:creator>
      <dc:date>2004-10-26T15:11:52Z</dc:date>
    </item>
  </channel>
</rss>

