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!

Newbie, PIX lab not working. Need help!

Status
Not open for further replies.

bitsecure

Technical User
May 9, 2005
5
0
0
US
Trying to setup simple lab. I want to be able to ping through the firewall and to the outside interface. Right now I can only ping the inside interface from the PC.

ROUTER 2520
|
PIX 501
|
PC

router 10.0.0.1
pix outside to router 10.0.0.10
pix inside 192.168.1.1
pc 192.168.1.202

Here is my configuration:

: Written by enable_15 at 16:52:29.244 UTC Mon May 23 2005
PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 3N0SDGOVYMVwOR1N encrypted
passwd uOLtDDXwBWaa4FP5 encrypted
hostname PIX501
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 inside_in permit tcp 192.168.1.0 255.255.255.0 any
access-list outside_in permit tcp any any
pager lines 24
logging on
icmp permit any echo outside
icmp permit any outside
icmp permit any echo inside
icmp permit any inside
mtu outside 1500
mtu inside 1500
ip address outside 10.0.0.10 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 logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 10.0.0.11-10.0.0.19 netmask 255.255.255.0
nat (inside) 1 192.168.1.0 255.255.255.0 0 0
static (inside,outside) 10.0.0.0 192.168.1.0 netmask 255.255.255.0 0 0
access-group outside_in in interface outside
access-group inside_in in interface inside
route outside 0.0.0.0 0.0.0.0 10.0.0.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 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 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
Cryptochecksum:0c609b96702353fac316bd3b27f924df
PIX501#


HOST --------------------------PIX---------------------2520ROUTER
192.168.1.202 in_192.168.1.1 out_10.0.0.10 10.0.0.1

Any advice appreciated.

Thanks.

 
That is not allowed by default. However you can still do it. Use the command 'management access outside'. This will allow you to ping the outside from the inside. But why would you ever need to? I am sure that enabling this has negative effects that I am not thinking of at this point, and if I was thinking of them I may never have told you about this. But since this is a test lab I suppose it is better to know.

Eddie Venus
 
Thanks EddieVenus,

I put in the command management-access outside but still could not ping the outside interface. Is there some other way to test connectivity between my pix and router? Are my nat and global statements correct. Sorry I'm totally new at pix and have been working on this using several sources but havent been able to make it work.
 
sure enough. I just did it on one of our PIXs and it did not work. A pix does not let traffic that enters an interface to leave via that same interface. magement-access inside makes it so that you can ping an inside interface from accross a VPN tunnel, which of course would generally be against that whole in and out via the same interface thing.

I know that this PIX is right and it doesn't work for me, so my first reaction is that this will not work for you either.

Why are you trying to do this again?
 
Okay,

Eventually I want the following setup:

Internet
|
Linksys
|
PIX
|
Router

I have a network lab (192.168.1.0) that requires internet access that I want to set up behind the PIX but I need the wireless router which faces the internet for others in the house on network (10.0.0.0). I worked a couple of weeks trying to make that setup work and could not. I decided to start with a simpler setup and work my way up but I still cant get it to work. I'm not so concerned with pinging the firewall as i just want to verify my config and pass traffic which i cant seem to do.
 
Thanks to all who responded.

I reworked my config to include the Linksys router. I can now ping to the inside and outside interfaces of the pix both to and from the pix but still cant get traffic across. I think the problem is with my NAT and global statements. I'm working on that now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top