asked on

PIX 501 - VERY simple configuration

I have a VERY simple configuration of a PIX 501 Firewall. But I can not seem to get traffic to flow out (internet browsing for example). Your help is much appreciated:

Configuration:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxxxxxxxxxx encrypted
passwd xxxxxxxxxxxx encrypted
hostname xxxxxxxxxxx
domain-name xxxxxxxxxxxxxxxx
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 64.32.245.2 255.255.255.248
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPNPool 192.168.1.15-192.168.1.30
pdm location 192.168.1.0 255.255.255.0 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 64.32.245.1 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
vpngroup ACM-DR address-pool VPNPool
vpngroup ACM-DR dns-server 64.7.11.2 66.80.131.5
vpngroup ACM-DR default-domain xxxxxxxxxxxxxx
vpngroup ACM-DR split-dns xxxxxxxxxxxxxxxx
vpngroup ACM-DR idle-time 1800
vpngroup ACM-DR password ********
telnet 192.168.1.0 255.255.255.0 inside
telnet timeout 60
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.33 inside
dhcpd dns 64.7.11.2 66.80.131.5
dhcpd lease 1048575
dhcpd ping_timeout 750
dhcpd domain xxxxxxxxxxxxxxx
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:35ccca57704aed633429cb4377d3c241
: end

John Meggers

I don't see anything really wrong with the usual culprits -- NAT, routing, etc. But one thing I do notice is you're handing out addresses via DHCP that overlap with your VPN pool. I would suggest not doing this. The VPN address assignment does not use DHCP, and while I don't know for sure this is causing a problem, it strikes me as poor form. (If you eventually want to actually configure VPN, you will also want to "nat 0" (no-nat) anything going from the inside subnets to your VPN pool.)

So, basics. Can you ping the ISP address (default route) from the PIX? Can you reach any other internet addresses (e.g., public DNS servers)? Are you able to reach anything from the laptop by IP address or have you only tried by name? Is DNS working, can you do an nslookup on the client and get an appropriate response?

I'd suggest starting with those and see where that takes you.

ASKER CERTIFIED SOLUTION

ArneLovius

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

denver218

Can you ping the internet from the PIX (ping 4.2.2.2)
Can you ping 64.32.245.1? (route outside 0.0.0.0 0.0.0.0 64.32.245.1 1)

SOLUTION

ArneLovius

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

garyhahn1

ASKER

Thanks for the responses. I can NOT ping the next hop (64.32.245.1....the default route), nor can I do a successful nslookup from a machine inside. I have another Cisco RV4000 firewall set up with exact same configurations and it works fine. I'll try taking out the VPN addresses from the pool and see if that makes a difference....will also try adding the access-list:

access-list inside-to-outside permit icmp any any
access-list inside-to-outside permit ip any any
access-group inside-to-outside in interface inside

I will post results when finished.

Thanks!

SOLUTION

ArneLovius

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

John Meggers

You shouldn't need to permit traffic from the inside outbound because the security level on the inside interface is higher than the outside. But you won't allow ICMP responses back in unless permitted by an ACL because ICMP is not stateful. ASA handles this with application inspections that allow you to specifically track ICMP and allow responses back in.

garyhahn1

ASKER

Cable in Port 4 and permit ip 192.168.1.0 255.255.255.0 any was the solution.