Pix515 basic config not working

[nupix]

Here is our current running config and we just are at a loss. We have a simple test bench setup and can't even ping to the outside interface of pix from an inside host.

1)What access-lists should we add to allow http in and out, allow pinging and show basic routing connectivity for testing situation?

2)Can the acls when applied co-exist with conduit statements or will we have to delete the conduits?

3)Should pix be used for DNS or how do we set it up to be DNS proxy.

4)How do we set up pix properly to allow any address range or client address to VPN in with the cisco VPN client?

5)Is there a problem gettting it to work because of the ipsec and crypto/DES policy we have set up in the config?

Here is our current config:




Welcome to the PIX firewall

:
PIX Version 6.1(1)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname gahifirewall
domain-name gahi.com
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 1720
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
fixup protocol domain 53
names
name 192.168.0.3 officeduron3
access-list vpn1 permit ip 192.168.1.0 255.255.255.0 10.0.0.0 255.255.0.0
pager lines 24
interface ethernet0 auto
interface ethernet1 auto
mtu outside 1500
mtu inside 1500
ip address outside 65.190.36.213 255.255.255.252
ip address inside 10.0.0.1 255.255.0.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpnclients 10.0.70.1-10.0.70.101
pdm location officeduron3 255.255.255.255 outside
pdm location 10.0.0.0 255.255.0.0 inside
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) 10.0.0.1 65.190.36.213 netmask 255.255.255.255 0 0
conduit permit icmp any any echo-reply
conduit permit icmp any any source-quench
conduit permit icmp any any unreachable
conduit permit icmp any any time-exceeded
route outside 0.0.0.0 0.0.0.0 65.190.36.214 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 si
p 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
http server enable
http 10.0.0.0 255.255.0.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
tftp-server inside 10.0.0.200 local
floodguard enable
sysopt connection permit-ipsec
sysopt noproxyarp outside
sysopt route dnat
crypto ipsec transform-set vpntrans1 esp-des esp-md5-hmac
crypto dynamic-map inboundvpns 99 set transform-set vpntrans1
crypto map basicsecurity 99 ipsec-isakmp dynamic inboundvpns
crypto map basicsecurity client configuration address respond
crypto map basicsecurity interface outside
isakmp enable outside
isakmp policy 1 authentication pre-share
isakmp policy 1 encryption des
isakmp policy 1 hash md5
isakmp policy 1 group 2
isakmp policy 1 lifetime 86400
vpngroup gahi address-pool vpnclients
vpngroup gahi idle-time 1800
vpngroup gahi password ********
telnet 10.0.0.0 255.255.0.0 inside
telnet timeout 5
ssh timeout 5
dhcpd lease 3600
dhcpd ping_timeout 750
terminal width 80
Cryptochecksum:214e3dc62d63adc3f95ad34b555c757f
: end
[OK]
gahifirewall(config)#

 

[yizhar]

HI.

> ip address outside 65.190.36.213 255.255.255.252
> ip address inside 10.0.0.1 255.255.0.0
> static (inside,outside) 10.0.0.1 65.190.36.213
Do not overlap the addresses. Remove that static command.

> conduit permit icmp ...
Use access-list instead.
conduit commands will work but they are for backward compatibility and should not be used on a new pix.

http://www.cisco.com/warp/public/707/28.html

http://teachers.sivan.co.il/yizhar/files/pixlinks.htm

> can't even ping to the outside interface of pix from an inside host
This is by design.
Try to telnet or ping the router instead.

> 1)What access-lists should we add to allow http in and out
Outbound traffic is permitted by default.
For inbound http traffic, use "static" and "access-list".

> 2)Can the acls when applied co-exist with conduit statements or will we have to delete the conduits?
Don't use a mix of ACL and conduit, because it will just make management and troubleshooting much more dificult for now reason.

> 3)Should pix be used for DNS or how do we set it up to be DNS proxy.
The pix can not be used as DNS proxy.
The best option is to implement internal DNS server.
The second option is to use ISP servers.

> 4+5) ... VPN ...
The VPN configuration seems OK.
Start testing it with a workstation connected directly to the pix outside interface.

You should configure the pix to send syslog messages to buffer/PDM/syslog server.
This is a must for monitoring and troubleshooting the pix.
Start with level 4 (warnings), or 6 (informational).

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar