<?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 routing on asa in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889066#M457076</link>
    <description>&lt;P&gt;L3 sitch is connected to firewall and firewall is connected to router&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on l3 network 10.0.0.0/24&lt;/P&gt;&lt;P&gt;172.16.0.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and default route is to firewall&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;from firewall default route is&amp;nbsp; ROUTE OUTSIDE 0.0.0.0 0.0.0.0 202.x.x.x(router)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&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 another router my requirement is i want 172.16.0.0 /24 data should go through this router(124.x.x.x)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;iF I GIVE THE ROUTE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ROUTE OUTSIDE 172.16.X.X 255.255.255.0 124.X.X.X ON FIREWALL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;THUS IT WORK&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 22:53:32 GMT</pubDate>
    <dc:creator>prashantrecon</dc:creator>
    <dc:date>2019-03-11T22:53:32Z</dc:date>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889066#M457076</link>
      <description>&lt;P&gt;L3 sitch is connected to firewall and firewall is connected to router&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on l3 network 10.0.0.0/24&lt;/P&gt;&lt;P&gt;172.16.0.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and default route is to firewall&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;from firewall default route is&amp;nbsp; ROUTE OUTSIDE 0.0.0.0 0.0.0.0 202.x.x.x(router)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&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 another router my requirement is i want 172.16.0.0 /24 data should go through this router(124.x.x.x)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;iF I GIVE THE ROUTE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ROUTE OUTSIDE 172.16.X.X 255.255.255.0 124.X.X.X ON FIREWALL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;THUS IT WORK&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:53:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889066#M457076</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2019-03-11T22:53:32Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889067#M457081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kumar, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all you must keep in mind that the traditional routing is made using destination address.&lt;/P&gt;&lt;P&gt;So taking this into consideration your firewall will make the routing decisions based on destination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As an short answer : no will not work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The solution is PBR , but sadly I do not think this feature is supported on ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 08:17:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889067#M457081</guid>
      <dc:creator>Dan-Ciprian Cicioiu</dc:creator>
      <dc:date>2012-04-13T08:17:25Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889068#M457088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i use another interface of firewall name it as outside1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;than route the traffic route outside1 172.16.x.x 255.255.0.0 124.x.x.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;will it work?&amp;nbsp; is there&amp;nbsp; any other solution ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 08:41:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889068#M457088</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-13T08:41:02Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889069#M457093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My understanding regarding your setup is :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;L3 switch ------- ASA -------- ROUTER &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;172.16.0.0/24 is connected to the L3 switch.&lt;/P&gt;&lt;P&gt;Is that correct ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 08:46:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889069#M457093</guid>
      <dc:creator>Dan-Ciprian Cicioiu</dc:creator>
      <dc:date>2012-04-13T08:46:48Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889070#M457097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;l3--asa--l2switch --router&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;all theports of l2 switch are in same vlan &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 08:48:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889070#M457097</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-13T08:48:44Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889071#M457102</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And where is connected the 172.16.0.0/24 network ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 08:49:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889071#M457102</guid>
      <dc:creator>Dan-Ciprian Cicioiu</dc:creator>
      <dc:date>2012-04-13T08:49:59Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889072#M457105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;on l3 switch&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 09:42:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889072#M457105</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-13T09:42:01Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889073#M457107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok.&lt;/P&gt;&lt;P&gt;As I see it , and taking into consideration that ASA does not suport PBR, the solution must involve PBR but on other equipments :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) after the firewall - on the router - this involves connecting the second router to the first router and also access to the routers in order to configure PBR&lt;/P&gt;&lt;P&gt;2) before the firewall - on the L3 switch - this involves creating 2 contexts on the firewall 1 for the first connection (router) , and the second for the second connection (router), and also PBR on the L3 switch in order to route the traffic coming from 172.16.0.0/24 to the second router/connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 2nd fits you better, because I do not think that you have access to the routers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 09:52:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889073#M457107</guid>
      <dc:creator>Dan-Ciprian Cicioiu</dc:creator>
      <dc:date>2012-04-13T09:52:00Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889074#M457114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding 2 solution can u give rough idea regarding scenario or any doc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 09:56:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889074#M457114</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-13T09:56:59Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889075#M457119</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;L3 switch&lt;/STRONG&gt; ----access ---- &lt;STRONG&gt;ASA&lt;/STRONG&gt; ------ trunk ----- &lt;STRONG&gt;L2 switch&lt;/STRONG&gt; ---- access vlan 2 ----&amp;nbsp; old &lt;STRONG&gt;router&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&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;&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; |-------------access vlan 3--------- new router&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;=&amp;gt;&amp;nbsp; L2 switch - you should create a separated vlan for the second connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;L2 switch : let's consider vlans : 2 old router vlan&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3 new router vlan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;=&amp;gt; ASA&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;ASA : interfaces E0 (inside) , E1 (outside)&lt;/P&gt;&lt;P&gt;Phisical :&amp;nbsp; interface E1 , should be configured with subinterfaces&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; E1.2 ----&amp;gt; old router vlan&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; E1.3 ----&amp;gt; new router vlan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;context ONE : interface E0 - inside - &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; interface E1.2 - outside - 202.x.x.x address&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; default route to the old router - 202.x.x.x&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; specific routes to the L3 switch - 172.16.0.0/24 , 10.0.0.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;context TWO : interface E0 - inside -&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; interface E1.3 - outside - 124.x.x.x address&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; default route to the new router 124.x.x.x&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; specific routes to the L3 switch&amp;nbsp; 172.16.0.0/24 , 10.0.0.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;=&amp;gt; L3 Switch &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;default route to the IP of the ASA Context ONE&lt;/P&gt;&lt;P&gt;PBR for the traffic sourced 172.16.0.0/24 next-hop the IP of the ASA Context TWO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 10:17:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889075#M457119</guid>
      <dc:creator>Dan-Ciprian Cicioiu</dc:creator>
      <dc:date>2012-04-13T10:17:57Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889076#M457123</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;THanks very much.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One last question i think it will we better if i another interface on firewall .and name it as outside1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And than route the traffic for that partcular valn through that outside1 interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thus it work ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 10:45:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889076#M457123</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-13T10:45:56Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889077#M457125</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No will not work for what you want to achieve.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why ? When you configure the route on the ASA as you first posted :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ROUTE OUTSIDE1 172.16.X.X 255.255.255.0 124.X.X.X&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will instruct the ASA to route all the traffic GOING ( this means having the destination ) to 172.16.0.0/24 to the OUTSIDE1 interface.This will never happen, because the 172.16.0.0 is on the L3 switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you will need to source route - meaning that you will need to route &lt;STRONG&gt;not after destination&lt;/STRONG&gt; but&lt;STRONG&gt; after source&lt;/STRONG&gt; ( using Policy Based Routing ) , in order to route the traffic sourced by 172.16.0.0/24 to the second router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 11:00:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889077#M457125</guid>
      <dc:creator>Dan-Ciprian Cicioiu</dc:creator>
      <dc:date>2012-04-13T11:00:38Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889078#M457128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am confused.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;from l3 there is dfault route to firewaall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and from firewall there is default route&amp;nbsp; to router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now from l3 all the traffic will first reach firewall .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on firewall ther are two outside interface otside 1 and outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for outside 1 i will provide ip&amp;nbsp; as in same range of 124.x.x.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so for 172.16.x.x i will route as route inside 172.16.x.x 255.255.255.0 172.16.x.1(vlan ip created on l3 as svi)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on firewall&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside1 172.16..x.x 255.255.255.0 124.x.x.x(ip of secound router)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so it will work or not.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 11:24:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889078#M457128</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-13T11:24:28Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889079#M457130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"route outside1 172.16..x.x 255.255.255.0 124.x.x.x"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this command tells the equipment where is the 172.16.x.x 255.255.255.0. Not where to send the traffic for that prefix.&lt;/P&gt;&lt;P&gt; So you are telling the ASA that the 172.16.x.x 255.255.255.0 is located on the outside1 interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To answer your question : no , will not work&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 11:52:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889079#M457130</guid>
      <dc:creator>Dan-Ciprian Cicioiu</dc:creator>
      <dc:date>2012-04-13T11:52:25Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889080#M457133</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;You are right&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now if i want to route 172.16.x.x traffic to outside 1 interface .how can i make it possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i do not want to nat this traffic...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 14:33:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889080#M457133</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-13T14:33:05Z</dc:date>
    </item>
    <item>
      <title>routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889081#M457135</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What type of access does those two routers offer ? Internet&amp;nbsp; ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2012 15:06:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889081#M457135</guid>
      <dc:creator>Dan-Ciprian Cicioiu</dc:creator>
      <dc:date>2012-04-13T15:06:09Z</dc:date>
    </item>
    <item>
      <title>Re: routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889082#M457136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My requirement is like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i want to use router 1(bgp is runing)&amp;nbsp; for internet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and i want to use router 2(bgp is runing) for many site to site vpn.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have a apnic range that i want to use in both router 1 and 2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now requirement is like i want to use firewall in any case (for security reason all traffic router 1 and router should go through firewall))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now i want to make a site to site vpn with this 172.16.x.x lan on router 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thats why i am asking how to route 172.16.x.x range to router 2 on firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;﻿please find the attahment&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Apr 2012 03:46:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889082#M457136</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-14T03:46:28Z</dc:date>
    </item>
    <item>
      <title>Re: routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889083#M457137</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Prashant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Long time no see..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you know the ASA does not support PBR and can have only one default route on on its routing table..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what I would&amp;nbsp; like to know if its the both routers and the ASA are on the same broadcast domain???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If they are you could configure a default route pointing ro R1 and then create a route pointing to R2 with the subnet network on the other side of the VPN tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That should do it!!&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;DO rate all the helpful posts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Apr 2012 04:22:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889083#M457137</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-04-14T04:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889084#M457138</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your concern &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firewall ,router 1 and router 2 are in same broadcast domain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please share an example&amp;nbsp; regarding your suggestion &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prashant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Apr 2012 06:37:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889084#M457138</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-14T06:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: routing on asa</title>
      <link>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889085#M457139</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Prashant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks really simple to me unless I am not understanding this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You want to send all traffic to the x.x.x.x. (vpn destination) subnet to router 2 and all the internet traffic to router 1 so all you need on the ASA&lt;/P&gt;&lt;P&gt;is a nat 0 ACL for the traffic going to the vpn subnet and the regular nat and global for the internet&lt;/P&gt;&lt;P&gt;Then for the routes you need&lt;/P&gt;&lt;P&gt;route outside 0 0 R1_Ip&lt;/P&gt;&lt;P&gt;route outside x.x.x.x x.x.x.x.x R2_IP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;that's all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DO Rate all the helpful posts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Apr 2012 07:16:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-on-asa/m-p/1889085#M457139</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-04-14T07:16:04Z</dc:date>
    </item>
  </channel>
</rss>

