How to configure an ASA 5510 to route VPN client traffic back out through a tunnel?
What must be done to allow user traffic to come in from a remote user (using a Cisco VPN client on their latp) via the ASA's Outside interface and then have that traffic turn around and go back out via an ASP's VPN tunnel on that same outside interface?
I'm moving VPN clients and ASPs' branch office tunnels to a new Cisco ASA 5510. The clients work fine, the tunnels to branch ASP sites work fine. But home users who connect to this 5510 via the Cisco VPN client isn't getting their pings or traceroutes or applications to ASP's that are in the branch office tunnels.
Inside my network, I can ping & traceroute to the ASP's devices through the tunnels. I can also ping & trace to home users via their VPN client connections.
Somewhere I'm missing something in the ASA that will allow the home user to ping & trace to the ASP via the VPN tunnel to the ASP.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...