howto/Bird2.md
... ...
@@ -53,15 +53,15 @@ protocol device {
53 53
* Utility functions
54 54
*/
55 55
56
-function is_self_net() {
56
+function is_self_net() -> bool {
57 57
return net ~ OWNNETSET;
58 58
}
59 59
60
-function is_self_net_v6() {
60
+function is_self_net_v6() -> bool {
61 61
return net ~ OWNNETSETv6;
62 62
}
63 63
64
-function is_valid_network() {
64
+function is_valid_network() -> bool {
65 65
return net ~ [
66 66
172.20.0.0/14{21,29}, # dn42
67 67
172.20.0.0/24{28,32}, # dn42 Anycast
... ...
@@ -88,7 +88,7 @@ protocol static {
88 88
include "/etc/bird/roa_dn42_v6.conf";
89 89
};
90 90
91
-function is_valid_network_v6() {
91
+function is_valid_network_v6() -> bool {
92 92
return net ~ [
93 93
fd00::/8{44,64} # ULA address space as per RFC 4193
94 94
];
... ...
@@ -204,6 +204,7 @@ protocol bgp <NEIGHBOR_NAME>_v6 from dnpeers {
204 204
}
205 205
```
206 206
And for the case of MP-BGP over IPV6 with ENH
207
+This work without a configured IPV4 in the link interface
207 208
```conf
208 209
protocol bgp <NEIGHBOR_NAME> from dnpeers {
209 210
enable extended messages on;
... ...
@@ -434,6 +435,7 @@ To do a basic configuration you need to add 1 line to your bird.conf and enable
434 435
template.
435 436
It is currently recommended that you only enable it for each peer that supports it and has it enabled.
436 437
Add this above the template for dnpeers.
438
+It acts as a detection mechanism that is very fast and can detect for example if your tunnel link is down.
437 439
```conf
438 440
protocol bfd {};
439 441
```