Archived from groups: comp.security.firewalls (More info?)
Here's what should be a simple config issue... We have a PIX501, and a
web server behind it. I need everyone from the Outside
interface to be able to view our website sitting behind the firewall at
an internal address. I've done this on many other firewalls, but it's
not intuitive to me how to accomplish this on the PIX 501. Can anyone
tell me the easy way to accomplish this either on the command line or
by adding a new access rule in PDM?
Here is my currnet config that does not work (try not to laugh):
Archived from groups: comp.security.firewalls (More info?)
In article <1125447672.331715.14670@g43g2000cwa.googlegroups.com>,
<michael@culpeppertech.com> wrote:
:Here's what should be a simple config issue... We have a PIX501, and a
:web server behind it. I need everyone from the Outside
:interface to be able to view our website sitting behind the firewall at
:an internal address.
IX Version 6.3(4)
:name 192.168.4.192 WEB
bject-group service HTTPHTTPS tcp
: port-object eq www
: port-object eq https
:access-list inside_outbound_nat0_acl permit ip any 192.168.4.80 255.255.255.240
:access-list outside_cryptomap_dyn_20 permit ip any 192.168.4.80 255.255.255.240
:access-list outside_cryptomap_dyn_40 permit ip any 192.168.4.80 255.255.255.240
Your VPN pool must always be "outside" relative to your inside interface.
Otherwise the return traffic will not be able to get to it. This will
affect your inside_outbound_nat0_acl and outside_cryptomap_dyn_* ACLs.
dm location 192.168.11.0 255.255.255.0 inside
That line, though not actually a functional line, is wrong, as
192.168.11.0 is not "inside" and you have no "route" statement
pointing that subnet to the inside interface.
:global (outside) 1 interface
OK.
:global (inside) 2 interface
?? global (inside) would only be used in rather uncommon reverse-NAT
configurations, which you are NOT using. And you don't have a
nat (outside) 2 statement to match that global (inside) 2.
If RCMSWEB is what you named as WEB earlier then you are static'ing
a private IP (192.168.4.192) to be translated to itself when it goes
outside. That's not going to work.
:crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
:crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
:crypto dynamic-map outside_dyn_map 40 match address outside_cryptomap_dyn_40
:crypto dynamic-map outside_dyn_map 40 set transform-set ESP-3DES-MD5
outside_cryptomap_dyn_20 and outside_cryptomap_dyn_40 have the same
contents, so those two policies duplicate each other. You probably
only want one of the two.
access-list outside_cryptomap_nonat permit ip any 192.168.255.80 255.255.255.240
access-list outside_cryptomap_dyn_20 permit ip any 192.168.255.80 255.255.255.240
vpngroup rcmsremote address-pool VPNIP
--
'The short version of what Walter said is "You have asked a question
which has no useful answer, please reconsider the nature of the
problem you wish to solve".' -- Tony Mantler
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.