• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

PIX 501 driving me crazy

RightIsWrong

Diamond Member
Hoping that someone here can help me.....

I have a PIX 501 that seems to work great when I connected it at home and had the outside interface set to get it's IP via DHCP. All pc's connected to it were able to get out to the internet without incidence.

I brought it in to work to connect it here....and the madness appears.

I have set the outside interface to the static IP and subnet that we have here and connected my laptop directly to the builtin switch and I am unable to connect.

I'm thinking that this is a problem with the default gateway, but I'm a newbie and couldn't find out where to set the gateway at. Also not sure if I have to manually set up DNS on it either.

Please help.....and try not to make too much fun of me 🙂
 
is the pix setup for inside dhcp or are you using another solution? you cannot set the default gateway on the pix. instead of probing every line of your setup, post your config 🙂
 
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password XX3tzWNzK9OooNx9 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname MyPix
domain-name Mydom
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
access-list inside_outbound_nat0_acl permit ip any 10.0.0.0 255.255.255.192
access-list outside_cryptomap_dyn_20 permit ip any 10.0.0.0 255.255.255.192
access-list outside_cryptomap_dyn_40 permit ip any 10.0.0.0 255.255.255.192
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside xx.xx.xxx.xx 255.255.255.252
ip address inside 192.168.0.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool MyRAS 10.0.0.25-10.0.0.34
pdm location 192.168.1.15 255.255.255.255 inside
pdm location 10.0.0.0 255.255.255.192 outside
pdm location 192.168.1.5 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
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
http 192.168.1.15 255.255.255.255 inside
http 192.168.1.5 255.255.255.255 inside
http 192.168.0.5 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
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
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
isakmp enable outside
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup MyRAS address-pool MyRAS
vpngroup MyRAS dns-server 24.93.40.62 24.93.40.63
vpngroup MyRAS default-domain Mydom
vpngroup MyRAS idle-time 1800
vpngroup MyRAS password ********
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
Cryptochecksum😀110c1aecd19a1a546c7e97cf75c5036
 
I have not played with Cisco in awhile but this looks odd to me.

nat (inside) 0 access-list inside_outbound_nat0_acl
access-list inside_outbound_nat0_acl permit ip any 10.0.0.0 255.255.255.192


ip address inside 192.168.0.1 255.255.255.0
 
Originally posted by: Genx87
I have not played with Cisco in awhile but this looks odd to me.

nat (inside) 0 access-list inside_outbound_nat0_acl
access-list inside_outbound_nat0_acl permit ip any 10.0.0.0 255.255.255.192

ip address inside 192.168.0.1 255.255.255.0
it may looks a little strange with an acl in a nat statement, but its used to specify the IP addresses that should not be translated.

is this for a site-to-site vpn connection? when you say you had the outside interface configured to get its ip via dhcp, were you referring to this command?

dhcpd auto_config outside

that command doesnt configure an ip, what it does it gets the dns, wins, and domain info from the outside interface for dhcp. do a show dhcpd to see if its really able to retrieve it. either way, try to enter it manually (i've had trouble with autoconfig on our network as well). i also dont see where you set the dhcp range or enable it on an interface. try this...

! configure the network parameters the client will use once connected
dhcpd address 192.168.0.2-192.168.0.50
dhcpd dns x.x.x.x
dhcpd wins x.x.x.x
dhcpd lease 3000
dhcpd domain whatever.com
! enable dhcp server daemon on the inside interface
dhcpd enable inside


i also dont see any route commands telling your pix where to route the inside traffic to.

route outside 0.0.0.0 0.0.0.0 outsideaddress 1

then again its friday, absolutely pouring out, and i have a headache. sorry if i make no sense lawl.

 
The config is OK, as far is it goes.

The problem, I believe, is that ou have no Default Gateway / Default Route / "Gateway of Last Resort" configured.

When you use DHCP on the WAN interface, it adopts the DG from the DHCP response. When ou statically configure the address, you must also configure teh DG.

ip route x.x.x.x m.m.m.m <gateway address> <optional metric>

Do you have permission to put that thing on your company's network? In most places, that would put your job at risk.

Whatever, Good Luck

Scott
 
Back
Top