One interface, many peers
mGRE lets a router use one tunnel interface for many remote routers.
Build a clear mental model of Dynamic Multipoint VPN, then practice GRE, mGRE, NHRP, IPsec, all three DMVPN phases, direct spoke paths, and evidence-led verification.
Dynamic Multipoint Virtual Private Network (DMVPN) is a Cisco WAN design. It normally uses one or more central routers called hubs and many branch routers called spokes.
Every spoke first connects to the hub. Depending on the DMVPN phase, two spokes may also create a direct tunnel when they need to exchange traffic. This saves hub bandwidth and can reduce delay between branches.
mGRE lets a router use one tunnel interface for many remote routers.
NHRP tells routers which public or transport address belongs to a tunnel address.
EIGRP, OSPF, BGP or static routes carry branch network information across the tunnel.
IPsec protects the tunnel when traffic crosses an untrusted network such as the Internet.
You will understand this guide more easily if you already know the basics of IP routing, VPN tunnels, GRE and hub-and-spoke networks. The GRE foundation lab is a good starting point if GRE is new to you.
With normal point-to-point GRE, every tunnel has one source and one destination. A few sites are easy to manage, but a large network needs many tunnel interfaces and many repeated peer settings. A full mesh becomes harder to build each time a new branch is added.
DMVPN removes much of that manual work. The hub can accept new spokes dynamically, and the spokes can learn how to reach one another only when traffic needs a direct path.
| Part | What it does | Simple way to remember it |
|---|---|---|
| mGRE | Lets one tunnel interface send GRE packets to many remote routers. | The shared tunnel |
| NHRP | Maps a private tunnel IP address to the router's transport address. | The address book |
| Routing | Advertises which LAN networks are behind each router. | The path chooser |
| IPsec | Encrypts and authenticates traffic across an untrusted network. | The security layer |
The underlay is the real transport network. It must be able to carry packets between the routers' Internet-facing or WAN addresses. The overlay is the private tunnel network built on top of it.
The real address used to deliver the packet across the WAN. DMVPN calls this the NBMA address.
The private address on the DMVPN tunnel interface. Routing neighbors use this network.
mGRE can send packets to many places, but it still needs the correct transport destination. NHRP provides that information.
NBMA means the address used to reach a router through the transport network. On an Internet DMVPN, it is often the router's public IP address. NHRP maps the private tunnel address to this transport address.
| Phase | Traffic path | Routing rule | Main trade-off |
|---|---|---|---|
| Phase 1 | Spoke-to-spoke traffic always goes through the hub. | A summary or default route toward the hub is enough. | Simple, but the hub carries all branch traffic. |
| Phase 2 | Spokes can build a direct tunnel after NHRP resolution. | The route must keep the remote spoke as the next hop. | Direct paths work, but hub route summarization is limited. |
| Phase 3 | The first packets may cross the hub; later packets use a direct shortcut. | The hub can advertise summaries or a default route. | More scalable, but redirect and shortcut behavior must be understood. |
The hub uses mGRE. Spokes normally use point-to-point GRE and cannot create direct spoke tunnels.
All routers use mGRE. The routing table must point to the remote spoke before a direct tunnel can form.
The hub tells a spoke when a better direct path exists. The spokes then resolve each other through NHRP.
The phase changes how traffic moves and how much routing detail the spokes need. Use the design requirements—not only the phase number—to make the choice.
DMVPN can work with EIGRP, OSPF, BGP, RIP or static routes. The important detail is the route's next-hop address. Phase 2 needs the remote spoke to remain the next hop. Phase 3 can use the hub as the routing next hop and then create a forwarding shortcut.
GRE and NHRP do not encrypt data. If the underlay is the public Internet, use an IPsec tunnel-protection profile to provide confidentiality, integrity and peer authentication.
| Term | Meaning |
|---|---|
| Hub | The central router that spokes register with and normally use to exchange routes. |
| Spoke | A branch router that connects to the hub and may create direct tunnels to other spokes. |
| NHS | Next Hop Server—the NHRP role normally performed by the hub. |
| NBMA address | The router's address on the transport network, often its public Internet address. |
| Tunnel address | The router's private IP address inside the DMVPN overlay. |
| NHRP redirect | A Phase 3 message from the hub telling a spoke that a better direct path exists. |
| NHRP shortcut | The direct spoke-to-spoke forwarding entry created after NHRP resolution. |
mGRE has no fixed destination for every peer. NHRP maps a tunnel address to the peer's transport address so the router knows where to send the GRE packet.
No. GRE carries the packets and supports routing traffic, but IPsec supplies encryption, integrity checking and peer authentication.
Phase 2 and Phase 3 support direct spoke-to-spoke tunnels. Phase 1 always sends spoke-to-spoke traffic through the hub.
The hub can advertise a summary or default route while NHRP redirects active traffic to a direct spoke-to-spoke shortcut. Phase 2 normally needs more specific routes.
Yes. A spoke can register its current transport address with the hub. The hub address should remain stable so every spoke can find the NHRP server.