github-mirror/route0
1
0
Fork 0
mirror of https://github.com/Wojtek242/route0.git synced 2024-11-21 23:05:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fixes to zebra and static config lesson

Browse Source
This commit is contained in:
Wojciech Kozlowski 2019-04-09 23:16:26 +02:00
parent 4824e454b5
commit 75dc7e0d4a
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
lessons/configuring-zebra-and-static.md
View File

@ -20,6 +20,16 @@ Before you continue with the lesson you may find it useful to read the brief
section on [system architecture on the FRR section on [system architecture on the FRR
website](http://docs.frrouting.org/en/latest/overview.html#system-architecture). website](http://docs.frrouting.org/en/latest/overview.html#system-architecture).
## A note on running FRR daemons on hosts
It is a bit unusual to run the FRR daemons on the end-hosts as they are not
routers and do not need anything other than an IP address and a default route.
This could be achieved in Mininet in different ways using Python. However, by
using the FRR daemons, the configuration can be done through configuration
files read in at startup. This makes it much easier to define and maintain
topologies because as it keeps all IP address configuration for end-hosts in
the same place as router configuration.
## Starting the daemons ## Starting the daemons
Before we start the network we need to actually create a basic configuration Before we start the network we need to actually create a basic configuration
@ -206,7 +216,7 @@ the FRR daemons!
The manual configuration process was rather tedious which is why configuration The manual configuration process was rather tedious which is why configuration
files exist. When you start the network in the `basic` scenario using files exist. When you start the network in the `basic` scenario using
`route0.py` it simply reads in a bunch of configuration files. The ones it `route0.py` it simply reads in a bunch of configuration files. The ones it
reads on for `one_rtr` can be found in the reads in for `one_rtr` can be found in the
[`staticd`](../topology/one_rtr/staticd) and [`staticd`](../topology/one_rtr/staticd) and
[`zebra`](../topology/one_rtr/zebra) directories in its [topology [`zebra`](../topology/one_rtr/zebra) directories in its [topology
directory](../topology/one_rtr). Have a look at them and see how similar they directory](../topology/one_rtr). Have a look at them and see how similar they