<?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 NAT,ACCESS RULES N TRAFFIC INSPECTION in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342945#M343312</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Sep 2013 22:56:56 GMT</pubDate>
    <dc:creator>Antonio Simoes</dc:creator>
    <dc:date>2013-09-09T22:56:56Z</dc:date>
    <item>
      <title>NAT,ACCESS RULES N TRAFFIC INSPECTION</title>
      <link>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342939#M343300</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone awnser this questions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;What I have to do to:&lt;/SPAN&gt;&lt;OL&gt;&lt;/OL&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;Allow only traffic http/https from the inside to dmz&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Allow only traffic http/https from the dmz to inside&lt;/LI&gt;&lt;/OL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN style="line-height: 0px; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;How can I simulate inspected retrurning traffic in packet tracer?&amp;nbsp; Otherwise I never know if it will be allowed to return.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AS&lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 0px; font-size: 10pt;"&gt; &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:35:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342939#M343300</guid>
      <dc:creator>Antonio Simoes</dc:creator>
      <dc:date>2019-03-12T02:35:53Z</dc:date>
    </item>
    <item>
      <title>NAT,ACCESS RULES N TRAFFIC INSPECTION</title>
      <link>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342940#M343301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Antonio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For this particular traffic (HTTP, HTTPS) there will be only one session or data channel so with a regular packet-tracer you will be able to determine whether the returning traffic will be allowed or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An example would be with ICMP (without the stateful inspection you will see a drop on the packet-tracer.. It points to an ACL issue I think).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I will provide you is a really useful command that not all of the people is aware of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;show service-policy flow tcp host x.x.x.x host x.x.x.x eq 80&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will be seeing if a policy inspection or parameter is matched &lt;SPAN __jive_emoticon_name="grin" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/grin.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For more information about Core and Security Networking follow my website at &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;SPAN&gt;Any question contact me at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Sep 2013 18:40:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342940#M343301</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-09-09T18:40:01Z</dc:date>
    </item>
    <item>
      <title>NAT,ACCESS RULES N TRAFFIC INSPECTION</title>
      <link>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342941#M343304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi J,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I´m confuse about one situation. In on of my branch companies, I have conected to my ASA inside port a ISR 2911/K9, doing router on the stick to my vlan´s. But now I have do conect a service on the main office. So I will do a Site-to-Site VPN on the ASA. But the local network is on of my vlans.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what will happen, I do the VPN and the ASA Route the traffic to the ISR and vice versa?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Sep 2013 22:37:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342941#M343304</guid>
      <dc:creator>Antonio Simoes</dc:creator>
      <dc:date>2013-09-09T22:37:23Z</dc:date>
    </item>
    <item>
      <title>NAT,ACCESS RULES N TRAFFIC INSPECTION</title>
      <link>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342942#M343305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Antonio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exactly, You build the VPN between the ASA and the other site and the ASA routes and encrypts the traffic properly &lt;SPAN __jive_emoticon_name="grin" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/grin.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For more information about Core and Security Networking follow my website at &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;SPAN&gt;Any question contact me at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Sep 2013 22:43:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342942#M343305</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-09-09T22:43:01Z</dc:date>
    </item>
    <item>
      <title>NAT,ACCESS RULES N TRAFFIC INSPECTION</title>
      <link>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342943#M343307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi J&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ok. Two days from now I will test it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take care man.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Sep 2013 22:49:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342943#M343307</guid>
      <dc:creator>Antonio Simoes</dc:creator>
      <dc:date>2013-09-09T22:49:42Z</dc:date>
    </item>
    <item>
      <title>NAT,ACCESS RULES N TRAFFIC INSPECTION</title>
      <link>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342944#M343309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Antonio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sure, keep me posted!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For more information about Core and Security Networking follow my website at &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://laguiadelnetworking.com"&gt;http://laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;SPAN&gt;Any question contact me at &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:jcarvaja@laguiadelnetworking.com"&gt;jcarvaja@laguiadelnetworking.com&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt; &lt;BR /&gt;Cheers, &lt;BR /&gt; &lt;BR /&gt;Julio Carvajal Segura&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Sep 2013 22:52:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342944#M343309</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-09-09T22:52:12Z</dc:date>
    </item>
    <item>
      <title>NAT,ACCESS RULES N TRAFFIC INSPECTION</title>
      <link>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342945#M343312</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Sep 2013 22:56:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-access-rules-n-traffic-inspection/m-p/2342945#M343312</guid>
      <dc:creator>Antonio Simoes</dc:creator>
      <dc:date>2013-09-09T22:56:56Z</dc:date>
    </item>
  </channel>
</rss>

