<?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: Incoming traffic one interface and users outgoing on another in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/incoming-traffic-one-interface-and-users-outgoing-on-another/m-p/1279093#M772268</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are correct. The issue is because of routing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately there is nothing much that can be done on the PIX. However if you have a router that supports PBR, you can set that up upstream to the PIX and have that device do the routing for you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 24 Oct 2009 23:23:05 GMT</pubDate>
    <dc:creator>Tanveer Deewan</dc:creator>
    <dc:date>2009-10-24T23:23:05Z</dc:date>
    <item>
      <title>Incoming traffic one interface and users outgoing on another using PIX 515</title>
      <link>https://community.cisco.com/t5/network-security/incoming-traffic-one-interface-and-users-outgoing-on-another/m-p/1279092#M772245</link>
      <description>&lt;P&gt;Hello every one,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;I currently have a PIX 515 6.3 set up in the following way&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;4 interfaces:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;nameif ethernet0 outside security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;nameif ethernet2 outside2 security50&lt;/P&gt;&lt;P&gt;nameif ethernet3 outsied3 security50&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;I have all my published services(http, smtp.. etc) on public IP of interface Outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;All users internet traffic also uses this interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Outside2 is used for our VPN Inter-office traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;global (outside2) 1 interface&lt;/P&gt;&lt;P&gt;global (outside3) 1 interface&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list 100&lt;/P&gt;&lt;P&gt;nat (inside) 1 192.168.80.0 255.255.255.0 0 0&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp x.x.x.107 www 192.168.80.4 www netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp x.x.x.107 smtp mail01 smtp netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp x.x.x.107 https 192.168.80.4 https netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (inside,outside) x.x.x.108 192.168.80.6 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (inside,outside) x.x.x.109 192.168.80.12 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;route outside 0.0.0.0 0.0.0.0 x.x.x.105 1&lt;/P&gt;&lt;P&gt;route outside2 z.z.z.16 255.255.255.248 z.z.z.241 1&lt;/P&gt;&lt;P&gt;route outside2 z.z.z.232 255.255.255.248 z.z.z.241 1&lt;/P&gt;&lt;P&gt;route outside2 z.z.z.192 255.255.255.248 z.z.z.241 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;I would like that all our internal users traffic use Interface Outside2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;this is what i have done so far.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;i have changed the default route:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;no route outside 0.0.0.0 0.0.0.0 x.x.x.105&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside2  0.0.0.0 0.0.0.0 z.z.z.241.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;all users can navigate on the internet fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;the problem is that no one can reach our public ip address on interface outside after this change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;I think the problem could be that when te trafic gets translated to the internal ip address then it goes back to the pix and gets out whit interface Outside2 IP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Can any one give me a hand whit this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;thanks very much for your time&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:29:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/incoming-traffic-one-interface-and-users-outgoing-on-another/m-p/1279092#M772245</guid>
      <dc:creator>hviniciusg</dc:creator>
      <dc:date>2019-03-11T16:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: Incoming traffic one interface and users outgoing on another</title>
      <link>https://community.cisco.com/t5/network-security/incoming-traffic-one-interface-and-users-outgoing-on-another/m-p/1279093#M772268</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are correct. The issue is because of routing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately there is nothing much that can be done on the PIX. However if you have a router that supports PBR, you can set that up upstream to the PIX and have that device do the routing for you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Oct 2009 23:23:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/incoming-traffic-one-interface-and-users-outgoing-on-another/m-p/1279093#M772268</guid>
      <dc:creator>Tanveer Deewan</dc:creator>
      <dc:date>2009-10-24T23:23:05Z</dc:date>
    </item>
    <item>
      <title>Re: Incoming traffic one interface and users outgoing on another</title>
      <link>https://community.cisco.com/t5/network-security/incoming-traffic-one-interface-and-users-outgoing-on-another/m-p/1279094#M772294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi tdeewan, thanks for the reply, I have a Cisco 1760 and I could set policy based routing on it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This device has 2 serial ports and 2 Ethernet ports; also there are 1 serial and one Ethernet ports free.&lt;/P&gt;&lt;P&gt;The router is connected to the pix using Fast Ethernet 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As of now a frame relay connection is configured on one of the serial interfaces and  the other Ethernet port is free&lt;/P&gt;&lt;P&gt;The final configuration I was thinking of would be to connect the ADSL connection to the free Ethernet port on the router. Then I could NAT the public IP of the Ethernet port of the ADSL connection to the pix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is one problem. I also use this ADSL connection for multiple site to site VPN's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I set up the pix so we still have the VPN's, our services to the world use the frame relay connection and internal users use the ADSL connection for internet traffic?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was thinking on using a secondary IP address on the Outside interface of the pix. I'm a little bit confused whit all this.&lt;/P&gt;&lt;P&gt;I'll appreciate a lot if someone could point me in the right direction to accomplish the following goals:&lt;/P&gt;&lt;P&gt;-	Route internal user traffic to the internet using the ADSL connection&lt;/P&gt;&lt;P&gt;-	Allow the VPN's connections on the ADSL Connection&lt;/P&gt;&lt;P&gt;-	Route Incoming traffic of the frame relay connection to our Internal servers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ADSL -----------------&lt;/P&gt;&lt;P&gt;Frame relay ---- ROUTER ---- PIX --- INTERNAL SERVER&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2009 13:10:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/incoming-traffic-one-interface-and-users-outgoing-on-another/m-p/1279094#M772294</guid>
      <dc:creator>hviniciusg</dc:creator>
      <dc:date>2009-10-26T13:10:17Z</dc:date>
    </item>
  </channel>
</rss>

