I have a new DMVPN network with 1 hub (2801) and 2 spokes (871s). I am using EIGRP over the DMVPN.
One of the spokes is the Easy VPN server for users to login remotely with the Cisco VPN client. When a user VPNs in, they can access the local networks on the 871 they've logged into.
The problem I am having is the user's IP address is not being announced with EIGRP, so none of the other routers know the route to the VPN client. When I add the VPN addresses as a static route with the VPN server as the next hop, the user can access all networks connected to the DMVPN. All other EIGRP announced networks are working correctly.
Is there any special configuration needed to have the VPN client IP addresses announced via EIGRP, or is this not even possible?
Here's the show ip route entry for the VPN user on the VPN server router:
192.168.6.0/32 is subnetted, 1 subnets
S 192.168.6.1 [1/0] via x.x.x.x
Here's the EIGRP config on the VPN server:
router eigrp 1
network 192.168.4.0 0.0.0.15
network 192.168.6.0 0.0.0.0
network 192.168.6.1 0.0.0.0
network 192.168.6.2 0.0.0.0
network 192.168.6.3 0.0.0.0
network 192.168.6.4 0.0.0.0
network 192.168.6.5 0.0.0.0
Also, here's the pool used for VPN clients:
ip local pool SDM_POOL_1 192.168.6.1 192.168.6.5
Let me know if there's any other information that would help.
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...