CRXN
/
docs
mirror of https://codeberg.org/CRXN/docs.git
1
0
Fork 0
Code Releases Activity

Merge pull request 'add random rid for babel' (#20) from mark22k/docs:babel_rid into master 

Reviewed-on: https://codeberg.org/CRXN/docs/pulls/20
This commit is contained in:
Marek Küthe 2023-01-11 07:37:40 +00:00
parent 6474db556d c998e28710
commit 7c6590af44
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/routing/bird/bird.md
View File

@ -107,6 +107,8 @@ protocol kernel {
}
protocol babel crxn_net {
randomize router id on;
interface "crxn_peer1" {
type wired;
rxcost 30;
@ -226,6 +228,8 @@ The keyword `persist` can be used to prevent bird from deleting routes from the
```
protocol babel crxn_net {
randomize router id on;
interface "crxn_peer1" {
type wired;
rxcost 30;
@ -246,6 +250,7 @@ With `interface "crxn*";` you can mark any interface starting with `crxn` as a p
Therefore it makes sense to define a separate interface for each peer. As `type` there are `wired` and `wireless`. In general `wired` is always used. According to the `type` parameter babel is adjusted. With `rxcost` we define the "cost", which a peer needs to us. Without specification this is 96. Here it is recommended to take the latency as cost. If you want to avoid that packets are routed through you, you can increase the cost.
In this example, there is a connection to our peer via the interface `crxn_peer1`. This is a wired connection with a latency of 30ms.
`randomize router id on;` If a Babel peer is restarted in a short time, other peers may reject its routes. To prevent this, you can randomize the first 32 bits of your router ID at each startup, which will cause other Babel peers to think you are a "new" peer and therefore accept your routes.
```
protocol device {}