<?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 How to move data transparently from one security 100 interface to another security 100 interface. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-to-move-data-transparently-from-one-security-100-interface/m-p/2684461#M192067</link>
    <description>&lt;P&gt;I have an ASA 5505 with an inside network configured normally plus another security level 100 network we call 'transit'. &amp;nbsp;Data flow is enabled across the interfaces, and it does work, but in order to get communications between hosts on each side, I have to add routing statements manually on the host systems. &amp;nbsp;For example, a Windows host on the 'transit' network has to have a 'Route Add' statement run on it in order to respond to traffic from&amp;nbsp;the 'inside' network, and vice-versa. &amp;nbsp;Once the statements are added on both sides, the traffic works fine. &amp;nbsp;I'm not able to add a static route on&amp;nbsp;the ASA to&amp;nbsp;the 'transit' network, for example, if I try I get an error in the GUI client that it is a connected network and can't have a static route to it. &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there some way to configure the ASA to move the traffic between the two segments without having to use the route add statements on the hosts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:52:15 GMT</pubDate>
    <dc:creator>cgarrison2</dc:creator>
    <dc:date>2019-03-12T05:52:15Z</dc:date>
    <item>
      <title>How to move data transparently from one security 100 interface to another security 100 interface.</title>
      <link>https://community.cisco.com/t5/network-security/how-to-move-data-transparently-from-one-security-100-interface/m-p/2684461#M192067</link>
      <description>&lt;P&gt;I have an ASA 5505 with an inside network configured normally plus another security level 100 network we call 'transit'. &amp;nbsp;Data flow is enabled across the interfaces, and it does work, but in order to get communications between hosts on each side, I have to add routing statements manually on the host systems. &amp;nbsp;For example, a Windows host on the 'transit' network has to have a 'Route Add' statement run on it in order to respond to traffic from&amp;nbsp;the 'inside' network, and vice-versa. &amp;nbsp;Once the statements are added on both sides, the traffic works fine. &amp;nbsp;I'm not able to add a static route on&amp;nbsp;the ASA to&amp;nbsp;the 'transit' network, for example, if I try I get an error in the GUI client that it is a connected network and can't have a static route to it. &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there some way to configure the ASA to move the traffic between the two segments without having to use the route add statements on the hosts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:52:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-move-data-transparently-from-one-security-100-interface/m-p/2684461#M192067</guid>
      <dc:creator>cgarrison2</dc:creator>
      <dc:date>2019-03-12T05:52:15Z</dc:date>
    </item>
    <item>
      <title>You can add static routes on</title>
      <link>https://community.cisco.com/t5/network-security/how-to-move-data-transparently-from-one-security-100-interface/m-p/2684462#M192068</link>
      <description>&lt;P&gt;You can add static routes on the clients' normal gateway(s).&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2015 21:15:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-move-data-transparently-from-one-security-100-interface/m-p/2684462#M192068</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-04-30T21:15:12Z</dc:date>
    </item>
  </channel>
</rss>

