<?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 Re: Routing between contexts in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576688#M657832</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you are absolutely correct. There needs to be at least 1 shared interface to route traffic between context.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Sep 2010 05:46:27 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2010-09-21T05:46:27Z</dc:date>
    <item>
      <title>Routing between contexts</title>
      <link>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576685#M657695</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 contexts, and i want to route between the contexts. Is that possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CONTEXT 1&lt;/P&gt;&lt;P&gt;==========&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OUTSIDE IP - 10.10.10.0&lt;/P&gt;&lt;P&gt;INSIDE IP - 192.168.20.0&lt;/P&gt;&lt;P&gt;DMZ IP - 192.168.30.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Static NAT ON OUTSIDE IP to DMZ - 100.100.100.100 - .105&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CONTEXT 2&lt;/P&gt;&lt;P&gt;=========&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OUTSIDE IP - 10.20.20.20&lt;/P&gt;&lt;P&gt;INSIDE IP - 192.168.40.0&lt;/P&gt;&lt;P&gt;DMZ IP - 192.168.41.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Static NAT on OUTSIDE IP to DMZ - 4.2.2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to route traffic between context 2 DMZ IP to static NAT on CONTEXT 1?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What do i need to add on the contexts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sid&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:42:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576685#M657695</guid>
      <dc:creator>sidcracker</dc:creator>
      <dc:date>2019-03-11T18:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: Routing between contexts</title>
      <link>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576686#M657764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You would need to have at least one shared interface to be able to route traffic between context. What you are trying to achieve is called cascading security context and here is the diagram for your reference:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/contexts.html#wp1146927"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/contexts.html#wp1146927&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case, since there is no shared interface between the 2 contexts, you can't route traffic between the 2 contexts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Sep 2010 05:35:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576686#M657764</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-09-21T05:35:10Z</dc:date>
    </item>
    <item>
      <title>Re: Routing between contexts</title>
      <link>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576687#M657798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Halijenn,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As of now I have only 2 contexts which are using shared outside interfaces and they are able to ping each other. The other context which has a unique interface cannot access the other context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So there is no way that I can access it correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Sep 2010 05:37:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576687#M657798</guid>
      <dc:creator>sidcracker</dc:creator>
      <dc:date>2010-09-21T05:37:42Z</dc:date>
    </item>
    <item>
      <title>Re: Routing between contexts</title>
      <link>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576688#M657832</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you are absolutely correct. There needs to be at least 1 shared interface to route traffic between context.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Sep 2010 05:46:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-between-contexts/m-p/1576688#M657832</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-09-21T05:46:27Z</dc:date>
    </item>
  </channel>
</rss>

