<?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  Multiple context sharing Outside interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-multiple-context-sharing-outside-interface/m-p/2223937#M347964</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think by default when you configure the ASA in Multiple Context mode and have a shared interface between 2 Security Contexts then both of the interfaces will use the same MAC address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In those cases I assume that the ASA uses existing NAT configurations or IP addresses configured on the ASA interfaces to determine which is the correct Security Content to which the traffic needs to be forwarded to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It should work as long as the IP address configured on the interface is different. Naturally if the NAT configurations also play a role as I said.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With regards to the second setup. I would imagine that this is actually the preferred way. That each contexts shared interface has a unique MAC address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check this section of the 8.2 configuration guide&lt;/P&gt;&lt;P&gt;&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#wp1146806"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/contexts.html#wp1146806&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 16 Jun 2013 22:07:17 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-06-16T22:07:17Z</dc:date>
    <item>
      <title>ASA  Multiple context sharing Outside interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-sharing-outside-interface/m-p/2223936#M347962</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have question regarding the ASA&amp;nbsp; when working as multiple context mode.&lt;/P&gt;&lt;P&gt;If output interface is shared by two contexts and both&amp;nbsp; have different IP&amp;nbsp; address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible that outside shared interface can have same mac address for both the contexts?&lt;/P&gt;&lt;P&gt;Will the Setup work if outside interface is shared and also configured&amp;nbsp; with same mac address?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Second Setup&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If outside interface is shared but has unique mac address and connection is initated from the internet will then traffic&amp;nbsp; reach the inside context of &lt;/P&gt;&lt;P&gt;ASA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:58:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-sharing-outside-interface/m-p/2223936#M347962</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2019-03-12T01:58:43Z</dc:date>
    </item>
    <item>
      <title>ASA  Multiple context sharing Outside interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-sharing-outside-interface/m-p/2223937#M347964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think by default when you configure the ASA in Multiple Context mode and have a shared interface between 2 Security Contexts then both of the interfaces will use the same MAC address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In those cases I assume that the ASA uses existing NAT configurations or IP addresses configured on the ASA interfaces to determine which is the correct Security Content to which the traffic needs to be forwarded to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It should work as long as the IP address configured on the interface is different. Naturally if the NAT configurations also play a role as I said.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With regards to the second setup. I would imagine that this is actually the preferred way. That each contexts shared interface has a unique MAC address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check this section of the 8.2 configuration guide&lt;/P&gt;&lt;P&gt;&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#wp1146806"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/contexts.html#wp1146806&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 Jun 2013 22:07:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-sharing-outside-interface/m-p/2223937#M347964</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-06-16T22:07:17Z</dc:date>
    </item>
    <item>
      <title>ASA  Multiple context sharing Outside interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-sharing-outside-interface/m-p/2223938#M347965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jun 2013 16:15:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-sharing-outside-interface/m-p/2223938#M347965</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2013-06-17T16:15:16Z</dc:date>
    </item>
  </channel>
</rss>

