Solved

Problems with static route on PIX 501

Posted on 2011-02-10
7
352 Views
Last Modified: 2012-05-11
I've been given a PIX 501. I have never had to work with one before now, so I am not sure i have the proper syntax.  

I have tried a static route:
static (inside,outside) tcp 10.xxx.xxx.42 192.168.51.242 netmask 255.255.255
.255 0 0

After entering the route, internet connectivity is lost and PC w/ IP 10.xxx.xxx.42 cannot ping 192.168.51.242.
Any ideas what i am doing wrong? Thanks in advance.
0
Comment
Question by:andrewferrer
  • 4
  • 3
7 Comments
 
LVL 24

Expert Comment

by:Ken Boone
Comment Utility
Well actually that is not a route.  That is a static route assignment.  What that statement says is the following:

take the "internal" ip address of 192.168.51.242 and NAT it on the outside as 10.x.x.x.    So that doesn't route anything.  It would be used to allow devices on the outside to access the inside ip address of 192.168.51.242  by going to the outside ip address of 10.x.x.x.

So if you want to route the statement looks like this:

route interface x.x.x.x y.y.y.y z.z.z.z

replace interface with the interface that the packet needs to route out.
replace x.x.x.x with the destination network
replace y.y.y.y with the subnet mask of the destination network
replace z.z.z.z with the next hop address to reach the destination.
0
 
LVL 24

Expert Comment

by:Ken Boone
Comment Utility
Excuse I said it was a static route assignment.  It is a static NAT assignment. ;)
0
 

Author Comment

by:andrewferrer
Comment Utility
Should I be able to ping 192.168.51.242 from 10.xxx.xxx.42 and vice-versa? When I add a static route I lose connectivity to the internet from 192.168.51.x devices. Thanks for your help. I'm a router config newbie.

Current setup:
Internet<-->ASA (inside:10.xxx.xxx.201)
                      |
                      |
      PC------------------------PIX (10.xxx.xxx.24)-outside
(10.xxx.xxx.42)                         (192.168.51.201)-inside
                                             |
                                             |
                                             |
                                          PC
                                   (192.168.51.242)  

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 5RBH8LS encrypted
passwd 2KI.2KYOU encrypted
hostname xxxx-xxx-x
domain-name xxxx
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_access_in permit tcp any any
access-list outside_access_in permit tcp any any
route iniside 10.xxx.xxx.42 255.255.255.255 192.168.51.201 1
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside dhcp setroute
ip address inside 192.168.51.201 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 10.xx.xx.0 255.255.255.0 outside
pdm location 0.0.0.0 255.255.255.0 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group inside_access_in in interface inside
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.51.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
snmp-server enable traps
floodguard enable
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.51.242-192.168.51.252 inside
dhcpd dns 10.xxx.xxx.7 10.xxx.xxx.10
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd domain xxxxxxx
dhcpd enable inside
terminal width 80
Cryptochecksum:87359fd82bf7
: end
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 
LVL 24

Accepted Solution

by:
Ken Boone earned 500 total points
Comment Utility
Ok to start with the PIX is connected to both the 10.x.x.x network on the outside and the 192.168.x.x network on the inside.

So it already has connected routes for those two networks.  That means you can remove this line:

route iniside 10.xxx.xxx.42 255.255.255.255 192.168.51.201 1

Secondly you have this configured:

global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0

This means that anything on the inside network when passing to the outside network will have its ip address NAT'd to the ip address of the outside interface of the PIX.

Thirdly you have this configured:

access-list inside_access_in permit tcp any any
access-group inside_access_in in interface inside

So what this does is allow all tcp traffic into the inside interface and blocks all other traffic by default.  As in it blocks udp and icmp packets.

So you might want to add this line:

access-list inside_acccess_in permit icmp any any

This will now allow the icmp packets to flow in to the inside interface.

But this still is not where you need to be although it will now let the return ping go through the inside interface.  The problem you face now is that the way the PIX/ASA work is that when you go from a lower security level interface (outside) to a higher security level interface (inside) you need to have a static NAT mapping AND an access-list rule allowing the traffic on the lower level security interface (outside).

So you need this:

static (inside,outside) 10.xxx.xxx.ZZ 192.168.51.242 netmask 255.255.255.255 0 0

The ZZ is a new ip address assignment that you are going to assign to the 192.168.51.242.  So what this does is makes the 192.168.51.242 look like 10.x.x.ZZ on the outside of the PIX.  So things on the outside will need to talk to the 192.168.51.242 by using the 10.x.x.ZZ ip address.

Lastly you need an access-list applied to the outside interface in order to make this work.  It would look something like this:

access-list outside_access_in permit tcp any 10.x.x.ZZ
access-list outside_access_in permit icmp any 10.x.x.ZZ

access-group outside_access_in in interface outside

Now that will allow any ip address to come in to the outside interface of that pix using TCP or ICMP (Pings) traffic when going to the new 10.x.x.ZZ address which will NAT to the 192.168.51.242 address on the inside.

Hope that helps.


0
 

Assisted Solution

by:andrewferrer
andrewferrer earned 0 total points
Comment Utility
"So you need this:

static (inside,outside) 10.xxx.xxx.ZZ 192.168.51.242 netmask 255.255.255.255 0 0

The ZZ is a new ip address assignment that you are going to assign to the 192.168.51.242.  So what this does is makes the 192.168.51.242 look like 10.x.x.ZZ on the outside of the PIX.  So things on the outside will need to talk to the 192.168.51.242 by using the 10.x.x.ZZ ip address."

Just to clarify, in the above statement, the "ZZ". Does the "ZZ" have to be the IP of the PC that I am attempting to ping from (10.xxx.xxx.42)? or does "ZZ" refer to a new IP address that I assign from a list of unused IP addresses? Thanks again for your assistance.
0
 
LVL 24

Expert Comment

by:Ken Boone
Comment Utility
The ZZ is a new ip address on the 10.x.x network that you will use that is currently unused.
0
 

Author Closing Comment

by:andrewferrer
Comment Utility
Thank you for your assistance.
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

Suggested Solutions

From Cisco ASA version 8.3, the Network Address Translation (NAT) configuration has been completely redesigned and it may be helpful to have the syntax configuration for both at a glance. You may as well want to read official Cisco published AS…
There are two basic ways to configure a static route for Cisco IOS devices. I've written this article to highlight a case study comparing the configuration of a static route using the next-hop IP and the configuration of a static route using an outg…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now