Hi. Currently we are testing a GET VPN solution between 6-10 branch offices connected by a private WAN using Metro Ethernet circuits.
One of the key servers is located within the Metro Ethernet as well..... The VPN topology is an any to any connectivity... using the crypto map on the outgoing interfaces on the branch routers towards the Metro IP WAN works as expected and traffic gets encrypted but there are sites that has redundant links using Wireless Radios (nearby offices) were we also like to have GET VPN working using the same key server.
The problem is that when traffic is transiting through this wireless links even though we have the crypto map it is not encrypting the data. The encryption domain remains the same.. the only difference is that instead of using the Metro IP WAN is using a different path (Wireless Link) connected to another FastEthernet port on the same IP WAN router. If we switch the traffic to the IP WAN then the encryption start working as expected.
Any ideas? Are redundant links supported on the GET VPN? I add all the outgoing interfaces on the IP WAN routers to the key server as "crypto isakmp key ... address x.y.z.w" but problem remains.
In the MAC/Encaps MAC indicates the Length in bytes of Layer 2 header and Encaps indicates length in bytes of packet encapsulation, including Layer 2 header and label header. Maximum transmission unit (MTU) of labeled packet.
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...