Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PIX 506E, What am I doing wrong w/ my Configuration

Status
Not open for further replies.

BlownOut

Programmer
Feb 4, 2005
4
0
0
US
Trying to get inbound/outbound access. I can ping 192.168.1.1 but that is all. Here's the config, Thanks!

PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt fef4444 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
domain-name ciscopix.com
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
object-group service HTTP tcp
port-object eq www
object-group service DNS udp
port-object range domain domain

access-list inside_access_in permit tcp any eq eq www
access-list outside_access_in permit tcp any any
access-list outside_access_in permit icmp any any
access-list outside_access_in permit udp any any

pager lines 24
mtu outside 1500
mtu inside 1500

ip address outside xxx.xxx.218.253 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
pdm logging informational 100
pdm history enable
arp timeout 14400

global (outside) 1 xxx.xxx.218.254
nat (inside) 1 0.0.0.0 0.0.0.0 0 0

access-group outside_access_in in interface outside
access-group inside_access_in in interface inside

route outside 0.0.0.0 0.0.0.0 xxx.xxx.218.248 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 uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
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
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.254 inside
dhcpd dns xxx.xxx.212.10 xxx.xxx.128.10
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 100
Cryptochecksum:1aa4a42e049a9f8d06f7417b2af80c18
 
You're not allowing any traffic out except tcp with source and destination ports equal 80. Probably not what you had in mind.

Start by removing "access-group inside_access_in in interface inside" and see what you have. Your outside acl allows all icmp, so ping should work as well as tcp & udp traffic. Then you'll want to trim the outside_in ACL as well.
 
Thanks lgarner,

I have removed the "access-group inside_access_in in interface inside" and I am still am not getting out. How should I define my ACLs and what should I trim in the outside ACL?
 
Well, it depends on what you want to do. Right now you're allowing all TCP, UDP and ICMP, which doesn't leave much that's *not* allowed.

The default for a Pix is to allow everything out and only responses to come in. For example, you should be able to surf the web from the inside without messing with ACLs.

Recheck your "route outside" statement to make sure it's pointed to the ISP router. It looks like it might be mixed up with the subnet mask, maybe it's ok.

There might be something else... it'll come to me eventually.
 
Regarding ACLs you should remember is that at the end of every ACL there is an implied deny all. So when you have an ACL, you better have it completely set up, or something will not function the way you plan. So far it looks like your inside_access_in ACL allows TCP connections but nothing else. Maybe you should either remove it, or change it to permit IP. Although maybe I'm wrong and the pix treats TCP and IP as a protocol suite instead of individual protocols.

Also, you should change your telnet password from cisco, as that is a security risk.

Computer/Network Technician
CCNA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top