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

Add some notes to README

Browse Source
This commit is contained in:
Wojciech Kozlowski 2019-04-09 22:08:53 +02:00
parent 1611bb8c3b
commit 4824e454b5
1 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -240,7 +240,7 @@ An experiment is simply a particular topology and scenario combination.
Technically this is redundant since scenarios are strictly associated with only Technically this is redundant since scenarios are strictly associated with only
one topology, but using different terminology avoids confusion. one topology, but using different terminology avoids confusion.
### A note on configuration files ### Configuration files
The official FRR documentation recommends using only a single configuration The official FRR documentation recommends using only a single configuration
file `frr.conf` per router. This makes sense if we are only running a single file `frr.conf` per router. This makes sense if we are only running a single
@ -260,6 +260,24 @@ but since we are running multiple instances on multiple virtual nodes on a
single physical device, it makes it easier to inspect and compare the single physical device, it makes it easier to inspect and compare the
configurations on a protocol level. configurations on a protocol level.
### End-host configuration files
It's not entirely normal to run FRR daemons on end-hosts. However, they still
need their IP address and default route configured and the options are to do it
either from a Python script or use FRR daemons. Using the FRR `zebra` and
`staticd` daemons makes it easier to configure the end-hosts together with the
actual routers. However, they should not be running any daemon other than
`zebra` and `staticd`.
### A note on VTY shell
The recommended way of connecting to daemons by FRR is to use the [VTY
shell](http://docs.frrouting.org/en/latest/vtysh.html) which can connect to all
the daemons simultaneously. Unfortunately, in our configuration where multiple
instances of the same daemon run on the same machine in Mininet, it gets
confused and it doesn't connect as expected. Therefore, you can't use the VTY
shell with Route 0.
## Contributing ## Contributing
For information on how to contribute see [CONTRIBUTING](CONTRIBUTING.md). For information on how to contribute see [CONTRIBUTING](CONTRIBUTING.md).