☰

Added a "getting routes installed to the kernel automatically" section to bird2.md. I got stuck at this stage when I was first setting up DN42 as I didnt know I had to do it.

Anonymous committed 2025-01-26 19:05:12 +0000 commit d646054085cde1a59c34086fd203bd6881e842fd

				howto/Bird2.md
			
          @@ -205,6 +205,27 @@ protocol bgp <NEIGHBOR_NAME>_v6 from dnpeers {

           Due to the special link local addresses of IPv6, an interface has to be specified using the `%<if>` or the `interface <if>;` syntax if a link local address is used (Which is recommended)

          +# Getting routes installed to the kernal automatically

          +

          +If you do not do this, your bird logs *will* be full of `Netlink: Invalid argument` errors and you will not be able to access the DN42 network.

          +

          +You will need to create a loopback dummy interface with your DN42 router IP, for both IPv4 and IPv6

          +

          +Create the dummy interface with these commands:

          +

          +```

          +ip link add dn42-dummy type dummy

          +ip link set dev dn42-dummy up

          +```

          +

          +Then, give it your router IP addresses:

          +

          +```

          +ip addr add dev dn42-dummy <router ip>/<subnet>

          +```

          +

          +Do this for both IPv4 and IPv6.

          +

           ## Note on multiprotocol BGP and extended next hops

           This configuration example shows the required configuration without using multiprotocol BGP and extended next hops.

           These two options are helpful if one desires to optimize their peering by reducing the session count per peer to 1 (in the case of multiprotocol BGP) and remove the need to have IPv4 tunnel IP addresses (in the case of Extended next hops over IPv6)

...	...	@@ -205,6 +205,27 @@ protocol bgp <NEIGHBOR_NAME>_v6 from dnpeers {
205	205
206	206	Due to the special link local addresses of IPv6, an interface has to be specified using the `%<if>` or the `interface <if>;` syntax if a link local address is used (Which is recommended)
207	207
	208	+# Getting routes installed to the kernal automatically
	209	+
	210	+If you do not do this, your bird logs will be full of `Netlink: Invalid argument` errors and you will not be able to access the DN42 network.
	211	+
	212	+You will need to create a loopback dummy interface with your DN42 router IP, for both IPv4 and IPv6
	213	+
	214	+Create the dummy interface with these commands:
	215	+
	216	+```
	217	+ip link add dn42-dummy type dummy
	218	+ip link set dev dn42-dummy up
	219	+```
	220	+
	221	+Then, give it your router IP addresses:
	222	+
	223	+```
	224	+ip addr add dev dn42-dummy <router ip>/<subnet>
	225	+```
	226	+
	227	+Do this for both IPv4 and IPv6.
	228	+
208	229	## Note on multiprotocol BGP and extended next hops
209	230	This configuration example shows the required configuration without using multiprotocol BGP and extended next hops.
210	231	These two options are helpful if one desires to optimize their peering by reducing the session count per peer to 1 (in the case of multiprotocol BGP) and remove the need to have IPv4 tunnel IP addresses (in the case of Extended next hops over IPv6)