Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Cisco Pix Firewall not routing our privite frame traffic...need help bad.

Posted on 2004-04-12
Medium Priority
Last Modified: 2013-11-16
We currently have a PIX Firewall running a very old IOS. Version 4.4 I think. It is used for a small company firewall. It connects to an AT&T router that gives us internet access. We also have a separate Frame line that connects a separate office to us via a 56K frame.  Our problem is we need to be able to route though the Frame connection when we try to get to a We are using the PIX as our gateway but so far I can not PING from my workstation I can Telnet into the PIX and do a Ping from the Pix to a workstation on the other end of the frame and it works great. It is like the PIX is not allowing the data from the FRAME to be routed.

There is a fairly good chance this post will make little sense to some so please ask questions I will answer them as I can.

Thanks for the help guys

Question by:tabmpierce
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Expert Comment

ID: 10807922
Not sure if I understand you correctly, but are you saying that both sites have the same subnet address range? (192.168.1.x/24) --that would be an issue, yes?

when your at site A (at and you try to ping at site B it doesn't go through any gateway b/c it's the same subnet.

I assume it works from the Pix b/c it's default route is NOT going back to 'site A'

When setting up 2 sites like this, I've only used different subnets so that there's no mistake when routing...
LVL 31

Expert Comment

by:Gareth Gudger
ID: 10808204
The PIX firewall might also be blocking ping requests. Have you also updated you PIX firewall firmware yet....just for security purposes :)

Expert Comment

ID: 10808322
Can you please post your PIX config without security details.  We can most likely give you an answer in short order if you post the config.
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.


Expert Comment

ID: 10808740
As I understand it, the PIX will not perform routing.  You must forward all your traffic inbound from the outside interface to a router that is capable of routing the traffic.  It will, of course, happily ping anywhere you like so long as it's default gatway or RIP table knows how to find that network.

Expert Comment

ID: 10809046

is this the way your network is connected ?

Internet <---> AT&T Router <----> PIX <----> Internal Network


Author Comment

ID: 10809434
Aaah Thank you all for Writing ...OK let me answer the questions.

ICMP is ON so pinging works till the issue is resolved.

I can not update the Firmware because newer versions of the PIX firmware limit the number of connections (LOL that should give you a clue to how old the IOS is)

Everyone in the office uses the PIX as it's gateway.

Robing66066 brought up a interesting comment.  I am trying to route the traffic from the internal network to the frame network useing routing statments on the PIX. Can anyone confirm that the PIX will not do routing?

I like the picture so I will use it to illistrate what I am trying to show you guys.

                                                 no IP           
Internet <---> AT&T Router <----> PIX <----> Cisco Switch <--->Internal Network
                                              (GATEWAY)            |
                                                              (internal home office IP address)
                                                              (Frame cloud IP address home office)
                                                              (Frame cloud IP address remote office)
                                                             (internal Remote office)

Author Comment

ID: 10809444
When I make it back into the office I will post the config minus the security information and maybe that will help.

Thanks guys =)
LVL 12

Expert Comment

ID: 10809459
You should make every effort to acquire the newest software for the PIX. If you are the original purchaser of the device, you should be able to get it covered under a SmartNET contract, which would entitle you to software upgrades.

Once that's done, re-write your configuration to get rid of conduits and move to access-lists to control traffic (we can help you convert the rules).

This will shore up the security quite a bit.

Now, to answer your questions - you need to define rules in the PIX that prevent traffic originating at your network and heading to the other private network from being address translated. Then, you need to open the appropriate holes for the traffic to move back and forth. All of this is much easier to do when you run the newer software, and don't have to use conduit statements...
LVL 11

Expert Comment

ID: 10814907
You have two gateways on your network -- the PIX, and the FR connection.  What you are trying to do is have the PIX forward any traffic it receives from the internal network that is intended for FR back across the internal network to the FR gateway.

IF the PIX was a router (Cisco says it's not, but what do *they* know...), it would do that forwarding, and send the clients an "ICMP redirect" message saying "You don't have to come through me to get there."  (Which most clients would ignore, but that's another story.)

Your simplest option would be if both the PIX and the FR gateway could hang off the same internal network address, perhaps by introducing a small router between them and the rest of the internal network.  You'd have to introduce a separate (private) subnet joining the three devices.

The "obvious" alternative is to add a route on each client that needs to talk via FR (which might be all of them in your case), telling them that traffic to 192.168.1.x needs to be sent to instead of the default gateway.


Accepted Solution

Pascal666 earned 2000 total points
ID: 10815578
A PIX will not route traffic back out the same interface it received it on.  Your easiest solution is to change your DHCP server so the default gateway it hands out is your frame relay router.


Author Comment

ID: 10921340
Pascal666 your comment answered my problem. I made the Frame relay route the traffic. Works great. Thanks a ton guys!!!

Featured Post

WEBINAR - Latest Cyber Tips for Defense

Join the WatchGuard Threat Research Team on October 26th for an informative webinar featuring expert tips and tricks for defending your organization from today's latest cyber threats. Don't leave yourself vulnerable to attack. Register for the webinar today!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

During and after that shift to cloud, one area that still poses a struggle for many organizations is what to do with their department file shares.
This program is used to assist in finding and resolving common problems with wireless connections.
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses

610 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