burble.dn42/grc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Format fixes

Browse Source
This commit is contained in:
Simon Marsh 2019-01-27 16:34:27 +00:00
parent 134554ef0e
commit 37f85b2af3
Signed by: burble
GPG Key ID: 7B9FE8780CFB6593
2 changed files with 16 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -1,23 +1,21 @@
# Global Route Collector # Global Route Collector
The global route collector is a common resource for collecting route data from across the DN42 network. This data can then be used to provide statistics and a global map of the DN42 network. The global route collector is a common resource for collecting route data from across the DN42 network.
This data can then be used to provide statistics and a global map of the DN42 network.
## Providing Routes to the Collector ## Providing Routes to the Collector
All DN42 users are invited to provide routes to the collector; the more users that take part, the more useful the collector becomes. All DN42 users are invited to provide routes to the collector; the more users that take part, the more useful the collector becomes.
1. Contact burble@hackint or mail dn42@burble.com, including your AS number and BGP peer address(es) - Contact burble@hackint or mail dn42@burble.com, including your AS number and BGP peer address(es)
The collector runs bird2 and supports multiprotocol BGP; the preference is for multiprotocol peering over IPv6. The collector runs bird2 and supports multiprotocol BGP; the preference is for multiprotocol peering over IPv6.
If you can't support multiprotocol BGP, please provide both IPv4 and IPv6 peer addresses. If you are unable to support multiprotocol BGP, please provide both IPv4 and IPv6 peer addresses.
2. Configure a BGP session for the collector on your router. - Configure a BGP session for the collector on your router.
Some example client configurations are included in the 'examples' directory.
Users are encouraged to configure the [BGP Add-Path](https://tools.ietf.org/html/rfc7911) extension to provide a comprehensive set of routes to the collector.
3. Profit !
Some example client configurations are included in the 'examples' directory.
Users are encouraged to configure the [BGP Add-Path](https://tools.ietf.org/html/rfc7911) extension to provide a comprehensive set of routes to the collector.
## Route Collector Services ## Route Collector Services
@ -35,3 +33,8 @@ to fix formating and bird2 compatibility.
[http://collector.dn42:9324/metrics](http://collector.dn42:9324/metrics) [http://collector.dn42:9324/metrics](http://collector.dn42:9324/metrics)
The collector runs [bird_exporter](https://github.com/czerwonk/bird_exporter) and the metrics are publically available on the default bird_exporter port. The collector runs [bird_exporter](https://github.com/czerwonk/bird_exporter) and the metrics are publically available on the default bird_exporter port.
### Downstream BGP Sessions
Contact dn42@burble.com if you would like a downstream BGP session for your own analysis or metrics.

2
server/bird/bird.conf
View File

@ -51,7 +51,7 @@ function rc_peer_import6(int peer_as; int peer_ref)
{ {
# accept valid networks # accept valid networks
if net ~ [ if net ~ [
fd00::/8{44,64} fd00::/8+
] then { ] then {
bgp_large_community.add(( GRC_AS, peer_as, peer_ref )); bgp_large_community.add(( GRC_AS, peer_as, peer_ref ));