<?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 Using an ASA as a router in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033572#M1109596</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;the question is in the title.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it possible to use the ASA as a router between 2 internal networks?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/1&lt;BR /&gt;nameif outside&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.0.1.254 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;interface GigabitEthernet1/2&lt;BR /&gt;nameif inside&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.40.1.249 255.255.255.0&lt;/P&gt;&lt;P&gt;"outside" interface, connected to an L2 switch.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;A PC ( PC1) is connected to this switch&lt;/P&gt;&lt;P&gt;10.0.1.110 255.255.255.0 GW : 10.01.254&lt;/P&gt;&lt;P&gt;The "inside" interface is also connected to an L2 switch, to which PCs are connected. These PCs have IP 10.40.1.X /24 and Gateway 10.40.1.254. This gateway is the IP of the ISP router (VPN MPLS router).&lt;/P&gt;&lt;P&gt;From the "inside" network, I need to retrieve FTP data on PC1. And allow ICMP too. Same thing in reverse (from outside to inside).&lt;/P&gt;&lt;P&gt;But the problem is that if I add a route on the ASA, it asks me to configure the next hop Ip address. But in this diagram, I don't have one?&lt;/P&gt;&lt;P&gt;The goal is to isolate PC1. A laboratory analyzer is connected to this PC (PC not supplied by us). It sends data to this PC, and I can retrieve data via FTp on it to send it to the inside network.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 04 Mar 2024 12:02:17 GMT</pubDate>
    <dc:creator>abtt-39</dc:creator>
    <dc:date>2024-03-04T12:02:17Z</dc:date>
    <item>
      <title>Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033572#M1109596</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;the question is in the title.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it possible to use the ASA as a router between 2 internal networks?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/1&lt;BR /&gt;nameif outside&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.0.1.254 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;interface GigabitEthernet1/2&lt;BR /&gt;nameif inside&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.40.1.249 255.255.255.0&lt;/P&gt;&lt;P&gt;"outside" interface, connected to an L2 switch.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;A PC ( PC1) is connected to this switch&lt;/P&gt;&lt;P&gt;10.0.1.110 255.255.255.0 GW : 10.01.254&lt;/P&gt;&lt;P&gt;The "inside" interface is also connected to an L2 switch, to which PCs are connected. These PCs have IP 10.40.1.X /24 and Gateway 10.40.1.254. This gateway is the IP of the ISP router (VPN MPLS router).&lt;/P&gt;&lt;P&gt;From the "inside" network, I need to retrieve FTP data on PC1. And allow ICMP too. Same thing in reverse (from outside to inside).&lt;/P&gt;&lt;P&gt;But the problem is that if I add a route on the ASA, it asks me to configure the next hop Ip address. But in this diagram, I don't have one?&lt;/P&gt;&lt;P&gt;The goal is to isolate PC1. A laboratory analyzer is connected to this PC (PC not supplied by us). It sends data to this PC, and I can retrieve data via FTp on it to send it to the inside network.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 12:02:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033572#M1109596</guid>
      <dc:creator>abtt-39</dc:creator>
      <dc:date>2024-03-04T12:02:17Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033577#M1109597</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1270425"&gt;@abtt-39&lt;/a&gt; you can either change the routing on your to make the ASA the next hop, you would also need to configure an ACL to explictly permit the traffic between the interfaces.&lt;/P&gt;
&lt;P&gt;Or you could configure the ASA in transparent mode - &lt;A href="https://integratingit.wordpress.com/2021/05/30/asa-transparent-mode/" target="_blank"&gt;https://integratingit.wordpress.com/2021/05/30/asa-transparent-mode/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 12:13:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033577#M1109597</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-04T12:13:09Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033585#M1109598</link>
      <description>&lt;P&gt;Hello rob,&lt;/P&gt;&lt;P&gt;Unfortunately, on the inside station, I cannot change the gateway to ASA. These PCs need their current gateway to access the MPLS VPN network between sites.&lt;/P&gt;&lt;P&gt;For transparent mode, I didn't know, but in the link indicated, it is written that switching to transparent mode will erase the ASA configuration. However, I also use it for other things not mentioned in my post&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 12:41:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033585#M1109598</guid>
      <dc:creator>abtt-39</dc:creator>
      <dc:date>2024-03-04T12:41:04Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033586#M1109599</link>
      <description>&lt;P&gt;I believe that you don´t need to configure static routes, due both network is directly connected to the ASA.&lt;BR /&gt;But is needed traffic permits between both security zones.&lt;BR /&gt;&lt;BR /&gt;Kind regards&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 12:52:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033586#M1109599</guid>
      <dc:creator>Edgar Benavente</dc:creator>
      <dc:date>2024-03-04T12:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033587#M1109600</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1270425"&gt;@abtt-39&lt;/a&gt; without knowing your topology I see no reason why you cannot change the routing on the LAN. Or alternatively create another network behind the ASA and route accordingly. Or depending on your ASA hardware you could convert to ASA Multi-context, 1 using your existing routed configuration and another context as transparent.&lt;/P&gt;
&lt;P&gt;I'd recommend you look to change your LAN topology to route between the different networks.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 12:54:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033587#M1109600</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2024-03-04T12:54:34Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033599#M1109601</link>
      <description>&lt;P&gt;From what you are describing you want to use FTP between two devices that have IPs in the same subnet as the Inside and Outside interfaces?&amp;nbsp; If this is the case then no routing is needed as these are "directly connected" subnets, the ASA already knows how to reach these networks.&amp;nbsp; So all that is needed is that the PCs need either a default gateway or a route for the PC in question pointing to the relevant ASA interface and access rules allowing the FTP connection (if using active FTP you will need to open for both tcp/20 and tcp/21).&lt;/P&gt;
&lt;P&gt;As for ICMP, as this is stateless you will need to add an inspect icmp command under the global policy-map configuration as well as allow this in the access list.&lt;/P&gt;
&lt;P&gt;policy-map global_policy&lt;/P&gt;
&lt;P&gt;&amp;nbsp; class inspeciton_default&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; inspect icmp&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 13:14:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033599#M1109601</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-03-04T13:14:19Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033607#M1109602</link>
      <description>&lt;P&gt;&lt;BR /&gt;I'm attaching a little diagram, it will be easier.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ld.JPG" style="width: 845px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/211673i237481695C2A355B/image-size/large?v=v2&amp;amp;px=999" role="button" title="ld.JPG" alt="ld.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 13:28:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033607#M1109602</guid>
      <dc:creator>abtt-39</dc:creator>
      <dc:date>2024-03-04T13:28:28Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033615#M1109603</link>
      <description>&lt;P&gt;LOL, never mind the last comment, I see it is a L2 switch.&amp;nbsp; In this case you would need to implement static routes on PC2 to point to the ASA for network 10.0.1.0/24.&amp;nbsp; Also, you still need the access list entries to allow access for FTP as well as inspect ICMP in the global policy map.&lt;/P&gt;
&lt;P&gt;Or place an L3 device between PC2 and the ISP and the rest of the internal network.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 13:45:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033615#M1109603</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-03-04T13:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033617#M1109604</link>
      <description>&lt;P&gt;it's already the case :&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;BR /&gt;class inspection_default&lt;BR /&gt;inspect ftp&lt;BR /&gt;inspect h323 h225&lt;BR /&gt;inspect h323 ras&lt;BR /&gt;inspect ip-options&lt;BR /&gt;inspect netbios&lt;BR /&gt;inspect rsh&lt;BR /&gt;inspect rtsp&lt;BR /&gt;inspect skinny&lt;BR /&gt;inspect esmtp&lt;BR /&gt;inspect sqlnet&lt;BR /&gt;inspect sunrpc&lt;BR /&gt;inspect tftp&lt;BR /&gt;inspect sip&lt;BR /&gt;inspect xdmcp&lt;BR /&gt;inspect dns preset_dns_map&lt;BR /&gt;inspect icmp&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and i can't ping&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 13:46:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033617#M1109604</guid>
      <dc:creator>abtt-39</dc:creator>
      <dc:date>2024-03-04T13:46:05Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033618#M1109605</link>
      <description>&lt;P&gt;go a head use FW as router&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but I want to mention that we normally named the Interface connect to ISP OUTSIDE and level 0&lt;BR /&gt;and interface connect to LAN as INSIDE and level 100&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 13:46:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033618#M1109605</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-04T13:46:08Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033619#M1109606</link>
      <description>&lt;P&gt;If you will use the ASA as a router you would need to provision a new subnet for PC2 as you will end up with asynchronous routing towards the ISP if left as is.&amp;nbsp; Or configure tcp bypass on the ASA, but I would not recommend going that direction.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 13:48:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033619#M1109606</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-03-04T13:48:42Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033629#M1109607</link>
      <description>&lt;P&gt;You are totally correct&amp;nbsp;&lt;BR /&gt;the traffic path will be&amp;nbsp;&lt;BR /&gt;PC2-&amp;gt;ISP-&amp;gt;ASA-&amp;gt;PC1&lt;BR /&gt;the return will be&amp;nbsp;&lt;BR /&gt;PC1-&amp;gt;ASA-&amp;gt;PC2 (since ASA and PC2 share same subnet)&lt;BR /&gt;&lt;BR /&gt;So He can use ASA as router but he need&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ld.JPG" style="width: 845px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/211677i5D8904D3B400D672/image-size/large?v=v2&amp;amp;px=999" role="button" title="ld.JPG" alt="ld.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 13:56:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033629#M1109607</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-04T13:56:30Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033641#M1109609</link>
      <description>&lt;P&gt;Indeed, it seemed to me that it was not possible as shown in the diagram without a router somewhere.&lt;BR /&gt;I'm going to try adding a static route on a PC (it's a Windows PC), I've never tried it on Windows.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 14:09:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033641#M1109609</guid>
      <dc:creator>abtt-39</dc:creator>
      <dc:date>2024-03-04T14:09:04Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033711#M1109612</link>
      <description>&lt;P&gt;it work not issue&amp;nbsp;&lt;/P&gt;
&lt;P&gt;NOTE:- R2 in my lab is pure L2 SW.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot (143).png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/211689i79A5895AAC98A1CA/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot (143).png" alt="Screenshot (143).png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot (144).png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/211688i2B2B4B09F1AD9455/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot (144).png" alt="Screenshot (144).png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 16:17:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5033711#M1109612</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-03-04T16:17:11Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195834#M1115887</link>
      <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;I'm re-uploading this post because I haven't worked on this problem again.&lt;/P&gt;&lt;P&gt;If I put the diagram back, it has evolved. A commenter added 2 routers/firewalls (not managed by us), 201 and 202&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Capture d’écran 2024-09-18 114827.jpg" style="width: 744px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/229353i2FF65E243777698D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Capture d’écran 2024-09-18 114827.jpg" alt="Capture d’écran 2024-09-18 114827.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;From a pc on the 10.40.1.0 network, I can ping 10.0.0.50&lt;/P&gt;&lt;P&gt;On this PC 10.0.0.50, there is a local web server in https&lt;/P&gt;&lt;P&gt;I would like to be able to access this local web server from a computer on the 10.40.1.0 network&lt;/P&gt;&lt;P&gt;&lt;A href="https://10.0.0.50/" target="_blank"&gt;https://10.0.0.50/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;ERR_CONNECTION_REFUSED&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gateway of last resort is 10.40.1.254 to network 0.0.0.0&lt;/P&gt;&lt;P&gt;S* 0.0.0.0 0.0.0.0 [1/0] via 10.40.1.254, inside&lt;BR /&gt;S 10.0.0.1 255.255.255.255 [1/0] via 10.0.1.253, outside&lt;BR /&gt;S 10.0.0.10 255.255.255.255 [1/0] via 10.0.1.252, outside&lt;BR /&gt;S 10.0.0.20 255.255.255.255 [1/0] via 10.0.1.253, outside&lt;BR /&gt;S 10.0.0.50 255.255.255.255 [1/0] via 10.0.1.253, outside&lt;BR /&gt;S 10.0.0.101 255.255.255.255 [1/0] via 10.0.1.253, outside&lt;BR /&gt;C 10.0.1.0 255.255.255.0 is directly connected, outside&lt;BR /&gt;S 10.0.1.5 255.255.255.255 [1/0] via 10.0.1.251, outside&lt;BR /&gt;L 10.0.1.254 255.255.255.255 is directly connected, outside&lt;BR /&gt;S 10.39.1.0 255.255.255.0 [1/0] via 10.40.1.254, inside&lt;BR /&gt;C 10.40.1.0 255.255.255.0 is directly connected, inside&lt;BR /&gt;L 10.40.1.249 255.255.255.255 is directly connected, inside&lt;BR /&gt;S 10.239.11.0 255.255.255.0 [1/0] via 10.40.1.254, inside&lt;/P&gt;&lt;P&gt;In this topology, I have 2 networks connected directly to the ASA, and a 3rd, not directly connected 10.0.0.0/24&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;with packet tracer :&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#packet-tracer input inside tcp 10.40.1.4 12345 10.0.0.50 443&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Phase: 1&lt;BR /&gt;Type: ROUTE-LOOKUP&lt;BR /&gt;Subtype: Resolve Egress Interface&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;BR /&gt;found next-hop 10.0.1.253 using egress ifc outside&lt;/P&gt;&lt;P&gt;Phase: 2&lt;BR /&gt;Type: ACCESS-LIST&lt;BR /&gt;Subtype: log&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;access-group inside_access in interface inside&lt;BR /&gt;access-list inside_access extended permit object-group DM_INLINE_SERVICE_4 object inside-network 10.0.0.0 255.255.255.0&lt;BR /&gt;object-group service DM_INLINE_SERVICE_4&lt;BR /&gt;service-object udp&lt;BR /&gt;service-object tcp destination eq https&lt;BR /&gt;service-object tcp destination eq www&lt;BR /&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Phase: 3&lt;BR /&gt;Type: NAT&lt;BR /&gt;Subtype:&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;object network obj_any&lt;BR /&gt;nat (any,outside) dynamic interface&lt;BR /&gt;Additional Information:&lt;BR /&gt;Dynamic translate 10.40.1.4/12345 to 10.0.1.254/12345&lt;/P&gt;&lt;P&gt;Phase: 4&lt;BR /&gt;Type: NAT&lt;BR /&gt;Subtype: per-session&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Phase: 5&lt;BR /&gt;Type: IP-OPTIONS&lt;BR /&gt;Subtype:&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Phase: 6&lt;BR /&gt;Type: FOVER&lt;BR /&gt;Subtype: standby-update&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Phase: 7&lt;BR /&gt;Type: NAT&lt;BR /&gt;Subtype: per-session&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Phase: 8&lt;BR /&gt;Type: IP-OPTIONS&lt;BR /&gt;Subtype:&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;/P&gt;&lt;P&gt;Phase: 9&lt;BR /&gt;Type: FLOW-CREATION&lt;BR /&gt;Subtype:&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;BR /&gt;New flow created with id 223558, packet dispatched to next module&lt;/P&gt;&lt;P&gt;Phase: 10&lt;BR /&gt;Type: ROUTE-LOOKUP&lt;BR /&gt;Subtype: Resolve Egress Interface&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;BR /&gt;found next-hop 10.0.1.253 using egress ifc outside&lt;/P&gt;&lt;P&gt;Phase: 11&lt;BR /&gt;Type: ADJACENCY-LOOKUP&lt;BR /&gt;Subtype: next-hop and adjacency&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;BR /&gt;adjacency Active&lt;BR /&gt;next-hop mac address 0008.da79.1d1e hits 0 reference 1&lt;/P&gt;&lt;P&gt;Result:&lt;BR /&gt;input-interface: inside&lt;BR /&gt;input-status: up&lt;BR /&gt;input-line-status: up&lt;BR /&gt;output-interface: outside&lt;BR /&gt;output-status: up&lt;BR /&gt;output-line-status: up&lt;BR /&gt;Action: allow&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#PING from 10.40.1.4 to 10.0.0.50 = OK&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Traceroute from 10.40.1.4 to 10.0.0.50 = OK&lt;/STRONG&gt;&lt;BR /&gt;1 &amp;lt;1 ms &amp;lt;1 ms &amp;lt;1 ms 10.40.1.254&lt;BR /&gt;2 4 ms 3 ms 3 ms 10.0.1.253&lt;BR /&gt;3 4 ms 4 ms 4 ms 10.0.0.50&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;# sh nat detail&lt;/STRONG&gt;&lt;BR /&gt;Auto NAT Policies (Section 2)&lt;BR /&gt;1 (any) to (outside) source dynamic obj_any interface&lt;BR /&gt;translate_hits = 3389, untranslate_hits = 9874&lt;BR /&gt;Source - Origin: 0.0.0.0/0, Translated: 10.0.1.254/24&lt;/P&gt;&lt;P&gt;In terms of nat, I'm not sure?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 12:08:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195834#M1115887</guid>
      <dc:creator>abtt-39</dc:creator>
      <dc:date>2024-09-18T12:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195863#M1115889</link>
      <description>&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Yes, you can use the ASA as a router between two internal networks. Set up bidirectional access rules allowing ICMP and FTP traffic between the "outside" and "inside" networks. Since you don’t have a next hop, you can use route statements with the connected interfaces. Make sure the ASA’s NAT and access lists are properly configured to ensure smooth communication between PC1 and the inside network.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Sep 2024 13:00:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195863#M1115889</guid>
      <dc:creator>alexcarry1044</dc:creator>
      <dc:date>2024-09-18T13:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195894#M1115892</link>
      <description>&lt;P&gt;First I am busy these day so my reply maybe delay' that OK for you?&lt;/P&gt;
&lt;P&gt;Now&lt;/P&gt;
&lt;P&gt;Same Subnet 10.0.0.0/24 connect to two routers and ASA ?&lt;/P&gt;
&lt;P&gt;That wrong.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 13:52:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195894#M1115892</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-09-18T13:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195911#M1115893</link>
      <description>&lt;P&gt;yes.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 14:19:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195911#M1115893</guid>
      <dc:creator>abtt-39</dc:creator>
      <dc:date>2024-09-18T14:19:36Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195912#M1115894</link>
      <description>&lt;P&gt;Currently, I have not specified it, but ping and ftp are functional between the inside network and the 10.0.0.0/24 network, it is https which is not. But as the diagram shows, there is a router in the architecture that is not managed by us. This week, a technician from this company is coming, I will ask him to check.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 14:20:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195912#M1115894</guid>
      <dc:creator>abtt-39</dc:creator>
      <dc:date>2024-09-18T14:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: Using an ASA as a router</title>
      <link>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195915#M1115895</link>
      <description>&lt;P&gt;If Yes you use same subnet then static route or igp not help here.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You need to use different subnet&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 14:34:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-an-asa-as-a-router/m-p/5195915#M1115895</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-09-18T14:34:56Z</dc:date>
    </item>
  </channel>
</rss>

