External interface vpn connectivity for separate isp pipe
We currently have a ssl and fat client vpn connectivity from the public interface on isp1. The current ISP has a T1, but my second ISP has a DS3
I would like to configure a second isp totally different isp and different ip subnet on the external interface on a 3020 vpn concentrator
I believe this is possible, but worried about the routing as normally the default--> sends it to public. I would need the return traffic going out the external interface when the vpn user tries to make connectivity using ssl or fat cisco vpn client to the ip address of the external interface.
Re: External interface vpn connectivity for separate isp pipe
So, you are talking about asymmetric routing at the Concentrator end. If I understand correctly, all outgoing SSL traffic should exit through the external interface and the rest of the traffic to the Internet through the default 'Public' interface. I can't think of a way to do this from top of my head. I am just thinking of using the filters that are used to 'hairpin' the traffic, overriding the Tunnel Default Gateway.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...