<?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 Rule to allow machine from DMZ to internal in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729896#M1004612</link>
    <description>&lt;P&gt;Hi all.  Here's the scenario:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX 515 v7.22 with 3 interfaces, Inside, Outside, DMZ. Inside=100, Outside=0, DMZ=98&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to put in a rule to allow a machine from the DMZ (let's say 192.168.100.25) to have access to one machine on the internal network (192.168.25.25), on ports 125 and 325.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would I need two rules that look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 eq 325 host 192.168.25.25 eq 325&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 eq 125 host 192.168.25.25 eq 125&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or is there a better way to do this?  Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 10:15:08 GMT</pubDate>
    <dc:creator>mwall1</dc:creator>
    <dc:date>2019-03-11T10:15:08Z</dc:date>
    <item>
      <title>Rule to allow machine from DMZ to internal</title>
      <link>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729896#M1004612</link>
      <description>&lt;P&gt;Hi all.  Here's the scenario:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX 515 v7.22 with 3 interfaces, Inside, Outside, DMZ. Inside=100, Outside=0, DMZ=98&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to put in a rule to allow a machine from the DMZ (let's say 192.168.100.25) to have access to one machine on the internal network (192.168.25.25), on ports 125 and 325.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would I need two rules that look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 eq 325 host 192.168.25.25 eq 325&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 eq 125 host 192.168.25.25 eq 125&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or is there a better way to do this?  Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:15:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729896#M1004612</guid>
      <dc:creator>mwall1</dc:creator>
      <dc:date>2019-03-11T10:15:08Z</dc:date>
    </item>
    <item>
      <title>Re: Rule to allow machine from DMZ to internal</title>
      <link>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729897#M1004616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;get rid of the source ports...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 host 192.168.25.25 eq 325 &lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 host 192.168.25.25 eq 125 &lt;/P&gt;&lt;P&gt;access-group dmz_access_in in interface DMZ&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;remember, once you do this you deny everything else into the DMZ interface so you probably want something like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 host 192.168.25.25 eq 325 &lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 host 192.168.25.25 eq 125&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended deny ip any 192.168.25.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit ip any any&lt;/P&gt;&lt;P&gt;access-group dmz_access_in in interface DMZ&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 May 2007 13:30:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729897#M1004616</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-05-16T13:30:58Z</dc:date>
    </item>
    <item>
      <title>Re: Rule to allow machine from DMZ to internal</title>
      <link>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729898#M1004618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need following commands-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,DMZ) 192.168.25.25 192.168.25.25&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 host 192.168.25.25 eq 325&lt;/P&gt;&lt;P&gt;access-list dmz_access_in extended permit tcp 192.168.100.25 host 192.168.25.25 eq 125 &lt;/P&gt;&lt;P&gt;access-group dmz_access_in in interface DMZ&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vibhor.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 May 2007 13:31:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729898#M1004618</guid>
      <dc:creator>vitripat</dc:creator>
      <dc:date>2007-05-16T13:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: Rule to allow machine from DMZ to internal</title>
      <link>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729899#M1004621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So do I need the Static command, or not?  I got 2 answers but they're not exactly saying the same thing...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 May 2007 17:11:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729899#M1004621</guid>
      <dc:creator>mwall1</dc:creator>
      <dc:date>2007-05-16T17:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: Rule to allow machine from DMZ to internal</title>
      <link>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729900#M1004623</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, as Vibhor wrote, you need the static as well. What I was trying to say is if you create an acl into the dmz to restrict traffic inside, you will also restrict the traffic from the dmz to the outside, so if you don't want to do that you must allow it in the acl. That's the only difference in our acl's.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 May 2007 17:13:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rule-to-allow-machine-from-dmz-to-internal/m-p/729900#M1004623</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-05-16T17:13:32Z</dc:date>
    </item>
  </channel>
</rss>

