<?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: Simple PIX Question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/353828#M552006</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes it is.  What I would do *if possible* is to group the machines that keep their outside global addresses together so that I could create an access list to cover them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.e.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list nonat permit ip 10.10.10.0 255.255.255.224&lt;/P&gt;&lt;P&gt;nat (outside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This allows the first 32 (-2) IP addresses through the firewall with no address translation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also want to restrict the traffic types as well.  My suggestion is to keep traffic flow and traffic filtering lists separate.  So if I have a webserver in the above mentioned subnet, I would write the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inbound permit tcp 10.10.10.3 255.255.255.255 eq www&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doug.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 Jan 2005 14:33:39 GMT</pubDate>
    <dc:creator>dougz</dc:creator>
    <dc:date>2005-01-31T14:33:39Z</dc:date>
    <item>
      <title>Simple PIX Question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/353827#M552005</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's been a while since I've done any work with a PIX and as such I'm a little rusty with them. I'm wondering if someone that's a little more familiar with them my be able to answer my question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a /24 block of public IP addresses that are currently being used for various Linux Servers + AS5300's. I'd rather keep it as one solid block with out subnetting it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a number of Windows 2000 servers that run various PSTN switching + SQL applications that will be installed on the same network. I don't wish to put these on the public internet no matter what safe guards are taken on the local machines. Thankfully we have a PIX 515 going spare.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From our net block is it possible to map individual/block of IP addresses from the outside interface to the inside interface of the pix as opposed to routing a block of addresses to the inside interface or performing a static mapping from public to private. The result I'm after is for the servers behind the PIX to have a public IP address which is passed through the PIX. So in effect the PIX would be acting as a firewalling bridge. Is this kind of setup possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alan&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:54:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/353827#M552005</guid>
      <dc:creator>alitster</dc:creator>
      <dc:date>2020-02-21T07:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: Simple PIX Question</title>
      <link>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/353828#M552006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes it is.  What I would do *if possible* is to group the machines that keep their outside global addresses together so that I could create an access list to cover them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.e.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list nonat permit ip 10.10.10.0 255.255.255.224&lt;/P&gt;&lt;P&gt;nat (outside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This allows the first 32 (-2) IP addresses through the firewall with no address translation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also want to restrict the traffic types as well.  My suggestion is to keep traffic flow and traffic filtering lists separate.  So if I have a webserver in the above mentioned subnet, I would write the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inbound permit tcp 10.10.10.3 255.255.255.255 eq www&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doug.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2005 14:33:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/simple-pix-question/m-p/353828#M552006</guid>
      <dc:creator>dougz</dc:creator>
      <dc:date>2005-01-31T14:33:39Z</dc:date>
    </item>
  </channel>
</rss>

