Cisco 3005 losing connectivity when LAN2LAN tunnel has been up for a while
I have a Cisco 3005 concentrator running software version 3.6.7 (cannot be upgraded for several reasons).
The private interface has an IP address of 10.101.0.242/20.
I have a lot of VPN clients and 6 3002 hardware clients, that connects and it's working fine.
I have to do business with another company and therefore creating a lan2lan tunnel to a 3005 in the other end. The private interface has IP address 10.3.1.1/24
The tunnel is working fine and I can ping and reach the servers on the other side. Suddenly after 2-4 hours of operation, my VPN clients cannot reach my own network. The only thing they can see is the 10.3.1.0 network on the other side.
What is wrong? Why is all traffic suddenly routet to the remote network?
Re: Cisco 3005 losing connectivity when LAN2LAN tunnel has been
Is it possible that the connection to the remote VPN clients is timing out due to inactivity. You can configure DPD on the client. It is my understanding that VPN SW client will continue to send DPD packets whether there is traffic or not. You should then see the client up even after an extended period of time.
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...