Distribute VPN client route in DMVPN - EIGRP

[mickd08]

Hello,

I want to advertise a VPN client route to DMVPN spoke sites.

VPN clients connect to the DMVPN hub which has EIGRP setup as follows;

router eigrp 10
maximum-paths 1
network 10.1.1.1 0.0.0.0 (tunnel1)
network 10.2.1.1 0.0.0.0 (tunnel2)
network 192.168.1.0 (local lan)
network 192.168.10.0 (vpn client pool)

network 1.1.1.1 0.0.0.0 (loopback)

In this configuration, the 192.168.10 route does not get advertised via EIGRP.

When a VPN client connects, it can route to all the DMVPN hub interfaces but not to the spokes.

If I add the "redistribute static" command, the route is then advertised as an external route to all the spokes and all works as desired.

Is there any potential issues with advertising the route in this manner?

Cheers 

[Georg Pauwen · Accepted solution]

Hello,

as far as I recall, this is by design. The DMVPN hub creates static host routes for your VPN clients, however there is no real interface with an IP address from your VPN client pool (192.168.10.0/24 in your case) existing on your hub, so EIGRP cannot advertise any interface from this range...

[mickd08]

Thanks for your reply.

For anyone else who comes across this, I used a "redistribute static" with "route map" in the final config in order to suppress the default route from being redistributed from the DMVPN hub - this was causing a "looped chain attempting to stack" error between the two DMVPN tunnels.

router eigrp 10
maximum-paths 1
network 10.1.1.1 0.0.0.0 (tunnel1)
network 10.2.1.1 0.0.0.0 (tunnel2)
network 192.168.1.0 (local lan)
network 1.1.1.1 0.0.0.0 (loopback)

redistribute static metric 100 10000 255 1 1500 route-map DISTRIBUTED-EXTERNAL-ROUTE
!
!
ip prefix-list DISTRIBUTED-EXTERNAL-ROUTES-LIST seq 10 permit 192.168.10.0/24 ge 32

route-map DISTRIBUTED-EXTERNAL-ROUTE permit 10
match ip address prefix-list DISTRIBUTED-EXTERNAL-ROUTES-LIST
route-map DISTRIBUTED-EXTERNAL-ROUTE deny 100