BIRD: Explained the two configuration files we will be editing
This commit is contained in:
parent
881c9b5bce
commit
19d7538784
|
@ -36,7 +36,12 @@ This will ensure that the routing daemon starts on boot.
|
|||
|
||||
## Configuration
|
||||
|
||||
TODO: Mention what configuration files we will be editing
|
||||
In this section we will be configuring two files:
|
||||
|
||||
1. `bird.conf`
|
||||
* For general BIRD configuration e.g. _router IDs_, _device protocol_ and _includes_
|
||||
2. `crxn.conf`
|
||||
* For CRXN-specific details
|
||||
|
||||
### Basics
|
||||
|
||||
|
@ -56,6 +61,10 @@ TODO: These need to be unique - check how much this applies etc
|
|||
|
||||
These router IDs are required to be unique as they are used in the various protocols that BIRD supports in order to determine where a route advertisement came from - see them as a unique identifier of your BIRD router. Failing to do so will cause issues when routing on CRXN **and** a banning (TODO: see how we can enforce this).
|
||||
|
||||
### CRXN-specific setup
|
||||
|
||||
TODO: Do this
|
||||
|
||||
### Tables
|
||||
|
||||
We need to define the routing tables that BIRD will use in its process to store the routes that we want to learn from other routers and also advertise. Such a definition looks as follows:
|
||||
|
|
Loading…
Reference in New Issue