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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

501 Pix config

Status
Not open for further replies.

phaseshift

IS-IT--Management
Dec 13, 2004
45
0
0
US
I have been working with this cisco firewall for a week now and no farther than when I started. Could some please look at my config and tell me what i am doing wrong.
Thanks

my inside network is 192.168.2.x
my outside network is 192.168.1.x
my dsl modem is 192.168.1.2

interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname elgmainpix
domain-name elgmain.local
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 192.168.0.224 255.255.255.240
access-list outside_cryptomap_dyn_20 permit ip any 192.168.0.224 255.255.255.240
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 192.168.1.10 255.255.255.0
ip address inside 192.168.2.10 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPN_Pool 192.168.0.230-192.168.0.235
pdm location 192.168.2.2 255.255.255.255 inside
pdm history enable
arp timeout 14400
global (outside) 1 192.168.2.14
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
rip inside default version 2
route inside 0.0.0.0 0.0.0.0 0.0.0.1 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 uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server RADIUS (inside) host 192.168.2.2 timeout 10
aaa-server LOCAL protocol local
http server enable
http 192.168.2.2 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
floodguard enable
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
 
delete
route inside 0.0.0.0 0.0.0.0 0.0.0.1 1
add
route outside 0.0.0.0 0.0.0.0 192.168.1.2 (The address of the DSL modem)
That should get internet access working from the 192.168.2.0 network.

You have RIP configured. Do you have another router/more networks on the inside? 'Sho route' will tell you if those routes are being learned.

Looks like you are trying to enable VPN access from the internet, but you are using private addresses on the outside of your firewall. Do you have a static NAT/PAT entry on your DSL modem that will direct inbound connections to the firewall? Your life will probably be much easier if you can have your ISP give you a real address range to use internal to the modem and turn NAT off on the DSL modem.
 
Thanks, I will try this and let you know what happens. It seems like I have had that line in before. But then I have tried a lot of things.

The end goal is to get VPN. I will call my isp and see if we can turn off nat. the problem is that the isp will not let use config the dsl box.

thanks for the help
 
No luck.

I added that route and nothing.

anymore ideas?
 
What is it that you are trying to do? Just get internal users to access the Internet? What sort of connection are you using?
 
first i would just like to get the internet and firewall configured for internal users.

once i have that done then I will work on the vpn.

right now if i plug that config into the pix, from the inside network i can't ping the outside.

I have a DSL conection coming into the building.
 
This is confusing ..

ip address outside 192.168.1.10 255.255.255.0
ip address inside 192.168.2.10 255.255.255.0
!
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
global (outside) 1 192.168.2.14

You are NATing all the traffic from your internal network to another INTERNAL address. You need to be NATing internal users to your external address. Presuming that your DSL modem is NATIng traffic from the 192.168.1.0 network correctly, you could use ..

global (outside) 1 interface

This will NAT outbound traffic to the IP address of the outside interface, ie. 192.168.1.10 which should then be NATed by your DSL router.

Chris.



**********************
Chris A.C, CCNA, CCSA
**********************
 
I know this is confusing.

Let me preface that I am working with someone else's config. I just started 2 weeks ago and am trying to get this thing working. I haven't worked with cisco products in a few years and i am rusty.

here is my current config with the new change and i still can't get to the internet.

thanks for the help.

PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname elgmainpix
domain-name elgmain.local
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 192.168.0.224 255.255.255.240
access-list outside_cryptomap_dyn_20 permit ip any 192.168.0.224 255.255.255.240

pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 192.168.1.10 255.255.255.0
ip address inside 192.168.2.10 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.2.2 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
rip inside default version 2
route inside 0.0.0.0 0.0.0.0 192.168.2.1 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 uauth 0:05:00 absolute
http server enable
http 192.168.2.0 255.255.255.0 inside
http 192.168.2.2 255.255.255.255 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
terminal width 80
 
on the latest config you are missing
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
to match up with
global (outside) 1 interface

Can you ping your DSL router from the pix?
 
I can ping the dsl router from the outside interface but not the inside.
 
There is a problem with your access-list. I would recomend you save a copy of that current config on floppy or of tftp server. After that, restore the pix to factory default settings.

When you first got there did this pix work at all?

Are there any users on the outside interface: ip address outside 192.168.1.10 255.255.255.0? and if so can any of them access the internet.

access-list inside_outbound_nat0_acl permit ip any 192.168.0.224 255.255.255.240
access-list outside_cryptomap_dyn_20 permit ip any 192.168.0.224 255.255.255.240

These two access-list does not pertain to your inside interface, and by the looks of it you have not applied any of these access-list to an interface using the access-group command.

By dafault the pix 501 firewall will allow tcp/ip traffic from a higher security setting to a lower one. How many programable interfaces are there on this PIX firewall you have?
 
As these access lists are not applied to any interface they will not affect access. The Pix in question here is a 501 and so they only have an inside and and outside so by default all traffic will be permitted outbound from the LAN.

Chris.

**********************
Chris A.C, CCNA, CCSA
**********************
 
First off, thanks to everyone.

OK no this PIX never worked so starting with the factory default is what I am going today.

Today i also got my ISP to push our static Ip address to the outside interface of the PIX. I hope that makes it a little easier.

I will try it will all the config info I have been given so far and come back

Larry
 
I got it working last night.

thanks for all the help.

Your config help and the new modem from my isp solved the problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top