Forum Discussion

Richard_H__Norw's avatar
Richard_H__Norw
Icon for Nimbostratus rankNimbostratus
Mar 15, 2010

ASA and F5 Configuration Routing issues

I hoping that someone else has experienced this problem or can recommneded some a solution or possible troubleshooting technique that I have not tried.

 

 

Configuration:

 

 

ASA -> (10.0/24) -> F5 -> (30.0/23) -> Internal Network

 

\

 

\-> (30.0/23) Internal Network

 

 

1. Path one (ASA -> F5 -> Internal) is for application traffice.

 

2. Path two (ASA -> Internal Network) is for VPN traffic.

 

 

Problem:

 

 

The problem I'm running into is when my workstation is connected to the ASA VPN (40.0/24).

 

 

I'm able to ping from my workstation to internal systems and the internal systems are able to ping my VPN IP.

 

 

Traceroutes do not appear to be working very well. Even when an internal system has its default route configured as the internal interface of the ASA.

 

 

For instance when attempting to ssh to an internal server from my workstation while connected to the VPN.

 

- inbound connections (my workstaition to the internal server) half work. The return bound traffic is not making it back to the workstations terminal.

 

- debugging in sshd doesn't reveal anything.

 

- it appears that some traffic from the sshd server is attempting to communicate through the F5.

 

 

Any pointers would be appreciated.

 

 

Rick

 

 

 

1 Reply

  • can you clarify your infrastructure again? You have 30.0/23 specified twice above. Can you also specify what routing is in place for the ASA, the F5, and the Internal Servers?