ASA 5505 Configuration - Static Route

I am configuring a Cisco ASA 5505 and need to add a static route.  My internal network is 10.1.1.x and the internal IP address of the ASA is 10.1.1.1.  One service we use is connected to a router on the network with an IP of 10.1.1.12.  I need to route all traffic to the 192.108.200.X network through 10.1.1.12.  I thought it would be as simple as adding a route, which I did.  The command I used added a static route to the inside interface so that all traffic to 192.108.200.x goes through gateway 10.1.1.12 metric 2.  No go.  Is this even possible on the ASA 5505?  I've read some articles that seem to indicate this isn't a router and can't do that.  If it is possible, do I need an ACL?  I didn't think so as all internal traffic is allowed out to the internet and all internal devices can communicate with each other.
mikerich61Director of TechnologyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lrmooreCommented:
Yes, it can route, but probably not in the sense that you think.
The metric should be "1" and not 2 because the next hop is directly connected on the inside. But that is irrelevant.

What it won't do is allow you to have the ASA as the LAN default gateway and re-route packets that come from your PC going to 192.108.200.x, hit the inside ASA, then redirect them back out the same interface to the other router.
You have to have a default route on this other router pointing to the ASA, then point your PC's default gateway to this router and not the ASA. Routers can "bounce" the packet off to another locally connected gateway whereas the ASA cannot.
0
JimmyLarssonCommented:
As long as it is an ASA and not a Pix it[ running verion >7.0. In this case you can indeed reroute traffic back on the ingress interface. Here is some more information about this:

http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a0080734db7.shtml

Br Jimmy Larsson
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.