6 .. index:: How to install FRR
7 .. index:: Installation
8 .. index:: Installing FRR
9 .. index:: Building the system
12 This section covers the basics of building, installing and setting up FRR.
17 The project publishes packages for Red Hat, Centos, Debian and Ubuntu on the
18 `GitHub releases <https://github.com/FRRouting/frr/releases>`_. page. External
19 contributors offer packages for many other platforms including \*BSD, Alpine,
20 Gentoo, Docker, and others. There is currently no documentation on how to use
21 those but we hope to add it soon.
26 In addition to traditional packages the project also builds and publishes
27 universal Snap images, available at https://snapcraft.io/frr.
32 Building FRR from source is the best way to ensure you have the latest features
33 and bug fixes. Details for each supported platform, including dependency
34 package listings, permissions, and other gotchas, are in the developer's
35 documentation. This section provides a brief overview on the process.
40 FRR's source is available on the project
41 `GitHub page <https://github.com/FRRouting/frr>`_.
45 git clone https://github.com/FRRouting/frr.git
47 When building from Git there are several branches to choose from. The
48 ``master`` branch is the primary development branch. It should be considered
49 unstable. Each release has its own branch named ``stable/X.X``, where ``X.X``
50 is the release version.
52 In addition, release tarballs are published on the GitHub releases page
53 `here <https://github.com/FRRouting/frr/releases>`_.
58 .. index:: Configuration options
59 .. index:: Options for configuring
60 .. index:: Build options
61 .. index:: Distribution configuration
62 .. index:: Options to `./configure`
64 FRR has an excellent configure script which automatically detects most host
65 configurations. There are several additional configure options to customize the
66 build to include or exclude specific features and dependencies.
68 First, update the build system. Change into your FRR source directory and issue:
74 This will install any missing build scripts and update the Autotools
75 configuration. Once this is done you can move on to choosing your configuration
76 options from the list below.
78 .. _frr-configuration:
80 .. program:: configure
82 .. option:: --enable-tcmalloc
84 Enable the alternate malloc library. In some cases this is faster and more efficient,
85 in some cases it is not.
87 .. option:: --disable-doc
89 Do not build any documentation, including this one.
91 .. option:: --enable-doc-html
93 From the documentation build html docs as well in addition to the normal output.
95 .. option:: --disable-zebra
97 Do not build zebra daemon. This generally only be useful in a scenario where
98 you are building bgp as a standalone server.
100 .. option:: --disable-ripd
104 .. option:: --disable-ripngd
108 .. option:: --disable-ospfd
112 .. option:: --disable-ospf6d
116 .. option:: --disable-bgpd
120 .. option:: --disable-ldpd
124 .. option:: --disable-nhrpd
128 .. option:: --disable-eigrpd
132 .. option:: --disable-babeld
136 .. option:: --disable-watchfrr
138 Do not build watchfrr. Watchfrr is used to integrate daemons into startup/shutdown
139 software available on your machine. This is needed for systemd integration, if you
140 disable watchfrr you cannot have any systemd integration.
142 .. option:: --enable-systemd
144 Build watchfrr with systemd integration, this will allow FRR to communicate with
145 systemd to tell systemd if FRR has come up properly.
147 .. option:: --disable-pimd
149 Turn off building of pimd. On some BSD platforms pimd will not build properly due
150 to lack of kernel support.
152 .. option:: --disable-pbrd
154 Turn off building of pbrd. This daemon currently requires linux in order to function
157 .. option:: --enable-sharpd
159 Turn on building of sharpd. This daemon facilitates testing of FRR and can also
160 be used as a quick and easy route generator.
162 .. option:: --disable-staticd
164 Do not build staticd. This daemon is necessary if you want static routes.
166 .. option:: --disable-bfdd
170 .. option:: --disable-bgp-announce
172 Make *bgpd* which does not make bgp announcements at all. This
173 feature is good for using *bgpd* as a BGP announcement listener.
175 .. option:: --disable-bgp-vnc
177 Turn off bgpd's ability to use VNC.
179 .. option:: --enable-datacenter
181 Enable system defaults to work as if in a Data Center. See defaults.h
182 for what is changed by this configure option.
184 .. option:: --enable-snmp
186 Enable SNMP support. By default, SNMP support is disabled.
188 .. option:: --disable-ospfapi
190 Disable support for OSPF-API, an API to interface directly with ospfd.
191 OSPF-API is enabled if --enable-opaque-lsa is set.
193 .. option:: --disable-ospfclient
195 Disable building of the example OSPF-API client.
197 .. option:: --disable-ospf-ri
199 Disable support for OSPF Router Information (RFC4970 & RFC5088) this
200 requires support for Opaque LSAs and Traffic Engineering.
202 .. option:: --disable-isisd
206 .. option:: --disable-fabricd
208 Do not build fabricd.
210 .. option:: --enable-isis-topology
212 Enable IS-IS topology generator.
214 .. option:: --enable-isis-te
216 Enable Traffic Engineering Extension for ISIS (RFC5305)
218 .. option:: --enable-realms
220 Enable the support of Linux Realms. Convert tag values from 1-255 into a
221 realm value when inserting into the Linux kernel. Then routing policy can be
222 assigned to the realm. See the tc man page.
224 .. option:: --disable-rtadv
226 Disable support IPV6 router advertisement in zebra.
228 .. option:: --enable-gcc-rdynamic
230 Pass the ``-rdynamic`` option to the linker driver. This is in most cases
231 necessary for getting usable backtraces. This option defaults to on if the
232 compiler is detected as gcc, but giving an explicit enable/disable is
235 .. option:: --disable-backtrace
237 Controls backtrace support for the crash handlers. This is autodetected by
238 default. Using the switch will enforce the requested behaviour, failing with
239 an error if support is requested but not available. On BSD systems, this
240 needs libexecinfo, while on glibc support for this is part of libc itself.
242 .. option:: --enable-dev-build
244 Turn on some options for compiling FRR within a development environment in
245 mind. Specifically turn on -g3 -O0 for compiling options and add inclusion
248 .. option:: --enable-fuzzing
250 Turn on some compile options to allow you to run fuzzing tools against the
251 system. This flag is intended as a developer only tool and should not be
252 used for normal operations.
254 .. option:: --disable-snmp
256 Build without SNMP support.
258 .. option:: --disable-vtysh
262 .. option:: --enable-fpm
264 Build with FPM module support.
266 .. option:: --enable-numeric-version
268 Alpine Linux does not allow non-numeric characters in the version string.
269 With this option, we provide a way to strip out these characters for APK dev
272 .. option:: --enable-multipath=X
274 Compile FRR with up to X way ECMP supported. This number can be from 0-999.
275 For backwards compatibility with older configure options when setting X = 0,
276 we will build FRR with 64 way ECMP. This is needed because there are
277 hardcoded arrays that FRR builds towards, so we need to know how big to
278 make these arrays at build time. Additionally if this parameter is
279 not passed in FRR will default to 16 ECMP.
281 .. option:: --enable-shell-access
283 Turn on the ability of FRR to access some shell options( telnet/ssh/bash/etc. )
284 from vtysh itself. This option is considered extremely unsecure and should only
285 be considered for usage if you really really know what you are doing.
287 .. option:: --enable-gcov
289 Code coverage reports from gcov require adjustments to the C and LD flags.
290 With this option, gcov instrumentation is added to the build and coverage
291 reports are created during execution. The check-coverage make target is
292 also created to ease report uploading to codecov.io. The upload requires
293 the COMMIT (git hash) and TOKEN (codecov upload token) environment variables
296 .. option:: --enable-config-rollbacks
298 Build with configuration rollback support. Requires SQLite3.
300 .. option:: --enable-confd=<dir>
302 Build the ConfD northbound plugin. Look for the libconfd libs and headers
305 .. option:: --enable-sysrepo
307 Build the Sysrepo northbound plugin.
309 You may specify any combination of the above options to the configure
310 script. By default, the executables are placed in :file:`/usr/local/sbin`
311 and the configuration files in :file:`/usr/local/etc`. The :file:`/usr/local/`
312 installation prefix and other directories may be changed using the following
313 options to the configuration script.
315 .. option:: --prefix <prefix>
317 Install architecture-independent files in `prefix` [/usr/local].
319 .. option:: --sysconfdir <dir>
321 Look for configuration files in `dir` [`prefix`/etc]. Note that sample
322 configuration files will be installed here.
324 .. option:: --localstatedir <dir>
326 Configure zebra to use `dir` for local state files, such as pid files and
329 .. option:: --with-yangmodelsdir <dir>
331 Look for YANG modules in `dir` [`prefix`/share/yang]. Note that the FRR
332 YANG modules will be installed here.
334 Python dependency, documentation and tests
335 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
337 FRR's documentation and basic unit tests heavily use code written in Python.
338 Additionally, FRR ships Python extensions written in C which are used during
341 To this extent, FRR needs the following:
343 * an installation of CPython, preferably version 3.2 or newer (2.7 works but
344 is end of life and will stop working at some point.)
345 * development files (mostly headers) for that version of CPython
346 * an installation of `sphinx` for that version of CPython, to build the
348 * an installation of `pytest` for that version of CPython, to run the unit
351 The `sphinx` and `pytest` dependencies can be avoided by not building
352 documentation / not running ``make check``, but the CPython dependency is a
353 hard dependency of the FRR build process (for the `clippy` tool.)
355 .. _least-privilege-support:
357 Least-Privilege Support
358 """""""""""""""""""""""
360 .. index:: FRR Least-Privileges
361 .. index:: FRR Privileges
363 Additionally, you may configure zebra to drop its elevated privileges
364 shortly after startup and switch to another user. The configure script will
365 automatically try to configure this support. There are three configure
366 options to control the behaviour of FRR daemons.
368 .. option:: --enable-user <user>
370 Switch to user `user shortly after startup, and run as user `user` in normal
373 .. option:: --enable-group <user>
375 Switch real and effective group to `group` shortly after startup.
377 .. option:: --enable-vty-group <group>
379 Create Unix Vty sockets (for use with vtysh) with group ownership set to
380 `group`. This allows one to create a separate group which is restricted to
381 accessing only the vty sockets, hence allowing one to delegate this group to
382 individual users, or to run vtysh setgid to this group.
384 The default user and group which will be configured is 'frr' if no user or
385 group is specified. Note that this user or group requires write access to the
386 local state directory (see :option:`--localstatedir`) and requires at least
387 read access, and write access if you wish to allow daemons to write out their
388 configuration, to the configuration directory (see :option:`--sysconfdir`).
390 On systems which have the 'libcap' capabilities manipulation library (currently
391 only Linux), FRR will retain only minimal capabilities required and will only
392 raise these capabilities for brief periods. On systems without libcap, FRR will
393 run as the user specified and only raise its UID to 0 for brief periods.
398 .. index:: Building on Linux boxes
399 .. index:: Linux configurations
401 There are several options available only to GNU/Linux systems. If you use
402 GNU/Linux, make sure that the current kernel configuration is what you want.
403 FRR will run with any kernel configuration but some recommendations do exist.
405 :makevar:`CONFIG_NETLINK`
406 Kernel/User Netlink socket. This enables an advanced interface between
407 the Linux kernel and *zebra* (:ref:`kernel-interface`).
409 :makevar:`CONFIG_RTNETLINK`
410 This makes it possible to receive Netlink routing messages. If you specify
411 this option, *zebra* can detect routing information updates directly from
412 the kernel (:ref:`kernel-interface`).
414 :makevar:`CONFIG_IP_MULTICAST`
415 This option enables IP multicast and should be specified when you use *ripd*
416 (:ref:`rip`) or *ospfd* (:ref:`ospfv2`) because these protocols use
419 Linux sysctl settings and kernel modules
420 ````````````````````````````````````````
422 There are several kernel parameters that impact overall operation of FRR when
423 using Linux as a router. Generally these parameters should be set in a
424 sysctl related configuration file, e.g., :file:`/etc/sysctl.conf` on
425 Ubuntu based systems and a new file
426 :file:`/etc/sysctl.d/90-routing-sysctl.conf` on Centos based systems.
427 Additional kernel modules are also needed to support MPLS forwarding.
429 :makevar:`IPv4 and IPv6 forwarding`
430 The following are set to enable IP forwarding in the kernel:
432 .. code-block:: shell
434 net.ipv4.conf.all.forwarding=1
435 net.ipv6.conf.all.forwarding=1
437 :makevar:`MPLS forwarding`
438 Basic MPLS support was introduced in the kernel in version 4.1 and
439 additional capability was introduced in 4.3 and 4.5.
440 For some general information on Linux MPLS support, see
441 https://www.netdevconf.org/1.1/proceedings/slides/prabhu-mpls-tutorial.pdf.
442 The following modules should be loaded to support MPLS forwarding,
443 and are generally added to a configuration file such as
444 :file:`/etc/modules-load.d/modules.conf`:
446 .. code-block:: shell
448 # Load MPLS Kernel Modules
452 The following is an example to enable MPLS forwarding in the
453 kernel, typically by editing :file:`/etc/sysctl.conf`:
455 .. code-block:: shell
457 # Enable MPLS Label processing on all interfaces
458 net.mpls.conf.eth0.input=1
459 net.mpls.conf.eth1.input=1
460 net.mpls.conf.eth2.input=1
461 net.mpls.platform_labels=100000
463 Make sure to add a line equal to :file:`net.mpls.conf.<if>.input` for
464 each interface *'<if>'* used with MPLS and to set labels to an
467 :makevar:`VRF forwarding`
468 General information on Linux VRF support can be found in
469 https://www.kernel.org/doc/Documentation/networking/vrf.txt. Kernel
470 support for VRFs was introduced in 4.3 and improved upon through
471 4.13, which is the version most used in FRR testing (as of June
472 2018). Additional background on using Linux VRFs and kernel specific
473 features can be found in
474 http://schd.ws/hosted_files/ossna2017/fe/vrf-tutorial-oss.pdf.
476 The following impacts how BGP TCP sockets are managed across VRFs:
478 .. code-block:: shell
480 net.ipv4.tcp_l3mdev_accept=0
482 With this setting a BGP TCP socket is opened per VRF. This setting
483 ensures that other TCP services, such as SSH, provided for non-VRF
484 purposes are blocked from VRF associated Linux interfaces.
486 .. code-block:: shell
488 net.ipv4.tcp_l3mdev_accept=1
490 With this setting a single BGP TCP socket is shared across the
491 system. This setting exposes any TCP service running on the system,
492 e.g., SSH, to all VRFs. Generally this setting is not used in
493 environments where VRFs are used to support multiple administrative
496 **Important note** as of June 2018, Kernel versions 4.14-4.18 have a
497 known bug where VRF-specific TCP sockets are not properly handled. When
498 running these kernel versions, if unable to establish any VRF BGP
499 adjacencies, either downgrade to 4.13 or set
500 'net.ipv4.tcp_l3mdev_accept=1'. The fix for this issue is planned to be
501 included in future kernel versions. So upgrading your kernel may also
508 Once you have chosen your configure options, run the configure script and pass
509 the options you chose:
511 .. code-block:: shell
515 --enable-exampledir=/usr/share/doc/frr/examples/ \
516 --localstatedir=/var/run/frr \
517 --sbindir=/usr/lib/frr \
518 --sysconfdir=/etc/frr \
523 After configuring the software, you are ready to build and install it in your
526 .. code-block:: shell
528 make && sudo make install
530 If everything finishes successfully, FRR should be installed. You should now
531 skip to the section on :ref:`basic-setup`.