Static Route configuration on ASA Firewall

I have attached a simple diagram on what i have.
Essentially on a Cisco ASA i am trying to create a static route to another router.
For this reference i will call the Cisco ASA Router A
On router A we have our LAN interface which is 192.168.0.1 on a /24
We have PCs on this network.
There is a uplink to another router B.
Router B has a IP of 192.168.0.254

Then Router B has a subnet of 192.168.254.0/24

To me it appears it be a issue on the Router A configuration.
Here is my testing.

Test 1:
If i do a PING from Client B to Client A. (192.168.254.100 => 192.168.0.100)  I run a wireshark on client A.  I see ICMP traffic coming in, and responses going out.  But a wireshark on Client B does not show the response.
In this same test i have ran a capture on Router B eth0/1 and i do not see the response.
This woudl lead me to believe that Router A is dropping the response.

Test 2:  
If i do a PING from client B to Router A. (192.168.254.100 => 192.168.0.1) Responds correct.

Test 3:
If i do a PING from Router A to client B (192.168.0.1 => 192.168.254.100) Responds correct.

What could i be missing in my configuration?

Cleaned-Config.txt
Digram
tsukrawAsked:
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.

JustInCaseCommented:
According to your drawing route on Router A supposed to be:
route inside 192.168.254.0 255.255.255.0 192.168.0.2 1
0
tsukrawAuthor Commented:
Sorry about that. That was a typo on the diagram.  Diagram has been updated.
0
JustInCaseCommented:
Is ICMP inspected? If it is not, ICMP should be permitted in opposite direction.
access-group outboundtraffic in interface inside

Open in new window

0
tsukrawAuthor Commented:
Figured it out.
Added these two lines to the attached config. Once these were in things took off.

access-list bypassnat extended permit ip 192.168.0.0 255.255.255.0 192.168.254.0 255.255.255.0
nat (inside) 0 access-list bypassnat
1

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
tsukrawAuthor Commented:
Figured out solution.
Posted solution.
0
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
ASA

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.