CRXN
/
docs
mirror of http://deavmi.assigned.network/git/CRXN/docs
1
0
Fork 0
Code Releases Activity

Change recommended RTT Cost

This commit is contained in:
Marek Küthe 2024-07-17 18:34:33 +00:00
parent 1ba6d6ad65
commit 8427569646
No known key found for this signature in database
GPG Key ID: 7E869146699108C7
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/routing/babeld/babeld.md
View File

@ -32,7 +32,7 @@ random-id true
link-detect true link-detect true
default hello-interval 4 type tunnel rtt-min 10 rtt-max 1000 enable-timestamps true default hello-interval 4 type tunnel rtt-min 10 rtt-max 1000 max-rtt-penalty 192 enable-timestamps true
interface <PEER> type tunnel interface <PEER> type tunnel

4
docs/routing/bird/rtt.md
View File

@ -14,12 +14,12 @@ To add a peering with RTT, the attributes `rtt min`, `rtt max` and `rtt cost` ar
``` ```
interface "crxn_peer2" { interface "crxn_peer2" {
type tunnel; type tunnel;
rtt cost 96; rtt cost 192;
rtt min 10 ms; rtt min 10 ms;
rtt max 1000 ms; rtt max 1000 ms;
}; };
``` ```
The `rxcost` is set to the default value for the interface type. However, this is less relevant as the rxcost is also influenced by the RTT. If the RTT is less than 10 ms, no RTT-specific change is made; if the RTT is over 1000 ms or 1 s, the maximum RTT-specific cost is added. You can also use `rtt cost` to specify how high the maximum RTT specific costs may be. These are 96 for tunnel interfaces and 0 otherwise. The `rxcost` is set to the default value for the interface type. However, this is less relevant as the rxcost is also influenced by the RTT. If the RTT is less than 10 ms, no RTT-specific change is made; if the RTT is over 1000 ms or 1 s, the maximum RTT-specific cost is added. You can also use `rtt cost` to specify how high the maximum RTT specific costs may be. These are 96 for tunnel interfaces and 0 otherwise. In the case of CRXN, 192 is recommended - the RTT costs are therefore increased approximately every fifth second in the RTT.
There is also the `max-rtt-penalty` setting, which specifies how quickly old RTT measurements should be discarded and therefore no longer included in the calculation (higher values mean that old measurements are discarded more quickly). The default value is 42, but if you have the feeling or observation that this is not suitable for the link between the routers you can increase the value, for example to `125` or similar. There is also the `max-rtt-penalty` setting, which specifies how quickly old RTT measurements should be discarded and therefore no longer included in the calculation (higher values mean that old measurements are discarded more quickly). The default value is 42, but if you have the feeling or observation that this is not suitable for the link between the routers you can increase the value, for example to `125` or similar.
## Links ## Links