<?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: ip redirect with PIX 515 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844941#M489482</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thuven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The diagram didn't get formatted very well so I'm not sure if I understand. However, using the static NAT I suggested would meet the written requirements you have (users trying to access A would be redirected to B). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case, only B is the real host that lives on the Internet. You can think of A as just a virtual IP address that the PIX will do a translation for. If the PIX receives a packet destined for A on the LAN interface, it will just re-write the destination of the packet to B and send it on based on the routing table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Jan 2012 13:07:31 GMT</pubDate>
    <dc:creator>mirober2</dc:creator>
    <dc:date>2012-01-06T13:07:31Z</dc:date>
    <item>
      <title>ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844934#M489475</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I have a PIX 515 that i need to use as an ip redirector.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example if users try to access 80.80.80.80 ,they need to be redirected to 90.90.90.90&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; It ist possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show ver,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hardware:&amp;nbsp;&amp;nbsp; PIX-515E, 128 MB RAM, CPU Pentium II 433 MHz&lt;/P&gt;&lt;P&gt;Flash E28F128J3 @ 0xfff00000, 16MB&lt;/P&gt;&lt;P&gt;BIOS Flash AM29F400B @ 0xfffd8000, 32KB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 0: Ext: Ethernet0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 000b.5fad.0c99, irq 10&lt;/P&gt;&lt;P&gt; 1: Ext: Ethernet1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 000b.5fad.0c9a, irq 11&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Licensed features for this platform:&lt;/P&gt;&lt;P&gt;Maximum Physical Interfaces&amp;nbsp; : 6&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Maximum VLANs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 25&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Inside Hosts&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Unlimited &lt;/P&gt;&lt;P&gt;Failover&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Active/Active&lt;/P&gt;&lt;P&gt;VPN-DES&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;VPN-3DES-AES&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&amp;nbsp; &lt;/P&gt;&lt;P&gt;Cut-through Proxy&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Guards&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;URL Filtering&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Security Contexts&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;GTP/GPRS&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&amp;nbsp; &lt;/P&gt;&lt;P&gt;VPN Peers&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Unlimited &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This platform has an Unrestricted (UR) license.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance for the help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;T&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:09:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844934#M489475</guid>
      <dc:creator>teez007</dc:creator>
      <dc:date>2019-03-11T22:09:50Z</dc:date>
    </item>
    <item>
      <title>ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844935#M489476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thuven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use static NAT for this. See this page for more details and examples:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/cfgnat.html#wp1043190"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/cfgnat.html#wp1043190&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jan 2012 14:19:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844935#M489476</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2012-01-04T14:19:30Z</dc:date>
    </item>
    <item>
      <title>ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844936#M489477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If your 90.90.90.90 is a locally connected segment you can use a static route as such below, assuming you have prior nat in placed for 80.80.80.80 (static nat)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route (inside or dmz ) 80.80.80.80 255.255.255.255 90.90.90.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rizwan Rafeek.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jan 2012 14:30:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844936#M489477</guid>
      <dc:creator>rizwanr74</dc:creator>
      <dc:date>2012-01-04T14:30:16Z</dc:date>
    </item>
    <item>
      <title>ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844937#M489478</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;both IPs are on the outside interface, i am trying to redirect users on my lan.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any ideas ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 06:42:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844937#M489478</guid>
      <dc:creator>teez007</dc:creator>
      <dc:date>2012-01-05T06:42:59Z</dc:date>
    </item>
    <item>
      <title>ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844938#M489479</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thuven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can try something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;static (outside,inside) 80.80.80.80 90.90.90.90 netmask 255.255.255.255&lt;/PRE&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When users on the inside try to access 80.80.80.80, the PIX will change the destination IP of the packet to be 90.90.90.90.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 13:12:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844938#M489479</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2012-01-05T13:12:41Z</dc:date>
    </item>
    <item>
      <title>ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844939#M489480</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am not 100 percent sure exactly, what is that you are trying to accomplish.&lt;/P&gt;&lt;P&gt;Based on information you provided so far.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You said: "both IPs are on the outside interface, i am trying to redirect users on my lan."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume, that you have sub-interfaces ip addresses (two IPs) on the outside interface, if then you need a policy base nat.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regular nat:... &lt;/P&gt;&lt;P&gt;access-list &lt;STRONG&gt;allow-nat-all &lt;/STRONG&gt;extended permit ip 80.80.80.0 255.255.255.0 any &lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;nat (inside) 1 access-list &lt;STRONG&gt;allow-nat-all&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Policy nat:... &lt;/P&gt;&lt;P&gt;access-list &lt;STRONG&gt;allow-nat-specific &lt;/STRONG&gt;extended permit ip host 80.80.80.80 host 90.90.90.90 &lt;/P&gt;&lt;P&gt;global (outside) 2 xxx.xxx.xxx.xxx &lt;YOUR second="" ip="" address="" on="" the="" outside="" interface=""&gt;&lt;/YOUR&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 2 &lt;STRONG&gt;allow-nat-specific &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Let me know, if this is what you want to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rizwan Rafeek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 14:19:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844939#M489480</guid>
      <dc:creator>rizwanr74</dc:creator>
      <dc:date>2012-01-05T14:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844940#M489481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks Mike and Rizwanr,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; A&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; / &lt;/P&gt;&lt;P&gt;L ---[PIX]---- {Internet&amp;nbsp; } &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; \&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; \&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; B&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OK, think i should try and explain it a bit better,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;L = LAN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A = 80.80.80.80&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;B = 90.90.90.90&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if the LAN users try to access A, they should be redirected to B.&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;Mike, if i use the static nat you suggested, 90.90.90.90 would need to reside on the LAN (right ?) &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2012 07:05:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844940#M489481</guid>
      <dc:creator>teez007</dc:creator>
      <dc:date>2012-01-06T07:05:21Z</dc:date>
    </item>
    <item>
      <title>Re: ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844941#M489482</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thuven,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The diagram didn't get formatted very well so I'm not sure if I understand. However, using the static NAT I suggested would meet the written requirements you have (users trying to access A would be redirected to B). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case, only B is the real host that lives on the Internet. You can think of A as just a virtual IP address that the PIX will do a translation for. If the PIX receives a packet destined for A on the LAN interface, it will just re-write the destination of the packet to B and send it on based on the routing table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2012 13:07:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844941#M489482</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2012-01-06T13:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844942#M489483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thuven and Mike,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The requirement is that traffic is initiated from the LAN but not from the Internet-Users, therefore static-nat is out of the question. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If Thuven’s PIX has one leg (i.e. physical interface) facing the ISP’s circuit then there is only one route on the PIX takes all unknown traffic to destination to Default-Gateway (i.e. default route) on PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If otherwise Thuven’s PIX has two ISP circuits facing the Internet (i.e. physical or sub-interface) then a policy-base NAT will do the trick.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2012 14:07:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844942#M489483</guid>
      <dc:creator>rizwanr74</dc:creator>
      <dc:date>2012-01-06T14:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844943#M489484</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry for the late reply,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the pix has only 1 interface to the internet, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ok, so the users can access anything but if they try to access 80.80.80.80 they should be redirected to 90.90.90.90.(Both IPs live on the internet). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps more.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i will try and draw a more detailed diagram.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jan 2012 07:02:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844943#M489484</guid>
      <dc:creator>teez007</dc:creator>
      <dc:date>2012-01-09T07:02:46Z</dc:date>
    </item>
    <item>
      <title>Re: ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844944#M489485</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You cannot influence how your ISP transmits internet bound traffic on their network.&lt;BR /&gt;Since you do not have a next hop address pointing to 90.90.90.90, you cannot redirect traffic to 90.90.90.90 but to your default gateway only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if you own the IP (i.e. 90.90.90.90) and it is accessible on your circuit then you will be able to do a policy-nat, other than that there is nothing you can do, with limited internet circuit on the PIX outside interface.&lt;BR /&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jan 2012 17:00:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844944#M489485</guid>
      <dc:creator>rizwanr74</dc:creator>
      <dc:date>2012-01-09T17:00:47Z</dc:date>
    </item>
    <item>
      <title>Re: ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844945#M489486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so that means a PIX can inspect a packet and change the destination from IP to another on the WWW ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2012 08:45:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844945#M489486</guid>
      <dc:creator>teez007</dc:creator>
      <dc:date>2012-01-10T08:45:33Z</dc:date>
    </item>
    <item>
      <title>Re: ip redirect with PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844946#M489487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As far as I know, you can change next-hop address and in your case there is only one next hop, i.e. default-gateway pointing all unknown traffic to single destination, ISP gateway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take care.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rizwan Rafeek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2012 14:21:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-redirect-with-pix-515/m-p/1844946#M489487</guid>
      <dc:creator>rizwanr74</dc:creator>
      <dc:date>2012-01-10T14:21:24Z</dc:date>
    </item>
  </channel>
</rss>

