Re-think historical

- * [Show and Tell](/internal/ShowAndTell)

- * [Historical services](/internal/Historical-Services)

-

-* Historical

- * [Bird 1](/historical/Bird)

- * [Quagga](/historical/Quagga)

- * [HedgeDoc](https://hedgedoc.dn42.eu)

-Bird is a commonly used BGP daemon. This page provides configuration and help to run Bird for dn42.

-Compared to quagga, bird supports multiple routing tables, which is useful, if you also plan to peer with other federated networks such as freifunk. In the following a working configuration for dn42 is shown. If you

-want to learn the practical details behind routing protocols in bird, see the following [guide](https://github.com/knorrie/network-examples)

-

-**Bird 1.6.x will be EOL by the end of 2023, it's recommended to upgrade to 2.13.**

-

-# Debian

-In the Debian release cycle the bird packages may become outdated at times, if that is the case you should use the official bird package repository maintained by the developers of nic.cz.

-

-This is not necessary for Debian Stretch, which currently ships the most recent version (1.6.3) in this repositories.

-

-```sh

-echo "deb http://deb.debian.org/debian buster-backports main" > /etc/apt/sources.list.d/buster-backports.list

-apt update

-apt install bird

-```

-

-# Example configuration

-

-Note: This file covers the configuration of Bird 1.x. For an example configuration of Bird 2.x see [howto/Bird2](/howto/Bird2)

-

-* Replace `<AS>` with your Autonomous System Number (only the digits)

-* Replace `<GATEWAY_IP>` with your gateway ip (the internal dn42 ip address you use on the host, where dn42 is running)

-* Replace `<SUBNET>` with your registered dn42 subnet

-* Replace `<PEER_IP>` with the ip of your peer who is connected with you using your favorite vpn protocol (openvpn, ipsec, tinc, ...)

-* Replace `<PEER_AS>` the Autonomous System Number of your peer (only the digits)

-* Replace `<PEER_NAME>` a self chosen name for your peer

-

-## IPv6

-

-```conf

-#/etc/bird/bird6.conf

-protocol device {

- scan time 10;

-}

-

-# local configuration

-######################

-

-include "/etc/bird/local6.conf";

-

-# filter helpers

-#################

-

-##include "/etc/bird/filter6.conf";

-

-# Kernel routing tables

-########################

-

-

-/*

- krt_prefsrc defines the source address for outgoing connections.

- On Linux, this causes the "src" attribute of a route to be set.

-

- Without this option outgoing connections would use the peering IP which

- would cause packet loss if some peering disconnects but the interface

- is still available. (The route would still exist and thus route through

- the TUN/TAP interface but the VPN daemon would simply drop the packet.)

-*/

-protocol kernel {

- scan time 20;

- import none;

- export filter {

- if source = RTS_STATIC then reject;

- krt_prefsrc = OWNIP;

- accept;

- };

-}

-

-# static routes

-################

-

-protocol static {

- route <SUBNET> reject;

- import all;

- export none;

-}

-

-template bgp dnpeers {

- local as OWNAS;

- path metric 1;

- import keep filtered;

- import filter {

- if is_valid_network() && !is_self_net() then {

- accept;

- }

- reject;

- };

- export filter {

- if is_valid_network() && source ~ [RTS_STATIC, RTS_BGP] then {

- accept;

- }

- reject;

- };

- import limit 1000 action block;

-}

-

-include "/etc/bird/peers6/*";

-```

-

-```conf

-# /etc/bird/local6.conf

-# should be a unique identifier, use same id as for ipv4

-router id <GATEWAY_IP>;

-

-define OWNAS = <AS>;

-define OWNIP = <GATEWAY_IP>;

-

-function is_self_net() {

- return net ~ [<SUBNET>+];

-}

-

-function is_valid_network() {

- return net ~ [

- fd00::/8{44,64} # ULA address space as per RFC 4193

- ];

-}

-```

-

-```conf

-# /etc/bird/peers6/<PEER_NAME>

-protocol bgp <PEER_NAME> from dnpeers {

- neighbor <PEERING_IP> as <PEER_AS>;

- # if you use link-local ipv6 addresses for peering using the following

- # neighbor <PEERING_IP> % '<INTERFACE_NAME>' as <PEER_AS>;

-};

-```

-

-### IPv4

-

-```conf

-# /etc/bird/bird.conf

-# Device status

-protocol device {

- scan time 10; # recheck every 10 seconds

-}

-

-protocol static {

- # Static routes to announce your own range(s) in dn42

- route <SUBNET> reject;

- import all;

- export none;

-};

-

-# local configuration

-######################

-

-# keeping router specific in a seperate file,

-# so this configuration can be reused on multiple routers in your network

-include "/etc/bird/local4.conf";

-

-# filter helpers

-#################

-

-##include "/etc/bird/filter4.conf";

-

-# Kernel routing tables

-########################

-

-/*

- krt_prefsrc defines the source address for outgoing connections.

- On Linux, this causes the "src" attribute of a route to be set.

-

- Without this option outgoing connections would use the peering IP which

- would cause packet loss if some peering disconnects but the interface

- is still available. (The route would still exist and thus route through

- the TUN/TAP interface but the VPN daemon would simply drop the packet.)

-*/

-protocol kernel {

- scan time 20;

- import none;

- export filter {

- if source = RTS_STATIC then reject;

- krt_prefsrc = OWNIP;

- accept;

- };

-};

-# DN42

-#######

-

-template bgp dnpeers {

- local as OWNAS;

- # metric is the number of hops between us and the peer

- path metric 1;

- # this lines allows debugging filter rules

- # filtered routes can be looked up in birdc using the "show route filtered" command

- import keep filtered;

- import filter {

- # accept every subnet, except our own advertised subnet

- # filtering is important, because some guys try to advertise routes like 0.0.0.0

- if is_valid_network() && !is_self_net() then {

- accept;

- }

- reject;

- };

- export filter {

- # here we export the whole net

- if is_valid_network() && source ~ [RTS_STATIC, RTS_BGP] then {

- accept;

- }

- reject;

- };

- import limit 1000 action block;

- #source address OWNIP;

-};

-

-include "/etc/bird/peers4/*";

-```

-

-```conf

-#/etc/bird/local4.conf

-# should be a unique identifier, <GATEWAY_IP> is what most people use.

-router id <GATEWAY_IP>;

-

-define OWNAS = <AS>;

-define OWNIP = <GATEWAY_IP>;

-

-function is_self_net() {

- return net ~ [<SUBNET>+];

-}

-

-function is_valid_network() {

- return net ~ [

- 172.20.0.0/14{21,29}, # dn42

- 172.20.0.0/24{28,32}, # dn42 Anycast

- 172.21.0.0/24{28,32}, # dn42 Anycast

- 172.22.0.0/24{28,32}, # dn42 Anycast

- 172.23.0.0/24{28,32}, # dn42 Anycast

- 172.31.0.0/16+, # ChaosVPN

- 10.100.0.0/14+, # ChaosVPN

- 10.127.0.0/16{16,32}, # neonetwork

- 10.0.0.0/8{15,24} # Freifunk.net

- ];

-}

-```

-

-```conf

-# /etc/bird/peers4/<PEER_NAME>

-protocol bgp <PEER_NAME> from dnpeers {

- neighbor <PEERING_IP> as <PEER_AS>;

-};

-```

-

-# Bird communities

-

-Communities can be used to prioritize traffic based on different flags, in DN42 we are using communities to prioritize based on latency, bandwidth and encryption. It is really easy to get started with communities and we encourage all of you to get the basic configuration done and to mark your peerings with the correct flags for improved routing.

-More information can be found [here](/howto/BGP-communities).

-

-# Route Origin Authorization

-

-Route Origin Authorizations should be used in BIRD to authenticate prefix announcements. These check the originating AS and validate that they are allowed to advertise a prefix.

-

-## ROA Tables

-

-The ROA table can be generated from the registry directly or you can use pre-built ROA tables.

-

-### Updating ROA tables

-

-You can add cron entries to periodically update the tables:

-

-```conf

-*/15 * * * * curl -sfSLR {-o,-z}/var/lib/bird/bird6_roa_dn42.conf https://dn42.burble.com/roa/dn42_roa_bird1_6.conf && chronic birdc6 configure

-*/15 * * * * curl -sfSLR {-o,-z}/var/lib/bird/bird_roa_dn42.conf https://dn42.burble.com/roa/dn42_roa_bird1_4.conf && chronic birdc configure

-```

-

-Debian version:

-

-```conf

-*/15 * * * * curl -sfSLR -o/var/lib/bird/bird6_roa_dn42.conf -z/var/lib/bird/bird6_roa_dn42.conf https://dn42.burble.com/roa/dn42_roa_bird1_6.conf && /usr/sbin/birdc6 configure

-*/15 * * * * curl -sfSLR -o/var/lib/bird/bird_roa_dn42.conf -z/var/lib/bird/bird_roa_dn42.conf https://dn42.burble.com/roa/dn42_roa_bird1_4.conf && /usr/sbin/birdc configure

-```

-

-then create the directory to make sure curls can save the files:

-

-```sh

-mkdir -p /var/lib/bird/

-```

-

-Or use a systemd timer: (check the commands before copy-pasting)

-

-```conf

-# /etc/systemd/system/dn42-roa.service

-[Unit]

-Description=Update DN42 ROA

-

-[Service]

-Type=oneshot

-ExecStart=curl -sfSLR -o /etc/bird/roa_dn42.conf -z /etc/bird/roa_dn42.conf https://dn42.burble.com/roa/dn42_roa_bird2_4.conf

-ExecStart=curl -sfSLR -o /etc/bird/roa_dn42_v6.conf -z /etc/bird/roa_dn42_v6.conf https://dn42.burble.com/roa/dn42_roa_bird2_6.conf

-ExecStart=birdc configure

-```

-

-```conf

-# /etc/systemd/system/dn42-roa.timer

-[Unit]

-Description=Update DN42 ROA periodically

-

-[Timer]

-OnBootSec=2m

-OnUnitActiveSec=15m

-AccuracySec=1m

-

-[Install]

-WantedBy=timers.target

-```

-

-then enable and start the timer with `systemctl enable --now dn42-roa.timer`.

-

-More advanced script with error checking:

-```sh

-#!/bin/bash

-roa4URL=""

-roa6URL=""

-

-roa4FILE="/etc/bird/roa/roa_dn42.conf"

-roa6FILE="/etc/bird/roa/roa_dn42_v6.conf"

-

-cp "${roa4FILE}" "${roa4FILE}.old"

-cp "${roa6FILE}" "${roa6FILE}.old"

-

-if curl -f -o "${roa4FILE}.new" "${roa4URL};" ;then

- mv "${roa4FILE}.new" "${roa4FILE}"

-fi

-

-if curl -f -o "${roa6FILE}.new" "${roa6URL};" ;then

- mv "${roa6FILE}.new" "${roa6FILE}"

-fi

-

-if birdc configure ; then

- rm "${roa4FILE}.old"

- rm "${roa6FILE}.old"

-else

- mv "${roa4FILE}.old" "${roa4FILE}"

- mv "${roa6FILE}.old" "${roa6FILE}"

-fi

-```

-

-

-### Use RPKI ROA in bird2

-

-* Download gortr

-

-<https://github.com/cloudflare/gortr/releases>

-

-* Run gortr.

-

-```sh

-./gortr -verify=false -checktime=false -cache=https://dn42.burble.com/roa/dn42_roa_46.json

-```

-

-

-* Run with docker

-

-```sh

-docker pull cloudflare/gortr

-```

-

-```sh

-docker run --name dn42rpki -p 8282:8282 --restart=always -d cloudflare/gortr -verify=false -checktime=false -cache=https://dn42.burble.com/roa/dn42_roa_46.json

-```

-

-* Add this to your bird configure file,other ROA protocol must removed.

-

-```conf

-protocol rpki rpki_dn42{

- roa4 { table dn42_roa; };

- roa6 { table dn42_roa_v6; };

-

- remote "<your rpki server ip or domain>" port 8282;

-

- retry keep 90;

- refresh keep 900;

- expire keep 172800;

-}

-```

-

-## Filter configuration

-

-In your import filter add the following to reject invalid routes:

-

-```conf

-if (roa_check(dn42_roa, net, bgp_path.last) != ROA_VALID) then {

- print "[dn42] ROA check failed for ", net, " ASN ", bgp_path.last;

- reject;

-}

-```

-

-Also, define your ROA table with:

-

-```conf

-roa table dn42_roa {

- include "/var/lib/bird/bird_roa_dn42.conf";

-};

-```

-

-

-**NOTE**: Make sure you setup ROA checks for both bird and bird6 (for IPv6).

-

-# Useful bird commmands

-

-bird can be remote controlled via the `birdc` command. Here is a list of useful bird commands:

-

-```sh

-$ birdc

-BIRD 1.4.5 ready.

-bird> configure # reload configuration

-Reading configuration from /etc/bird.conf

-Reconfigured

-bird> show ? # Completions work either by pressing tab or pressing '?'

-show bfd ... Show information about BFD protocol

-show interfaces Show network interfaces

-show memory Show memory usage

-show ospf ... Show information about OSPF protocol

-show protocols [<protocol> | "<pattern>"] Show routing protocols

-show roa ... Show ROA table

-show route ... Show routing table

-show static [<name>] Show details of static protocol

-show status Show router status

-show symbols ... Show all known symbolic names

-bird> show protocols # this command shows your peering status

-name proto table state since info

-device1 Device master up 07:20:25

-kernel1 Kernel master up 07:20:25

-chelnok BGP master up 07:20:29 Established

-hax404 BGP master up 07:20:26 Established

-static1 Static master up 07:20:25

-bird> show protocols all chelnok # show verbose peering status for peering with chelnok

-bird> show route for 172.22.141.181 # show possible routes to internal.dn42

-172.22.141.0/24 via 172.23.67.1 on tobee [tobee 07:20:30] * (100) [AS64737i]

- via 172.23.64.1 on chelnok [chelnok 07:20:29] (100) [AS64737i]

- via 172.23.136.65 on hax404 [hax404 07:20:26] (100) [AS64737i]

-bird> show route filtered # shows routed filtered out by rules

-172.23.245.1/32 via 172.23.64.1 on chelnok [chelnok 21:26:18] * (100) [AS76175i]

-172.22.247.128/32 via 172.23.64.1 on chelnok [chelnok 21:26:18] * (100) [AS76175i]

-172.22.227.1/32 via 172.23.64.1 on chelnok [chelnok 21:26:18] * (100) [AS76115i]

-172.23.196.75/32 via 172.23.64.1 on chelnok [chelnok 21:26:18] * (100) [AS76115i]

-172.22.41.241/32 via 172.23.64.1 on chelnok [chelnok 21:26:18] * (100) [AS76115i]

-172.22.249.4/30 via 172.23.64.1 on chelnok [chelnok 21:26:18] * (100) [AS4242420002i]

-172.22.255.133/32 via 172.23.64.1 on chelnok [chelnok 21:26:18] * (100) [AS64654i]

-bird> show route protocol <somepeer> # shows the route they export to you

-bird> show route export <somepeer> # shows the route you export to someone

-...

-```

-

-# External Links

-* detailed bird configuration from Mic92: <https://github.com/Mic92/bird-dn42>

-* more bird commands: <https://bird.network.cz/?get_doc&v=20&f=bird-4.html>

-# Quagga

-

-Quagga is probably one of the oldest software router around. It still works, of course, even though it has an unattractive configuration syntax (unfortunately inspired by [Cisco's IOS](/howto/IPsecWithPublicKeys/CiscoIOSExample)) and has some small issues with IPv6. But since it's so old, you will find a lot of configuration examples around.

-

-## Source address selection

-

-Use this in your `zebra.conf`:

-

-```conf

-route-map RM_SET_SRC permit 10

- set src 172.22.XX.XX

-ip protocol bgp route-map RM_SET_SRC

-```

-

-Unfortunately, this is not possible with IPv6...

-

-## Important bgp commands

-To connect to bgpd use:

-

-```sh

-$ vtysh

-```

-

-Which provides an interactive interface.

-In this interface '?' can be used to list the available commands or subcommands.

-

-## Configure Quagga

-a minimal config would look like this:

-

-```sh

-vtysh> configure terminal

-vtysh(config)> router bgp <your-asn>

-vtysh(config-router)> neighbor <neighbor-ip> remote-as <neighbor-asn>

-vtysh(config-router)> neighbor <neighbor-ip> interface <interface>

-vtysh(config-router)> exit

-vtysh(config)> exit

-```

-

-### IPv6

-for IPv6 do something like

-

-```sh

-vtysh> configure terminal

-vtysh(config)> router bgp <your-asn>

-vtysh(config-router)> neighbor <neighbor-ip> remote-as <neighbor-asn>

-vtysh(config-router)> neighbor <neighbor-ip> interface <interface>

-vtysh(config-router)> no neighbor <neighbor-ip> activate

-vtysh(config-router)> address-family ipv6

-vtysh(config-router-af)> neighbor <neighbor-ip> activate

-vtysh(config-router-af)> exit

-vtysh(config-router)> exit

-vtysh(config)> exit

-```

-

-### peer groups, prefix lists and such

-If you want to use 'prefix-list' to filter some of the prefixes quagga is receiving, you can use a 'peer-group' instead of apply the prefix list to every neighbor.

-

-Define a peer group:

-

-```sh

-vtysh(config-router)> neighbor <peer-group-name> peer-group

-```

-

-Apply to a neighbor:

-

-```sh

-vtysh(config-router)> neighbor <neighbor-ip> peer-group <name>

-```

-

-Apply a prefix list for incoming prefixes to your peer group:

-

-```sh

-vtysh(config-router)> neighbor <peer-group-name> prefix-list <prefix-list-name> in

-```

-

-#### Example filter list

-

-```sh

-ip prefix-list vpn-in description BGP IPv4 import filter

-!old network:

-ip prefix-list vpn-in seq 5 permit 172.22.0.0/15 ge 22 le 28

-!new dn42 allocation:

-ip prefix-list vpn-in seq 10 permit 172.20.0.0/16 ge 22 le 28

-

-! Anycast /32s for Whois and DNS:

-ip prefix-list vpn-in seq 11 permit 172.22.0.43/32

-ip prefix-list vpn-in seq 12 permit 172.22.0.53/32

-

-ip prefix-list vpn-in seq 18 permit 192.175.48.0/24

-ip prefix-list vpn-in seq 20 deny 10.10.10.0/24

-ip prefix-list vpn-in seq 21 permit 10.0.0.0/8

-ip prefix-list vpn-in seq 30 permit 172.31.0.0/16

-ip prefix-list vpn-in seq 39 permit 100.64.0.0/10

-ip prefix-list vpn-in seq 40 permit 195.160.168.0/23

-ip prefix-list vpn-in seq 41 permit 91.204.4.0/22

-ip prefix-list vpn-in seq 43 permit 193.43.220.0/23

-ip prefix-list vpn-in seq 46 permit 83.133.178.0/23

-ip prefix-list vpn-in seq 47 permit 87.106.29.254/32

-ip prefix-list vpn-in seq 50 permit 85.25.246.16/28

-ip prefix-list vpn-in seq 51 permit 46.4.248.192/27

-ip prefix-list vpn-in seq 60 permit 94.45.224.0/19

-ip prefix-list vpn-in seq 70 permit 195.191.196.0/23

-ip prefix-list vpn-in seq 80 permit 80.244.241.224/27

-ip prefix-list vpn-in seq 90 permit 46.19.90.48/28

-ip prefix-list vpn-in seq 91 permit 46.19.90.96/28

-ip prefix-list vpn-in seq 110 permit 188.40.34.241/32

-ip prefix-list vpn-in seq 130 permit 37.1.89.192/26

-ip prefix-list vpn-in seq 140 permit 178.33.32.123/32

-ip prefix-list vpn-in seq 150 permit 87.98.246.19/32

-ip prefix-list vpn-in seq 1000 deny 0.0.0.0/0

-

-ipv6 prefix-list vpn-in seq 10 permit fd00::/8 ge 9

-ipv6 prefix-list vpn-in seq 15 deny any

-```

-

-#### Example filter list script

-```sh

-#!/bin/bash

-

-vtysh -c 'conf t' -c "no ip prefix-list dn42"; #drop old prefix list

-

-while read pl

-do

- vtysh -c 'conf t' -c "$pl"; #insert prefix list row by row

-done < <(curl -s https://ca.dn42.us/reg/filter.txt | grep -e ^[0-9] | awk '{ print "ip prefix-list dn42 seq " $1 " " $2 " " $3 " ge " $4 " le " $5}' | sed "s_/\([0-9]\+\) ge \1_/\1_g;s_/\([0-9]\+\) le \1_/\1_g");

-vtysh -c "wr" #write new prefix list

-

-```

-

-## show bpg session status

-

-in this example:

-* an active bgp session exists with peer 64713.

-* no (vpn) connection at all exists with peer 64692

-* a (vpn) connection with 4242421375 exists, but no bgp session

-

-```

-vtysh> show ip bgp summary

-BGP router identifier 172.22.100.254, local AS number 64698

-RIB entries 938, using 103 KiB of memory

-Peers 11, using 49 KiB of memory

-Peer groups 1, using 32 bytes of memory

-

-Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

-172.22.92.247 4 64692 0 0 0 0 0 never Connect

-...

-172.22.113.2 4 64713 2206 865 0 0 0 01:23:11 322

-....

-172.23.64.1 4 4242421375 0 0 0 0 0 never Active

-fe80::deca:fbad 4 64699 902 694 0 0 0 01:23:57 486

-```

-You are asked to show some creativity in terms of network usage and content ([ideas](/internal/Ideas)).