<?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 classifying packets in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-classifying-packets/m-p/436266#M427822</link>
    <description>&lt;P&gt;Hi, running in multiple mode, and sharing both the inside and outside interface.&lt;/P&gt;&lt;P&gt;Each context has it's own ip address etc.&lt;/P&gt;&lt;P&gt;The ASA classifies the packet into a context by matching the destination address to one of the contexts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this mean that if I had contextA and contextB, both sharing their interfaces, that traffic originating from both customers could not go to the same destination i.e. customer A want to go to inside address of 1.1.1.1 and customer b wants to go to inside address of 1.1.1.1, since the classify works on destination, it would not work.... &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;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:25:11 GMT</pubDate>
    <dc:creator>haydenmace</dc:creator>
    <dc:date>2020-02-21T08:25:11Z</dc:date>
    <item>
      <title>ASA classifying packets</title>
      <link>https://community.cisco.com/t5/network-security/asa-classifying-packets/m-p/436266#M427822</link>
      <description>&lt;P&gt;Hi, running in multiple mode, and sharing both the inside and outside interface.&lt;/P&gt;&lt;P&gt;Each context has it's own ip address etc.&lt;/P&gt;&lt;P&gt;The ASA classifies the packet into a context by matching the destination address to one of the contexts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this mean that if I had contextA and contextB, both sharing their interfaces, that traffic originating from both customers could not go to the same destination i.e. customer A want to go to inside address of 1.1.1.1 and customer b wants to go to inside address of 1.1.1.1, since the classify works on destination, it would not work.... &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;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:25:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-classifying-packets/m-p/436266#M427822</guid>
      <dc:creator>haydenmace</dc:creator>
      <dc:date>2020-02-21T08:25:11Z</dc:date>
    </item>
    <item>
      <title>Re: ASA classifying packets</title>
      <link>https://community.cisco.com/t5/network-security/asa-classifying-packets/m-p/436267#M427823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so you have two context , contextA and contextB&lt;/P&gt;&lt;P&gt;they are sharing inside and outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ip address of ContextA outside = 10.1.1.1&lt;/P&gt;&lt;P&gt;IP address of ContextB outside = 10.1.1.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IP address of contextA inside  = 1.1.1.1&lt;/P&gt;&lt;P&gt;IP address of contextB outside = 1.1.1.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to define the translation for an address of ContextA e.g. 1.1.1.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this host will only be reachable via contextA. If you define the translation on both contexts it will confuse out the contexts and classisification will fail.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Oct 2005 00:59:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-classifying-packets/m-p/436267#M427823</guid>
      <dc:creator>nkhawaja</dc:creator>
      <dc:date>2005-10-03T00:59:54Z</dc:date>
    </item>
  </channel>
</rss>

