This page explains how to perform FIB manipulation; kernel routing table updates, interface lookups, and redistribution of routes between different routing protocols. GoBGP uses zebra included in Quagga or FRRouting.
Assume you finished Getting Started and installing Quagga or FRRouting on the same host with GoBGP.
Note: For the integration with FRRouting, version 3.0.x (Zebra API version 4), 5.0.x (Zebra API version 5), and 6.0.x (Zebra API version 6) is supported. FRRouting version 4.0.x is not work correctly, because FRRouting version 5.0.x changes zebra message and it doesn't keep backward compatibility for FRRouting version 4.0.x although FRRouting version 4.0.x and 5.0.x use Zebra API version 5.
You need to enable the zebra feature in the Global configuration as follows.
[zebra]
[zebra.config]
enabled = true
url = "unix:/var/run/quagga/zserv.api"
redistribute-route-type-list = ["connect"]
version = 2
-
url
specifies the path to the unix domain socket or the TCP port for connecting to Zebra API. If omitted, GoBGP will use"unix:/var/run/quagga/zserv.api"
by the default. Please note that with FRRouting, the path to the unix domain socket would be like"unix:/var/run/frr/zserv.api"
. To specify the TCP port,url
value would be like"tcp:192.168.24.1:2600"
. -
redistribute-route-type-list
specifies which route types you want to receive from Zebra daemon. For example, with["connect"]
, GoBGP will receive the connected routes and redistribute them. -
version
specifies Zebra API version.2
is the version used by Quagga on Ubuntu 16.04 LTS. To enable the Next-Hop Tracking features, please specify3
or later. For connecting to FRRouting 3.0.x, please specify4
. For connecting to FRRouting 5.0.x, please specify5
. For connecting to FRRouting 6.0.x, please specify6
. -
mpls-label-range-size
specifies mpls label range size for requesting to Zebra. It works with FRRouting 5.0.x or FRRouting 6.0.x.
Zebra has 3 connected routes in this example's environment.
- 172.16.1.100/30
- 172.16.6.100/30
- 192.168.31.0/24
Let's check these routes with GoBGP cli.
$ gobgp global rib
Network Next Hop AS_PATH Age Attrs
*> 172.16.1.100/30 0.0.0.0 00:00:02 [{Origin: i} {Med: 1}]
*> 172.16.6.100/30 0.0.0.0 00:00:02 [{Origin: i} {Med: 1}]
*> 192.168.31.0/24 0.0.0.0 00:00:02 [{Origin: i} {Med: 1}]
You can see connected routes stored in the GoBGP global rib.