<?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 ASA routing with two different interfaces in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-routing-with-two-different-interfaces/m-p/2163743#M359598</link>
    <description>&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; I am running into an issue where I need to be able to access the management interface from a subnet of 10.170.2.0/23, but then I also have to add this subnet to the inside interface so my computer can get out to the internet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It complains when I have the same route on two different interfaces? How do I get around this?&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:18:38 GMT</pubDate>
    <dc:creator>Steven Williams</dc:creator>
    <dc:date>2019-03-12T01:18:38Z</dc:date>
    <item>
      <title>ASA routing with two different interfaces</title>
      <link>https://community.cisco.com/t5/network-security/asa-routing-with-two-different-interfaces/m-p/2163743#M359598</link>
      <description>&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; I am running into an issue where I need to be able to access the management interface from a subnet of 10.170.2.0/23, but then I also have to add this subnet to the inside interface so my computer can get out to the internet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It complains when I have the same route on two different interfaces? How do I get around this?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:18:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-routing-with-two-different-interfaces/m-p/2163743#M359598</guid>
      <dc:creator>Steven Williams</dc:creator>
      <dc:date>2019-03-12T01:18:38Z</dc:date>
    </item>
    <item>
      <title>ASA routing with two different interfaces</title>
      <link>https://community.cisco.com/t5/network-security/asa-routing-with-two-different-interfaces/m-p/2163744#M359599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can't really "bypass" this behavior because you are basically adding a static route for a network that is directly connected to the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your concern is about how to manage the device from an interface different from the "management" one, i can tell you that you can enable management protocols on any of the unit's interfaces. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Mar 2013 18:22:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-routing-with-two-different-interfaces/m-p/2163744#M359599</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-03-23T18:22:46Z</dc:date>
    </item>
  </channel>
</rss>

