<?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: PIX DMZ to inside in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138749#M608542</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As it is at the moment once the xlate has been set up from inside (by pinging to the dmz host) the dmz host can ping inside.  So what you're saying is to actually initiate the communication I need a xlate statement in the form of a static command to map the dmz ip address through the firewall?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Mar 2003 10:47:33 GMT</pubDate>
    <dc:creator>andyirving</dc:creator>
    <dc:date>2003-03-07T10:47:33Z</dc:date>
    <item>
      <title>PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138745#M608538</link>
      <description>&lt;P&gt;Running PIX 515 with one DMZ.   Problem is I cannot initiate any sessions from the DMZ side.  Ping is the really strange one.  I cannot ping from the DMZ to inside, the packets do not hit the debug packet dmz.  &lt;/P&gt;&lt;P&gt;Packet sniffer shows the requests being sent to the PIX interface, it seems as though the PIX just ignores the ping requests (they do not increment the ACL counter).  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if I ping from the inside to the host on DMZ it works, I can then ping from the DMZ to the inside.  This is the same for all traffic even with a permit ip any any on bothe the inside and DMZ ACLs.  &lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:36:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138745#M608538</guid>
      <dc:creator>andyirving</dc:creator>
      <dc:date>2020-02-21T06:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138746#M608539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would be much more helpful if you posted your ACL, static, nat, and global items.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Turn on logging.  Run a continous ping.  The Pix should tell you exactly why the pings are being dropped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Shannon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Mar 2003 09:21:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138746#M608539</guid>
      <dc:creator>shannong</dc:creator>
      <dc:date>2003-03-07T09:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138747#M608540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What level of logging do you advise&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host x.x.x.x eq www&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host x.x.x.xeq https&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host x.x.x.x eq www&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host x.x.x.x eq https&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp host 194.201.48.1 host x.x.x.x eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp host 180.10.39.14 host x.x.x.x eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp host 194.201.48.8 host  x.x.x.x eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp host 194.200.92.82 host  x.x.x.x eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp 195.212.0.0 255.255.255.240 host  x.x.x.x  eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp host 62.172.133.97 host  x.x.x.x eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp host 62.172.133.97 host  x.x.x.x eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_outside permit icmp any any&lt;/P&gt;&lt;P&gt;access-list acl_dmz permit tcp host 10.254.3.2 host 10.254.0.6 eq smtp&lt;/P&gt;&lt;P&gt;access-list acl_dmz permit tcp host 10.254.3.3 host 10.254.0.6 eq smtp&lt;/P&gt;&lt;P&gt;access-list acl_dmz permit tcp host 10.254.3.3 host 185.1.30.1 eq 1414&lt;/P&gt;&lt;P&gt;access-list acl_dmz permit tcp host 10.254.3.2 host 185.1.30.1 eq 1414&lt;/P&gt;&lt;P&gt;access-list acl_dmz permit tcp host 10.254.3.2 host 185.1.30.1 eq 1415&lt;/P&gt;&lt;P&gt;access-list acl_dmz permit tcp host 10.254.3.3 host 185.1.30.1 eq 1415&lt;/P&gt;&lt;P&gt;access-list acl_dmz permit icmp any any&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp host 185.1.30.1 host 10.254.3.3 eq 1414&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp host 185.1.30.1 host 10.254.3.2 eq 1414&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp host 185.1.30.1 host 10.254.3.2 eq 1415&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp host 185.1.30.1 host 10.254.3.3 eq 1415&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.2 eq 3700&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.3 eq 3700&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.2 eq 3700&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.3 eq 3700&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 10.0.0.0 255.255.255.0 host 10.254.3.2 eq 3700&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 10.0.0.0 255.255.255.0 host 10.254.3.3 eq 3700&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.2 eq www&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.2 eq https&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.3 eq www&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.3 eq https&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.2 eq www&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.3 eq www&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.2 eq https&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.3 eq https&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp host 185.1.123.89 host 185.2.254.2 eq https&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.2 eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.3 eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.3 eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp host 10.254.0.6 host 10.254.3.2 eq smtp&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp host 10.254.0.6 host 10.254.3.3 eq smtp&lt;/P&gt;&lt;P&gt;access-list acl_inside permit icmp any any&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.2 eq 8080&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.2 eq ftp&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.2 eq ftp&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.3 eq ftp&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.3 eq ftp&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.3 eq ftp-data&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.1.0.0 255.255.0.0 host 10.254.3.2 eq ftp-data&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.2 eq ftp-data&lt;/P&gt;&lt;P&gt;access-list acl_inside permit tcp 185.2.0.0 255.255.0.0 host 10.254.3.3 eq ftp-data&lt;/P&gt;&lt;P&gt;icmp permit any green&lt;/P&gt;&lt;P&gt;icmp permit any orange&lt;/P&gt;&lt;P&gt;..&lt;/P&gt;&lt;P&gt;nat (green) 0 0.0.0.0 0.0.0.0 0 0&lt;/P&gt;&lt;P&gt;static (orange,red) 62.172.133.109 10.254.3.2 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (orange,red) 62.172.133.111 10.254.3.3 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;access-group acl_outside in interface red&lt;/P&gt;&lt;P&gt;access-group acl_inside in interface green&lt;/P&gt;&lt;P&gt;access-group acl_dmz in interface orange&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Mar 2003 09:35:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138747#M608540</guid>
      <dc:creator>andyirving</dc:creator>
      <dc:date>2003-03-07T09:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138748#M608541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Officially, you cannot access a host on a higher security interface from a low security interface (orange to green) without a static statement.  For your DMZ hosts to ping inside, there must be something to hold their translations up.  Functionally, you should be able to do this with the nat 0 command as long as the host on the inside has already initiated traffic to the DMZ and the translation has not timed out yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use logging buffered 7.  You'll probably see complaints about no translation group found.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Shannon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Mar 2003 10:31:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138748#M608541</guid>
      <dc:creator>shannong</dc:creator>
      <dc:date>2003-03-07T10:31:13Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138749#M608542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As it is at the moment once the xlate has been set up from inside (by pinging to the dmz host) the dmz host can ping inside.  So what you're saying is to actually initiate the communication I need a xlate statement in the form of a static command to map the dmz ip address through the firewall?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Mar 2003 10:47:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138749#M608542</guid>
      <dc:creator>andyirving</dc:creator>
      <dc:date>2003-03-07T10:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138750#M608543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Shannon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry for this interruption! : )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You had posted a reply to a different question  with a perl script to provide an alerting mechanism for the IEV/IDM application (Cisco IDS platform).  I have run that script and get an error message which states: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C:\perl\bin&amp;gt;perl.exe idsalert.txt&lt;/P&gt;&lt;P&gt;Can't locate DBI.pm in @INC (@INC contains: C:/perl/lib C:/perl/site/lib .) at i&lt;/P&gt;&lt;P&gt;dsalert.txt line 3.&lt;/P&gt;&lt;P&gt;BEGIN failed--compilation aborted at idsalert.txt line 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I appreciate your help...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Mar 2003 16:06:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138750#M608543</guid>
      <dc:creator>amir.safayan</dc:creator>
      <dc:date>2003-03-07T16:06:48Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138751#M608544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Those first two  lines in the script are calling perl modules that need to installed.  I don't know what distribution of perl you're using, but you'll need to follow the instructions appropriate for that vendor to install the following modules:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DBI&lt;/P&gt;&lt;P&gt;DBD:mysql&lt;/P&gt;&lt;P&gt;Mail:Sender&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Mar 2003 00:57:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138751#M608544</guid>
      <dc:creator>shannong</dc:creator>
      <dc:date>2003-03-08T00:57:06Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138752#M608545</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had a similiar problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;your internet addresses are not recognized in the dmz, and are not translated in, &lt;/P&gt;&lt;P&gt;Here is what worked for me:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (orange,red) 10.254.3.3 10.254.3.2 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (orange,red) 10.254.3.3 10.254.3.3 netmask 255.255.255.255 0 0 &lt;/P&gt;&lt;P&gt;clear xlate&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Mar 2003 01:22:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138752#M608545</guid>
      <dc:creator>bwestbrook</dc:creator>
      <dc:date>2003-03-08T01:22:25Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138753#M608546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sorry,  I have one of yorur IP's wrong. it should look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (orange,red) 10.254.3.2 10.254.3.2 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;static (orange,red) 10.254.3.3 10.254.3.3 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;clear xlate&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>Sat, 08 Mar 2003 01:23:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138753#M608546</guid>
      <dc:creator>bwestbrook</dc:creator>
      <dc:date>2003-03-08T01:23:56Z</dc:date>
    </item>
    <item>
      <title>Re: PIX DMZ to inside</title>
      <link>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138754#M608547</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, he's trying to give his DMZ hosts access to inside.  So something like this would work:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (green, orange) 185.1.30.1 185.1.30.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally you do a "clear xlate", but you won't need to in this case because the address translation isn't changing to a different IP as NAT 0 is being used for everything already.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Mar 2003 17:16:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-dmz-to-inside/m-p/138754#M608547</guid>
      <dc:creator>shannong</dc:creator>
      <dc:date>2003-03-08T17:16:20Z</dc:date>
    </item>
  </channel>
</rss>

