7 *nhrpd* is an implementation of the :abbr:`NHRP (Next Hop Routing Protocol)`.
8 NHRP is described in :rfc:`2332`.
10 NHRP is used to improve the efficiency of routing computer network traffic over
11 :abbr:`NBMA (Non-Broadcast, Multiple Access)` networks. NHRP provides an
12 ARP-like solution that allows a system to dynamically learn the NBMA address of
13 the other systems that are part of that network, allowing these systems to
14 directly communicate without requiring traffic to use an intermediate hop.
16 NHRP is a client-server protocol. The server side is called the :abbr:`NHS
17 (Next Hop Server)` or the hub, while a client is referred to as the :abbr:`NHC
18 (Next Hop Client)` or the spoke. When a node is configured as an NHC, it
19 registers its address with the NHS which keeps track of all registered spokes.
20 An NHC client can then query the addresses of other clients from NHS allowing
21 all spokes to communicate directly with each other.
23 Cisco Dynamic Multipoint VPN (DMVPN) is based on NHRP, and |PACKAGE_NAME| nhrpd
24 implements this scenario.
31 nhrpd never handles routing of prefixes itself. You need to run some
32 real routing protocol (e.g. BGP) to advertise routes over the tunnels.
33 What nhrpd does it establishes 'shortcut routes' that optimizes the
34 routing protocol to avoid going through extra nodes in NBMA GRE mesh.
36 nhrpd does route NHRP domain addresses individually using per-host prefixes.
37 This is similar to Cisco FlexVPN; but in contrast to opennhrp which uses
38 a generic subnet route.
40 To create NBMA GRE tunnel you might use the following (Linux terminal
43 .. code-block:: console
45 ip tunnel add gre1 mode gre key 42 ttl 64
46 ip addr add 10.255.255.2/32 dev gre1
50 Note that the IP-address is assigned as host prefix to gre1. nhrpd will
51 automatically create additional host routes pointing to gre1 when
52 a connection with these hosts is established.
54 The gre1 subnet prefix should be announced by routing protocol from the
55 hub nodes (e.g. BGP 'network' announce). This allows the routing protocol
56 to decide which is the closest hub and determine the relay hub on prefix
57 basis when direct tunnel is not established.
59 nhrpd will redistribute directly connected neighbors to zebra. Within
60 hub nodes, these routes should be internally redistributed using some
61 routing protocol (e.g. iBGP) to allow hubs to be able to relay all traffic.
63 This can be achieved in hubs with the following bgp configuration (network
64 command defines the GRE subnet):
69 address-family ipv4 unicast
80 .. index:: ip nhrp holdtime (1-65000)
81 .. clicmd:: ip nhrp holdtime (1-65000)
83 Holdtime is the number of seconds that have to pass before stopping to
84 advertise an NHRP NBMA address as valid. It also controls how often NHRP
85 registration requests are sent. By default registrations are sent every one
86 third of the holdtime.
88 .. index:: ip nhrp map A.B.C.D|X:X::X:X A.B.C.D|local
89 .. clicmd:: ip nhrp map A.B.C.D|X:X::X:X A.B.C.D|local
91 Map an IP address of a station to the station's NBMA address.
93 .. index:: ip nhrp network-id (1-4294967295)
94 .. clicmd:: ip nhrp network-id (1-4294967295)
96 Enable NHRP on this interface and set the interface's network ID. The
97 network ID is used to allow creating multiple nhrp domains on a router when
98 multiple interfaces are configured on the router. Interfaces configured
99 with the same ID are part of the same logical NBMA network. The ID is a
100 local only parameter and is not sent to other NHRP nodes and so IDs on
101 different nodes do not need to match. When NHRP packets are received on an
102 interface they are assigned to the local NHRP domain for that interface.
104 .. index:: ip nhrp nhs A.B.C.D nbma A.B.C.D|FQDN
105 .. clicmd:: ip nhrp nhs A.B.C.D nbma A.B.C.D|FQDN
107 Configure the Next Hop Server address and its NBMA address.
109 .. index:: ip nhrp nhs dynamic nbma A.B.C.D
110 .. clicmd:: ip nhrp nhs dynamic nbma A.B.C.D
112 Configure the Next Hop Server to have a dynamic address and set its NBMA
115 .. index:: ip nhrp registration no-unique
116 .. clicmd:: ip nhrp registration no-unique
118 Allow the client to not set the unique flag in the NHRP packets. This is
119 useful when a station has a dynamic IP address that could change over time.
121 .. index:: ip nhrp shortcut
122 .. clicmd:: ip nhrp shortcut
124 Enable shortcut (spoke-to-spoke) tunnels to allow NHC to talk to each others
125 directly after establishing a connection without going through the hub.
127 .. index:: ip nhrp mtu
128 .. clicmd:: ip nhrp mtu
130 Configure NHRP advertised MTU.
133 .. _hub-functionality:
138 In addition to routing nhrp redistributed host prefixes, the hub nodes
139 are also responsible to send NHRP Traffic Indication messages that
140 trigger creation of the shortcut tunnels.
142 nhrpd sends Traffic Indication messages based on network traffic captured
143 using NFLOG. Typically you want to send Traffic Indications for network
144 traffic that is routed from gre1 back to gre1 in rate limited manner.
145 This can be achieved with the following iptables rule.
147 .. code-block:: shell
149 iptables -A FORWARD -i gre1 -o gre1 \\
150 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 \\
151 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 \\
152 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-range 128
155 You can fine tune the src/dstmask according to the prefix lengths you announce
156 internal, add additional IP range matches, or rate limitation if needed.
157 However, the above should be good in most cases.
159 This kernel NFLOG target's nflog-group is configured in global nhrp config
162 .. index:: nhrp nflog-group (1-65535)
163 .. clicmd:: nhrp nflog-group (1-65535)
165 To start sending these traffic notices out from hubs, use the nhrp
166 per-interface directive:
168 .. index:: ip nhrp redirect
169 .. clicmd:: ip nhrp redirect
171 This enable redirect replies on the NHS similar to ICMP redirects except this
172 is managed by the nhrp protocol. This setting allows spokes to communicate with
173 each others directly.
175 .. _integration-with-ike:
180 nhrpd needs tight integration with IKE daemon for various reasons.
181 Currently only strongSwan is supported as IKE daemon.
183 nhrpd connects to strongSwan using VICI protocol based on UNIX socket
184 (hardcoded now as /var/run/charon.vici).
186 strongSwan currently needs few patches applied. Please check out the
187 https://git.alpinelinux.org/user/tteras/strongswan/log/?h=tteras-release
189 https://git.alpinelinux.org/user/tteras/strongswan/log/?h=tteras
190 git repositories for the patches.
197 .. index:: nhrp event socket SOCKET
198 .. clicmd:: nhrp event socket SOCKET
200 Configure the Unix path for the event socket.
207 .. index:: show [ip|ipv6] nhrp cache [json]
208 .. clicmd:: show [ip|ipv6] nhrp cache [json]
210 Dump the cache entries.
212 .. index:: show [ip|ipv6] nhrp opennhrp [json]
213 .. clicmd:: show [ip|ipv6] nhrp opennhrp [json]
215 Dump the cache entries with opennhrp format.
217 .. index:: show [ip|ipv6] nhrp nhs [json]
218 .. clicmd:: show [ip|ipv6] nhrp nhs [json]
220 Dump the hub context.
222 .. index:: show dmvpn [json]
223 .. clicmd:: show dmvpn [json]
225 Dump the security contexts.
227 Configuration Example
228 =====================
230 .. figure:: ../figures/fig_dmvpn_topologies.png
235 IPSec configurration example
236 ----------------------------
238 This changes required on all nodes as HUB and Spokes.
242 .. code-block:: shell
249 ike=aes256-aes256-sha256-modp2048
250 esp=aes256-aes256-sha256-modp2048
264 .. code-block:: shell
266 %any : PSK "some_s3cret!"
269 HUB configuration example
270 -------------------------
272 Creating gre interface
274 .. code-block:: console
276 ip tunnel add gre1 mode gre key 42 ttl 64
277 ip addr add 10.0.0.254/32 dev gre1
280 Adding iptables rules to provide possibility shortcut tunnels and connect spokes directly
282 .. code-block:: shell
284 iptables -A FORWARD -i gre1 -o gre1 \\
285 -m hashlimit --hashlimit-upto 4/minute --hashlimit-burst 1 \\
286 --hashlimit-mode srcip,dstip --hashlimit-srcmask 24 --hashlimit-dstmask 24 \\
287 --hashlimit-name loglimit-0 -j NFLOG --nflog-group 1 --nflog-range 128
296 description DMVPN Tunnel Interface
297 ip address 10.0.0.254/32
300 ip nhrp registration no-unique
302 tunnel protection vici profile dmvpn
306 bgp router-id 10.0.0.254
307 no bgp ebgp-requires-policy
308 neighbor SPOKES peer-group
309 neighbor SPOKES disable-connected-check
310 neighbor 10.0.0.1 remote-as 65001
311 neighbor 10.0.0.1 peer-group SPOKES
312 neighbor 10.0.0.2 remote-as 65002
313 neighbor 10.0.0.2 peer-group SPOKES
314 neighbor 10.0.0.3 remote-as 65003
315 neighbor 10.0.0.3 peer-group SPOKES
317 address-family ipv4 unicast
318 network 172.16.0.0/24
325 Creating gre interface
327 .. code-block:: console
329 ip tunnel add gre1 mode gre key 42 ttl 64
330 ip addr add 10.0.0.1/32 dev gre1
339 description DMVPN Tunnel Interface
340 ip address 10.0.0.1/32
342 ip nhrp nhs dynamic nbma 198.51.100.1
344 ip nhrp registration no-unique
347 tunnel protection vici profile dmvpn
351 no bgp ebgp-requires-policy
352 neighbor 10.0.0.254 remote-as 65000
353 neighbor 10.0.0.254 disable-connected-check
355 address-family ipv4 unicast
356 network 172.16.1.0/24
363 Creating gre interface
365 .. code-block:: console
367 ip tunnel add gre1 mode gre key 42 ttl 64
368 ip addr add 10.0.0.1/32 dev gre1
376 description DMVPN Tunnel Interface
377 ip address 10.0.0.2/32
379 ip nhrp nhs dynamic nbma 198.51.100.1
381 ip nhrp registration no-unique
384 tunnel protection vici profile dmvpn
388 no bgp ebgp-requires-policy
389 neighbor 10.0.0.254 remote-as 65000
390 neighbor 10.0.0.254 disable-connected-check
392 address-family ipv4 unicast
393 network 172.16.2.0/24
400 Creating gre interface
402 .. code-block:: console
404 ip tunnel add gre1 mode gre key 42 ttl 64
405 ip addr add 10.0.0.3/32 dev gre1
413 description DMVPN Tunnel Interface
414 ip address 10.0.0.3/32
416 ip nhrp nhs dynamic nbma 198.51.100.1
418 ip nhrp registration no-unique
421 tunnel protection vici profile dmvpn
425 no bgp ebgp-requires-policy
426 neighbor 10.0.0.254 remote-as 65000
427 neighbor 10.0.0.254 disable-connected-check
429 address-family ipv4 unicast
430 network 172.16.3.0/24