<?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 access policy/ NAT behavior from same subnet in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883822#M153241</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Will an ASA's (v9.4) access policy apply when connecting to a NAT'd address from the same subnet?&lt;/P&gt;
&lt;P&gt;I.e. Source = 192.168.10.5; Destination = 192.168.10.10 (NAT rule on firewall - physical addr 192.168.200.10).&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 07:51:19 GMT</pubDate>
    <dc:creator>NeGi00000</dc:creator>
    <dc:date>2019-03-12T07:51:19Z</dc:date>
    <item>
      <title>ASA access policy/ NAT behavior from same subnet</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883822#M153241</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Will an ASA's (v9.4) access policy apply when connecting to a NAT'd address from the same subnet?&lt;/P&gt;
&lt;P&gt;I.e. Source = 192.168.10.5; Destination = 192.168.10.10 (NAT rule on firewall - physical addr 192.168.200.10).&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:51:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883822#M153241</guid>
      <dc:creator>NeGi00000</dc:creator>
      <dc:date>2019-03-12T07:51:19Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883823#M153242</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Do you mean if the access-list will work for the intra-interface traffic, which means that the ingress and egress interface is same on ASA?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jagrati&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2016 11:50:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883823#M153242</guid>
      <dc:creator>jagraaga</dc:creator>
      <dc:date>2016-06-07T11:50:54Z</dc:date>
    </item>
    <item>
      <title>Hi - No, I believe this would</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883824#M153243</link>
      <description>&lt;P&gt;Hi - No, I believe this would be inter-interface.&lt;/P&gt;
&lt;P&gt;E.g. Traffic is ingress on eth0 (to use the example above, eth0 would have an addr of 192.168.10.1) and egress via eth1 (with an addr of 192.168.200.1).&lt;/P&gt;
&lt;P&gt;Surely access rules must come into effect in this scenario as the packet is traversing both interfaces. It is a firewall after all, not a reverse proxy.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would expect this if it was a routed connection (Source = 10.10.10.10), I'm just uncertain of the behavior when it's in the same subnet as the firewall interface (eth0).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2016 13:48:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883824#M153243</guid>
      <dc:creator>NeGi00000</dc:creator>
      <dc:date>2016-06-07T13:48:58Z</dc:date>
    </item>
    <item>
      <title>To see how the traffic is</title>
      <link>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883825#M153244</link>
      <description>&lt;P&gt;To see how the traffic is going to flow via the ASA, you can use packet-tracer.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;#packet-tracer input inside ip &amp;lt;source-ip&amp;gt; &amp;lt;source-port&amp;gt; &amp;lt;destination-ip&amp;gt; &amp;lt;destination-port&amp;gt; detailed&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Try to check with the IPs and ports how the traffic is going through the ASA. This will give you a detailed view&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Jagrati&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2016 13:53:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-access-policy-nat-behavior-from-same-subnet/m-p/2883825#M153244</guid>
      <dc:creator>jagraaga</dc:creator>
      <dc:date>2016-06-07T13:53:32Z</dc:date>
    </item>
  </channel>
</rss>

