Assigning DMVPN tunnel interface addresses with DHCP
I posted previously about some of the inner workings of DHCP. The three key points from that post are critical building blocks for this discussion:- DHCP requests get modified in flight by the DHCP relay.
- DHCP relay determines L2 destination by inspecting contents of relayed packets.
- DHCP clients, relays and (sometimes) servers use raw sockets because the end-to-end protocol stack isn't yet available.
- Configure a DHCP server. I'm using an external server1 in this example so that we can inspect the relayed packets while they're on the wire.
- Configure the hub router. There are some non-intuitive details we'll go over.
- Configure the spoke router. Ditto on the non-intuitive bits.
1 no ip dhcp conflict logging
2 ip dhcp excluded-address 172.16.1.1
3 !
4 ip dhcp pool DMVPN_POOL
5 network 172.16.1.0 255.255.255.0
So, that's pretty straightforward.
The Hub Router has the following relevant configuration:
1 ip dhcp support tunnel unicast
2 interface Tunnel0
3 Continue reading