mirror of
http://deavmi.assigned.network/git/CRXN/docs
synced 2025-02-21 07:26:49 +00:00
BIRD: Added information on the device
protocol
This commit is contained in:
parent
52f504117a
commit
87943e83f3
@ -61,6 +61,19 @@ 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).
|
||||
|
||||
#### Device protocol
|
||||
|
||||
BIRD supports many protocols which are used to import routing data from and export routing data to. However, the most basic of protocols which BIRD supports is known as the `device` protocol. The job of this protocol is just to provide basic device information to BIRD over time, it is required but luckily does not require much setup.
|
||||
|
||||
All that is required for this protocol to work is the following:
|
||||
|
||||
```
|
||||
protocol device {
|
||||
}
|
||||
```
|
||||
|
||||
You can adjust [scan times and such](https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.4) but the kernel normally will signal any changes to BIRD.
|
||||
|
||||
### CRXN-specific setup
|
||||
|
||||
TODO: Do this
|
||||
|
Loading…
Reference in New Issue
Block a user