PIX 501 Setup. Getting there.....

[stevep]

Hi folks.
First off, thanks for a great website, regularly check in to see what's new.

I've been running a simple home network for a while with a combination of Macs and PC's a Wii, an Apple TV and a couple of Nintendo DS's

Network hardware is as follows.

Zoom ADSL Modem
Smoothwall running on Micro ATX box
Linksys WRT54GS wireless router V3.37.2
Apple Airport Extreme Gigabyte version

The Linksys router provides wireless B and G and the Airport Extreme is wireless N only.

This set up works in the following hardwired setup :-

Modem -> Red Interface - Smoothwall - Green Interface -> Linksys -> Airport Extreme

I've recently got hold of a Cisco PIX501. It might seem overkill but it was in new condition and was pretty damn cheap.

I know it's a big ask for my first post but I would be very grateful for some advice in getting the setup of the PIX correct.
I'm part way there I believe.
I'm wanting to replace the Smoothwall with the PIX.

I've got it set up as follows.

Modem -> WAN Interface PIX Internal Interface 1/4 -> Linksys
Internal Interface 2/4 -> Airport Extreme

I have got so far with the setup of the pix.
I can connect to the modem and change it's settings on its web page, via the Linksys or Airport extreme. ( I switch my Mac Book Pro between the two.)
The only thing I can not do is get out through the firewall to the Internet.
IP settings are as follows.

Modem Internal Static 192.168.0.1
Pix External Static 192.168.0.40
Pix Internal Static 192.16.8.1.1
Linksys Static 192.168.1.2 DHCP enabled .100 - .150 Gateway mode
Airport Static 192.168.1.220 Bridge mode

I suspect I've got far too much defined in the PIX setup. A result of trying lots of different things to get it working. Would be happy to start again with a default setup and work from there.

Anyway, here goes, the PIX config is :

: Saved
: Written by enable_15 at 22:18:02.460 UTC Wed Apr 30 2008
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxxxxxxxx encrypted
passwd xxxxxxxxxxxx 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
access-list acl_out permit icmp any any
access-list 100 permit icmp any any echo-reply
access-list 100 permit icmp any any time-exceeded
access-list 100 permit icmp any any unreachable
access-list inbound permit tcp any host 192.168.1.2 eq www
pager lines 24
logging buffered debugging
mtu outside 1500
mtu inside 1500
ip address outside 192.168.0.40 255.255.255.0
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 0.0.0.0 255.255.255.255 outside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 192.168.0.45-192.168.0.200
global (outside) 1 interface
nat (inside) 1 192.168.1.0 255.255.255.0 0 0
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group acl_out in interface outside
route outside 0.0.0.0 255.255.255.255 192.168.0.1 1
route outside 0.0.0.0 0.0.0.0 192.168.0.8 1
timeout xlate 3:00: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
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.254 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:xxxxxxxxxxxxxxxxxxxxxx

Cisco PIX Firewall Version 6.3(5)
Cisco PIX Device Manager Version 3.0(4)
Compiled on Thu 04-Aug-05 21:40 by morlee
pixfirewall up 18 days 12 hours
Hardware: PIX-501, 16 MB RAM, CPU Am5x86 133 MHz
Flash E28F640J3 @ 0x3000000, 8MB
BIOS Flash E28F640J3 @ 0xfffd8000, 128KB
0: ethernet0: address is xxxxxxxxxxxxxxxx, irq 9
1: ethernet1: address is xxxxxxxxxxxxxxxx, irq 10
Licensed Features:
Failover: Disabled
VPN-DES: Enabled
VPN-3DES-AES: Enabled
Maximum Physical Interfaces: 2
Maximum Interfaces: 2
Cut-through Proxy: Enabled
Guards: Enabled
URL-filtering: Enabled
Inside Hosts: Unlimited
Throughput: Unlimited
IKE peers: 10
This PIX has a Restricted (R) license.
Serial Number: xxxxxxxxxxxxxxxxxxxx
Running Activation Key: xxxxxxxxxxxxxxxxxxxxxxx
Configuration has not been modified since last system restart.

Any of you tech types have any ideas as to where I'm buggering it up?

Cheers,
Steve

 

[YeOldeStonecat]

You're double NAT'ing there...unless you have your Linksys as an access point only (uplinked via LAN port w/DHCP disabled).

IMO the old PIX 501 is a "downgrade" performance wise from your Smoothie box. But just to learn 'n piddle...why not configure it via the easy WebGUI interface? It's has a little connection wizard much like a regular home grade router like the Linky.

 

[stevep]

Hi.
Thanks for the reply.
Yeah, with my working Smoothwall setup, I'm NATing with the modem.
External IP to 192.168.0.1
Again in the Smoothwall 192.168.0.40 to 192.168.1.x

Both the Linksys and Airport are connected to the Smoothie using the LAN ports and not the WAN ports. Everything inside the Smoothie is using 192.168.1.x

I want to achieve this using the LAN ports on the PIX.

Modem -> PIX -> Pix LAN ports to LAN ports on the Airport and Linksys.
Going to let the PIX handle DHCP on the 192.168.1.x network.
As I said, I've got the PIX working to the point where I can set it up wirelessly using the Web interface via the Airport or the Linksys. Whichever I connect to.
I can also reach the admin web pages of the modem through the PIX, changing its settings or rebooting.

I have not changed the settings on the modem so I'm lost as to why I cannot reach the internet through the PIX. I suspect my DNS and/or NAT and/or Routing setting in the PIX are screwed up. Not sure where though.

Cheers,
Steve

Edit to add:
I've used the web interface and wizard to configure the PIX. Still a bit stuck though. Any help would be very gratefully accepted.

 

[Brandon]

dhcpd address 192.168.1.2-192.168.1.254 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside

I think this is your problem, if you're using a private address staticed on the outside, the inside interface won't recieve DNS info.

Try this:

enable
dhcpd dns 4.2.2.3 interface inside
write config


That is a very very well known DNS server that stays up constantly, I always use it when not hosting my own DNS server, as my ISP's constantly goes down. If you host your own, you can always use that IP instead (192.168.x.x).

Hope this helps!

 

[stevep]

Brandon,
Many thanks. When I get a minute, I'll give it a go!
Cheers,
Steve

 

[stevep]

wohoo!!!!
working.
I did wonder if it was a DNS problem but wasn't sure how/where to set it up.

Added this command which got things going (it didnt like the interface inside bit though)
Once working, I tried it with the dns address's supplied by my ISP.
Everything running smoothly!
Thanks a million.

 

[Brandon]

Yeah, sorry about that. I'm a bit rusty on PIX commands, most are along the same as the ASA, so it's an easy guess >.>.

Most of the time, if you can see things via IP address, it's a DNS issue, just a matter of finding said DNS issue .

 

[Tamarin]

For the DNS server, a good free alternate is 208.67.222.222 which is run by OpenDNS. Check out their site, (www.opendns.org) you can do all kinds of neat things with it, all for free.

Tam

 

[Brandon]

I still like hosting my own. I never was one for finding PC's via IP addy.

I currently use Active Directory to manage my home DNS, while using 2003 DHCP. This also functions as a web Name Server for several webpages I host (Mostly backend/subdomains).

WinBIND also makes a DNS service that's Linux based for those looking for a free and easy solution.