<?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: Using PIX without firewall features. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385793#M551705</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I forgot the nat and global statements.  A wide open config should look more like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 1 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;access-list inbound permit ip any any&lt;/P&gt;&lt;P&gt;access-group inbound in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just wanted to clarify.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doug.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Feb 2005 22:53:41 GMT</pubDate>
    <dc:creator>dougz</dc:creator>
    <dc:date>2005-02-08T22:53:41Z</dc:date>
    <item>
      <title>Using PIX without firewall features.</title>
      <link>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385791#M551701</link>
      <description>&lt;P&gt;I need to install a PIX firewall to create a vpn tunnel from one site to another.  However, the site currently has a Sonicwall firewall appliance in place already.  I was thinking about just using the PIX as just a gateway on one end of the vpn tunnel and not have it act as a firewall.  Does anyone know if this is possible?  Is there a way to disable the firewall features on a PIX?  Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:55:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385791#M551701</guid>
      <dc:creator>jet.pak</dc:creator>
      <dc:date>2020-02-21T07:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: Using PIX without firewall features.</title>
      <link>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385792#M551703</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To disable the firewall protection on a PIX, you would have to do this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inbound permit ip any any&lt;/P&gt;&lt;P&gt;access-group inbound in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That would effectively open the flood gates.  The real question is do you really want to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would first consider a few options/issues:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. How many public IP addresses do I have?  If you have more than one available, could you run the PIX with another available IP address and have whichever device that is acting as the default gateway route traffic destined for the remote VPN endpoint to the PIX?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If you only have one available public IP address, can you replace the SonicWall with the PIX?  Even a PIX 501 with a 10-user license has a throughput of 3mpbs (approx. 2 T-1s) when using 3DES encryption.  The point being that the available bandwidth would more than cover even small offices while providing a secure tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. It sounds like what you want to do is to create a tunnel not from network edge to network edge but from inside network to inside network.  Will the SonicWall (plus whatever is at the remote end) handle this?  Remember that there are NAT issues to resolve and the proper ports must be opened at least at the far end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just some things to think about.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doug Zitzelsberger&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:dougz@lebanon-utilities.com"&gt;dougz@lebanon-utilities.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2005 22:48:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385792#M551703</guid>
      <dc:creator>dougz</dc:creator>
      <dc:date>2005-02-08T22:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: Using PIX without firewall features.</title>
      <link>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385793#M551705</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I forgot the nat and global statements.  A wide open config should look more like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 1 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;access-list inbound permit ip any any&lt;/P&gt;&lt;P&gt;access-group inbound in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just wanted to clarify.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doug.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2005 22:53:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385793#M551705</guid>
      <dc:creator>dougz</dc:creator>
      <dc:date>2005-02-08T22:53:41Z</dc:date>
    </item>
    <item>
      <title>Re: Using PIX without firewall features.</title>
      <link>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385794#M551706</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is only wide open from inside to outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To open from outside to inside you need to configure static's to go along with the ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example if you are using 10.0.0.0/24 on your inside interface then this is what your static would look like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 10.0.0.0 10.0.0.0 netmask 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2005 22:57:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385794#M551706</guid>
      <dc:creator>dbellaze</dc:creator>
      <dc:date>2005-02-08T22:57:10Z</dc:date>
    </item>
    <item>
      <title>Re: Using PIX without firewall features.</title>
      <link>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385795#M551707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Doug, thanks for the reply.  In a perfect world, I'd like to replace the Sonicwall appliance with the PIX.  However, the Sonicwall is handling voice traffic.  I'm not sure If I can completely do away with it....I have no experience with the Sonicwall unit.  My client is very reluctant to remove it as well.  Hence, the reason to change the role of the PIX.  I'm pretty sure my client has several public addresses........so, your first option is something I'll have to investigate further.  There will certainly be NAT issues to resolve.  Perhaps I can disable the firewall features of the Sonicwall instead.....maybe that's a better solution?  ...This way the PIX can be the VPN gateway and be a firewall.  I don't know if this scenario would be any easier...but i'm considering it.  Thanks again for your input.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2005 13:56:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/using-pix-without-firewall-features/m-p/385795#M551707</guid>
      <dc:creator>jet.pak</dc:creator>
      <dc:date>2005-02-09T13:56:36Z</dc:date>
    </item>
  </channel>
</rss>

