howto/Bird.md
... ...
@@ -182,6 +182,15 @@ function is_valid_network() {
182 182
}
183 183
```
184 184
185
+```
186
+# /etc/bird/peers6/<PEER_NAME>
187
+protocol bgp <PEER_NAME> from dnpeers {
188
+ neighbor <PEERING_IP> as <PEER_AS>;
189
+ # if you use link-local ipv6 addresses for peering using the following
190
+ # neighbor <PEERING_IP> % '<INTERFACE_NAME>' as <PEER_AS>;
191
+};
192
+```
193
+
185 194
### IPv4
186 195
187 196
```
... ...
@@ -330,8 +339,6 @@ protocol bgp <PEER_NAME> from dnpeers {
330 339
};
331 340
```
332 341
333
-
334
-
335 342
# Bird communities
336 343
337 344
Communities can be used to prioritize traffic based on different flags, in DN42 we are using communities to prioritize based on latency, bandwidth and encryption. It is really easy to get started with communities and we encourage all of you to get the basic configuration done and to mark your peerings with the correct flags for improved routing.