From 63123b3d66296551363d9d4a3d4d0f339c10eb61 Mon Sep 17 00:00:00 2001 From: Alarig Le Lay Date: Thu, 17 Oct 2024 15:25:24 +0200 Subject: [PATCH] README formating Signed-off-by: Alarig Le Lay --- README.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 122a0ea..48315b3 100644 --- a/README.md +++ b/README.md @@ -1,16 +1,20 @@ # What the scripts are used for -`/usr/local/sbin/update-irr-filters.sh` Has to be put in a cron -`/usr/local/sbin/update-check-import.sh` Is used to do generate the stuff common to all peers -`/usr/local/sbin/generate-irr-filter.sh` Is used to generate each peer configuration + * `/usr/local/sbin/update-irr-filters.sh` has to be put in a cron + * `/usr/local/sbin/update-check-import.sh` is used to do generate the stuff + common to all peers + * `/usr/local/sbin/generate-irr-filter.sh` is used to generate each peer + configuration # Configuration files `/usr/local/etc/bird-peers-update.conf` is sourced for three variables: * `PDB_API_KEY` which will be used to query the peeringdb api - * `BIRD_CONF_PATH` for the base dir of bird (freebsd and linux have different ones) + * `BIRD_CONF_PATH` for the base dir of bird (freebsd and linux have + different ones) * `IXP_ASN` the ixp asn for the communities # Override some peers configuration -If you want to add some configuration for some particular peers, you can do it like that: +If you want to add some configuration for some particular peers, you can do it +like that: ``` root@lillix-rs2:~# cat /usr/local/etc/bird-override/bgp_208627_ALARIG_193_34_197_135.conf bfd on;