<?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: inside to dmz in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4509928#M1085438</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/978208"&gt;@adel85&lt;/a&gt; how are you testing? Provide the output of packet-tracer command from the CLI.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are pinging the DMZ interface of the ASA when connecting from the inside network, that will never work by design - the ASA won't allow you to do that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You have a /30 on the DMZ interface so you cannot add any DMZ hosts, you will need static routes for the DMZ hosts network.&lt;/P&gt;</description>
    <pubDate>Mon, 29 Nov 2021 11:44:54 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2021-11-29T11:44:54Z</dc:date>
    <item>
      <title>inside to dmz</title>
      <link>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4509914#M1085437</link>
      <description>&lt;P&gt;my post marked as spam i dont know why&lt;/P&gt;&lt;P&gt;i am doing a lab with packet tracer and i cant reach inside network to dmz&amp;nbsp;&lt;/P&gt;&lt;P&gt;asa config&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hostname ciscoasa&lt;BR /&gt;names&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/1&lt;BR /&gt;nameif dmz&lt;BR /&gt;security-level 50&lt;BR /&gt;ip address 172.19.3.1 255.255.255.252&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/2&lt;BR /&gt;nameif inside&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 172.19.254.1 255.255.255.252&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/3&lt;BR /&gt;no nameif&lt;BR /&gt;no security-level&lt;BR /&gt;no ip address&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/4&lt;BR /&gt;no nameif&lt;BR /&gt;no security-level&lt;BR /&gt;no ip address&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/5&lt;BR /&gt;no nameif&lt;BR /&gt;no security-level&lt;BR /&gt;no ip address&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/6&lt;BR /&gt;no nameif&lt;BR /&gt;no security-level&lt;BR /&gt;no ip address&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/7&lt;BR /&gt;no nameif&lt;BR /&gt;no security-level&lt;BR /&gt;no ip address&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/8&lt;BR /&gt;no nameif&lt;BR /&gt;no security-level&lt;BR /&gt;no ip address&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface Management1/1&lt;BR /&gt;management-only&lt;BR /&gt;no nameif&lt;BR /&gt;no security-level&lt;BR /&gt;no ip address&lt;BR /&gt;shutdown&lt;/P&gt;&lt;P&gt;!&lt;BR /&gt;route inside 172.19.2.0 255.255.255.252 172.19.254.2 1&lt;BR /&gt;route inside 172.19.4.0 255.255.255.0 172.19.254.2 1&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;class-map inspection_default&lt;BR /&gt;match default-inspection-traffic&lt;BR /&gt;!&lt;BR /&gt;policy-map type inspect dns preset_dns_map&lt;BR /&gt;parameters&lt;BR /&gt;message-length maximum 512&lt;BR /&gt;policy-map global_policy&lt;BR /&gt;class inspection_default&lt;BR /&gt;inspect dns preset_dns_map&lt;BR /&gt;inspect ftp&lt;BR /&gt;inspect tftp&lt;BR /&gt;!&lt;BR /&gt;service-policy global_policy global&lt;BR /&gt;!&lt;BR /&gt;telnet timeout 5&lt;BR /&gt;ssh timeout 5&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 10:42:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4509914#M1085437</guid>
      <dc:creator>adel85</dc:creator>
      <dc:date>2021-11-29T10:42:49Z</dc:date>
    </item>
    <item>
      <title>Re: inside to dmz</title>
      <link>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4509928#M1085438</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/978208"&gt;@adel85&lt;/a&gt; how are you testing? Provide the output of packet-tracer command from the CLI.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are pinging the DMZ interface of the ASA when connecting from the inside network, that will never work by design - the ASA won't allow you to do that.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You have a /30 on the DMZ interface so you cannot add any DMZ hosts, you will need static routes for the DMZ hosts network.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 11:44:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4509928#M1085438</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2021-11-29T11:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: inside to dmz</title>
      <link>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4510095#M1085441</link>
      <description>&lt;P&gt;i only have one host behind that /30 subnet, 172.19.3.2&lt;/P&gt;&lt;P&gt;i can ping it if i raise the security level to 100 but when i make it 50 ping stops ( check attachment)&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 16:41:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4510095#M1085441</guid>
      <dc:creator>adel85</dc:creator>
      <dc:date>2021-11-29T16:41:17Z</dc:date>
    </item>
    <item>
      <title>Re: inside to dmz</title>
      <link>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4510101#M1085443</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/978208"&gt;@adel85&lt;/a&gt; ok, I assumed you'd have a switch if using a /30 network.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regardless you need to permit the return ICMP traffic, either create an ACL to permit the ICMP traffic or run the command &lt;STRONG&gt;fixup protocol icmp&lt;/STRONG&gt; to inspect the ICMP traffic, this should allow the ping to respond.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By default traffic between interfaces of the same security level is permitted, traffic from a lower security to a high level is denied - as you've found out. Hence why you need an ACL to specify the traffic or if just ICMP use the command specified above to inspect.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 16:49:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-to-dmz/m-p/4510101#M1085443</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2021-11-29T16:49:31Z</dc:date>
    </item>
  </channel>
</rss>

