I have a bit of a dilemma. We have an ASA 5510 which we currently have some L2L and remote access VPN connections on.We brought in a higher speed line to terminate our VPN on and I need start moving VPN connections to the new interface. I overlooked one issue the default route, it won't follow the same interface it connects to back out. Can I have 2 default routes so that is sends out both interfaces? I know this is a stretch, but I am hoping someone has a solution for this.
I did that with a test connection and it did work. The L2L connections are the easy ones, it is the client based ones that are going to be an issue as there are a lot of them and trying to do a static route individually will be an monstrous task.
Anyone know much about policy based routing? Can I setup a routing policy that allows routing back out the originating interface? That would make life much easier.
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...