<?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: Pinging DMZ Server from outside without applying Access list in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259746#M858577</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Answering your question "1.Im able to ping 192.168.100.215 server in DMZ from outside source ip 192.168.255.1 how?"...because of following rule:&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.100.0 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;When you allow ip access... you are allowing mostly anything from Internet. Make note that ICMP &amp;amp; IGMP operate on top of IP but do not transport data like UDP or TCP.... Also, not taking too much time...the following is wrong as well:&lt;/P&gt;&lt;P&gt;! &lt;/P&gt;&lt;P&gt;access-list DMZ_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.100.0 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Why? Because if your DMZ is only 192.168.100.x...then you should always see 192.168.100.x after your permit + protocol and not 192.168.255.x&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;If 192.168.255.x is coming from outside &amp;amp; you wanted to give 100% access to your DMZ (which no one does), the correct statement would be (as you have): &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.0.0 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Via above command, you are giving Internet users on 192.168.255.x segment total access to any 192.168.0.0 no matter what interface (inside or DMZ).&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Note: Make sure you have the following as well&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Access-list inside_access_all permit ip any any&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-group inside_access_all in interface inside&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list DMZ_access_all permit icmp any any&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;also add your other dmz servers accessing inside or outside after this line&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-group DMZ_access_all in interface DMZ&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Note: why am I, calling this DMZ_access_all and not DMZ_access_inâ&amp;#128;¦because sooner or later, your DMZ servers need to access http, ftp, https outside and you can only have 2  access group only depending on direction of trafficâ&amp;#128;¦ Most FW admin config call for one access group per interface. Also, more recent codes require you to have a access group on inside interface... however its a godd idea to have this, in case later you have an inside host attacking outside, you can block that inside host by placing an access list on top of permit ip an any... I hope this helps and good luck... Matt&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 19 Jul 2009 15:38:18 GMT</pubDate>
    <dc:creator>mattmatin007</dc:creator>
    <dc:date>2009-07-19T15:38:18Z</dc:date>
    <item>
      <title>Pinging DMZ Server from outside without applying Access list to DMZ Interf.</title>
      <link>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259743#M858571</link>
      <description>&lt;P&gt;************************&lt;/P&gt;&lt;P&gt;Kindly look on the configuration and guide me please.&lt;/P&gt;&lt;P&gt;************************&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/0&lt;/P&gt;&lt;P&gt; nameif outside&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt; ip address 10.10.10.2 255.255.255.252 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/1&lt;/P&gt;&lt;P&gt; nameif Inside&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; ip address 192.168.0.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/2&lt;/P&gt;&lt;P&gt; nameif DMZ&lt;/P&gt;&lt;P&gt; security-level 50&lt;/P&gt;&lt;P&gt; ip address 192.168.100.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;!             &lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/3&lt;/P&gt;&lt;P&gt; description LAN Failover Interface&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Management0/0&lt;/P&gt;&lt;P&gt; nameif management&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; ip address 192.168.1.1 255.255.255.0 &lt;/P&gt;&lt;P&gt; management-only&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;boot system disk0:/asa804-k8.bin&lt;/P&gt;&lt;P&gt;ftp mode passive&lt;/P&gt;&lt;P&gt;dns server-group DefaultDNS&lt;/P&gt;&lt;P&gt; domain-name default.domain.invalid&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp 192.168.22.0 255.255.255.0 host 192.168.0.210 eq ftp &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp 192.168.22.0 255.255.255.0 host 192.168.0.201 eq www &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp 192.168.22.0 255.255.255.0 host 192.168.0.204 eq www &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.0.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit icmp 10.10.10.0 255.255.255.252 192.168.0.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp host 192.168.22.38 host 192.168.0.201 eq 8080 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp 192.168.22.0 255.255.255.0 host 192.168.0.201 eq 7777 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended deny tcp host 192.168.22.38 host 192.168.0.201 eq 7777 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp host 192.168.22.100 host 192.168.0.201 eq 8080 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit icmp 192.168.22.0 255.255.255.0 192.168.0.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp host 192.168.22.100 host 192.168.0.204 eq 8080 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp host 192.168.22.100 host 192.168.0.204 eq 7777 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit icmp 10.10.10.0 255.255.255.252 192.168.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list nonat extended permit ip 192.168.0.0 255.255.255.0 any &lt;/P&gt;&lt;P&gt;access-list DMZ_access_in extended permit ip host 192.168.100.0 192.168.0.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list DMZ_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list nonatDMZ extended permit ip 192.168.100.0 255.255.255.0 any &lt;/P&gt;&lt;P&gt;access-list traffic_for_ips extended permit ip any any &lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;logging asdm informational&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu Inside 1500&lt;/P&gt;&lt;P&gt;mtu DMZ 1500  &lt;/P&gt;&lt;P&gt;mtu management 1500&lt;/P&gt;&lt;P&gt;ip verify reverse-path interface outside&lt;/P&gt;&lt;P&gt;ip verify reverse-path interface Inside&lt;/P&gt;&lt;P&gt;failover      &lt;/P&gt;&lt;P&gt;failover lan unit primary&lt;/P&gt;&lt;P&gt;failover lan interface failovetr-int GigabitEthernet0/3&lt;/P&gt;&lt;P&gt;failover replication http&lt;/P&gt;&lt;P&gt;failover interface ip failovetr-int 10.250.250.1 255.255.255.252 standby 10.250.250.2&lt;/P&gt;&lt;P&gt;icmp unreachable rate-limit 1 burst-size 1&lt;/P&gt;&lt;P&gt;asdm image disk0:/asdm-61551.bin&lt;/P&gt;&lt;P&gt;asdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;nat (Inside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;nat (DMZ) 0 access-list nonatDMZ&lt;/P&gt;&lt;P&gt;static (Inside,DMZ) 192.168.0.0 192.168.0.0 netmask 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-group outside_access_in in interface outside&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 10.10.10.1 1&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:56:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259743#M858571</guid>
      <dc:creator>aamirkiani</dc:creator>
      <dc:date>2019-03-11T15:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: Pinging DMZ Server from outside without applying Access list</title>
      <link>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259744#M858574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Pls. provide the output of "sh run policy-map" make sure there inspect icmp is enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class inspection_default&lt;/P&gt;&lt;P&gt;  inspect ftp&lt;/P&gt;&lt;P&gt;  .&lt;/P&gt;&lt;P&gt;  .&lt;/P&gt;&lt;P&gt;  .&lt;/P&gt;&lt;P&gt;  inspect icmp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service-policy global_policy global&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Jul 2009 12:07:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259744#M858574</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2009-07-19T12:07:06Z</dc:date>
    </item>
    <item>
      <title>Re: Pinging DMZ Server from outside without applying Access list</title>
      <link>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259745#M858575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;**********************&lt;/P&gt;&lt;P&gt;Kindly look at my configuration and guide me how i can solve my problem,&lt;/P&gt;&lt;P&gt;1.Im able to ping 192.168.100.215 server in DMZ from outside source ip 192.168.255.1 how? it is possible without apply access list to DMZ interface.2. when im applying access list to DMZ inerface then from outside im not able to ping DMZ server 192.168.100.215.why?&lt;/P&gt;&lt;P&gt;3. I want to access to DMZ network from Inside network. if any thing wrong pleae guide me.my complete ASA configuration as following.&lt;/P&gt;&lt;P&gt;*******************************************   ASA Version 8.0(4) &lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/0&lt;/P&gt;&lt;P&gt; nameif outside&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt; ip address 10.10.10.2 255.255.255.252 &lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/1&lt;/P&gt;&lt;P&gt; nameif Inside&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; ip address 192.168.0.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/2&lt;/P&gt;&lt;P&gt; nameif DMZ&lt;/P&gt;&lt;P&gt; security-level 50&lt;/P&gt;&lt;P&gt; ip address 192.168.100.1 255.255.255.0             &lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/3&lt;/P&gt;&lt;P&gt; description LAN Failover Interface&lt;/P&gt;&lt;P&gt;interface Management0/0&lt;/P&gt;&lt;P&gt; nameif management&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; ip address 192.168.1.1 255.255.255.0 &lt;/P&gt;&lt;P&gt; management-only&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp 192.168.22.0 255.255.255.0 host 192.168.0.210 eq ftp &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp 192.168.22.0 255.255.255.0 host 192.168.0.201 eq www &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp 192.168.22.0 255.255.255.0 host 192.168.0.204 eq www &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.0.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit icmp 10.10.10.0 255.255.255.252 192.168.0.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp host 192.168.22.38 host 192.168.0.201 eq 8080 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp 192.168.22.0 255.255.255.0 host 192.168.0.201 eq 7777 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended deny tcp host 192.168.22.38 host 192.168.0.201 eq 7777 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp host 192.168.22.100 host 192.168.0.201 eq 8080 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit icmp 192.168.22.0 255.255.255.0 192.168.0.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp host 192.168.22.100 host 192.168.0.204 eq 8080 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit tcp host 192.168.22.100 host 192.168.0.204 eq 7777 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit icmp 10.10.10.0 255.255.255.252 192.168.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list nonat extended permit ip 192.168.0.0 255.255.255.0 any &lt;/P&gt;&lt;P&gt;access-list DMZ_access_in extended permit ip 192.168.100.0 255.255.255.0 192.168.0.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list DMZ_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list DMZ_access_in extended permit icmp 10.10.10.0 255.255.255.252 192.168.100.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-list nonatDMZ extended permit ip 192.168.100.0 255.255.255.0 any &lt;/P&gt;&lt;P&gt;access-list traffic_for_ips extended permit ip any any &lt;/P&gt;&lt;P&gt;nat (Inside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;nat (DMZ) 0 access-list nonatDMZ&lt;/P&gt;&lt;P&gt;static (Inside,DMZ) 192.168.0.0 192.168.0.0 netmask 255.255.255.0 &lt;/P&gt;&lt;P&gt;access-group outside_access_in in interface outside&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 10.10.10.1 1&lt;/P&gt;&lt;P&gt;dynamic-access-policy-record DfltAccessPolicy&lt;/P&gt;&lt;P&gt;class-map inspection_default&lt;/P&gt;&lt;P&gt; match default-inspection-traffic&lt;/P&gt;&lt;P&gt;class-map ips_class_map&lt;/P&gt;&lt;P&gt; match access-list traffic_for_ips&lt;/P&gt;&lt;P&gt;policy-map type inspect dns migrated_dns_map_2&lt;/P&gt;&lt;P&gt; parameters&lt;/P&gt;&lt;P&gt;  message-length maximum 512&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class inspection_default&lt;/P&gt;&lt;P&gt;  inspect dns migrated_dns_map_2 &lt;/P&gt;&lt;P&gt;  inspect ftp &lt;/P&gt;&lt;P&gt;  inspect h323 h225 &lt;/P&gt;&lt;P&gt;  inspect h323 ras &lt;/P&gt;&lt;P&gt;  inspect rsh &lt;/P&gt;&lt;P&gt;  inspect rtsp &lt;/P&gt;&lt;P&gt;  inspect esmtp &lt;/P&gt;&lt;P&gt;  inspect sqlnet &lt;/P&gt;&lt;P&gt;  inspect skinny  &lt;/P&gt;&lt;P&gt;  inspect sunrpc &lt;/P&gt;&lt;P&gt;  inspect xdmcp &lt;/P&gt;&lt;P&gt;  inspect sip  &lt;/P&gt;&lt;P&gt;  inspect netbios &lt;/P&gt;&lt;P&gt;  inspect tftp &lt;/P&gt;&lt;P&gt;  inspect icmp &lt;/P&gt;&lt;P&gt; class ips_class_map&lt;/P&gt;&lt;P&gt;  ips inline fail-open&lt;/P&gt;&lt;P&gt;: end&lt;/P&gt;&lt;P&gt;ASA#               &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Jul 2009 12:26:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259745#M858575</guid>
      <dc:creator>aamirkiani</dc:creator>
      <dc:date>2009-07-19T12:26:20Z</dc:date>
    </item>
    <item>
      <title>Re: Pinging DMZ Server from outside without applying Access list</title>
      <link>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259746#M858577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Answering your question "1.Im able to ping 192.168.100.215 server in DMZ from outside source ip 192.168.255.1 how?"...because of following rule:&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.100.0 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;When you allow ip access... you are allowing mostly anything from Internet. Make note that ICMP &amp;amp; IGMP operate on top of IP but do not transport data like UDP or TCP.... Also, not taking too much time...the following is wrong as well:&lt;/P&gt;&lt;P&gt;! &lt;/P&gt;&lt;P&gt;access-list DMZ_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.100.0 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Why? Because if your DMZ is only 192.168.100.x...then you should always see 192.168.100.x after your permit + protocol and not 192.168.255.x&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;If 192.168.255.x is coming from outside &amp;amp; you wanted to give 100% access to your DMZ (which no one does), the correct statement would be (as you have): &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list outside_access_in extended permit ip 192.168.255.0 255.255.255.0 192.168.0.0 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Via above command, you are giving Internet users on 192.168.255.x segment total access to any 192.168.0.0 no matter what interface (inside or DMZ).&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Note: Make sure you have the following as well&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Access-list inside_access_all permit ip any any&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-group inside_access_all in interface inside&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list DMZ_access_all permit icmp any any&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;also add your other dmz servers accessing inside or outside after this line&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-group DMZ_access_all in interface DMZ&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Note: why am I, calling this DMZ_access_all and not DMZ_access_inâ&amp;#128;¦because sooner or later, your DMZ servers need to access http, ftp, https outside and you can only have 2  access group only depending on direction of trafficâ&amp;#128;¦ Most FW admin config call for one access group per interface. Also, more recent codes require you to have a access group on inside interface... however its a godd idea to have this, in case later you have an inside host attacking outside, you can block that inside host by placing an access list on top of permit ip an any... I hope this helps and good luck... Matt&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Jul 2009 15:38:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-dmz-server-from-outside-without-applying-access-list-to/m-p/1259746#M858577</guid>
      <dc:creator>mattmatin007</dc:creator>
      <dc:date>2009-07-19T15:38:18Z</dc:date>
    </item>
  </channel>
</rss>

