<?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 Route inside traffic out management interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/route-inside-traffic-out-management-interface/m-p/2902835#M158613</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have a need to temporarily route inside traffic out a management0/0 interface on a Cisco ASA.&amp;nbsp;ASA5525&amp;nbsp;Version 9.1(6)10.&lt;/P&gt;
&lt;P&gt;Basically there is a network off the management interface that inside users need to get to.&lt;/P&gt;
&lt;P&gt;So if I do a "route management 10.10.10.0&amp;nbsp;255.255.255.0 &amp;nbsp;10.95.95.10"&lt;/P&gt;
&lt;P&gt;Will the traffic from inside interface be able to travers out the management0/0 interface to the 10.10.10.0/24 network?&lt;/P&gt;
&lt;P&gt;I do have this enabled =&amp;nbsp;same-security-traffic permit inter-interface&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;If I can do this. Then, can I nat inside traffic out the management0/0 interface? And if so, what nat commands would i be able to use to source nat to the management interface?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 07:27:47 GMT</pubDate>
    <dc:creator>christians1</dc:creator>
    <dc:date>2019-03-12T07:27:47Z</dc:date>
    <item>
      <title>Route inside traffic out management interface</title>
      <link>https://community.cisco.com/t5/network-security/route-inside-traffic-out-management-interface/m-p/2902835#M158613</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have a need to temporarily route inside traffic out a management0/0 interface on a Cisco ASA.&amp;nbsp;ASA5525&amp;nbsp;Version 9.1(6)10.&lt;/P&gt;
&lt;P&gt;Basically there is a network off the management interface that inside users need to get to.&lt;/P&gt;
&lt;P&gt;So if I do a "route management 10.10.10.0&amp;nbsp;255.255.255.0 &amp;nbsp;10.95.95.10"&lt;/P&gt;
&lt;P&gt;Will the traffic from inside interface be able to travers out the management0/0 interface to the 10.10.10.0/24 network?&lt;/P&gt;
&lt;P&gt;I do have this enabled =&amp;nbsp;same-security-traffic permit inter-interface&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;If I can do this. Then, can I nat inside traffic out the management0/0 interface? And if so, what nat commands would i be able to use to source nat to the management interface?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:27:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/route-inside-traffic-out-management-interface/m-p/2902835#M158613</guid>
      <dc:creator>christians1</dc:creator>
      <dc:date>2019-03-12T07:27:47Z</dc:date>
    </item>
    <item>
      <title>You will also need to issue</title>
      <link>https://community.cisco.com/t5/network-security/route-inside-traffic-out-management-interface/m-p/2902836#M158618</link>
      <description>&lt;P&gt;You will also need to issue the command "no management-only" to allow the management port to forward data traffic.&lt;/P&gt;
&lt;P&gt;Also, keep in mind that once you apply an ACL to the interface then security levels are no longer in effect (until you remove the ACL again). &amp;nbsp;So if you do have ACLs configured on the inside interface then make sure to allow this traffic there.&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;Please remember to select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Thu, 10 Mar 2016 05:32:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/route-inside-traffic-out-management-interface/m-p/2902836#M158618</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2016-03-10T05:32:06Z</dc:date>
    </item>
  </channel>
</rss>

