I remember talking a little bit about something similar in the past here on the list.

Something I had suggested, which I already use to a certain extent, is to separate the settings of different snippets into different files, with includes.

For example, everything that is common is in a main file.
Everything that is downstream prefix-list is each one in its file (Ex: AS1234_prefix.conf)

From a settings organization point of view, this helps a lot!
It also makes it easy to see in git which files have changed over time.

But that doesn't change the BIRD reload at all.
Unfortunately.

Em qui., 14 de jul. de 2022 às 10:04, Nico Schottelius <nico.schottelius@ungleich.ch> escreveu:

Good morning fellow bird users,

I was wondering how you handle "dynamic reconfigurations" such as
rerouting, adding filters, changing the priority of routes in case of
attacks?

In particular I wonder if there is a "good way" to tell bird to lower or
raise a certain route temporarily, i.e. something that would be reset on
a reload? Or to tell bird to forget about specific routes that you want
to filter for blackholing certain parts?

So far in case of attacks we usually edit bird.conf, reload
bird and after the attacks are done, purge/overwrite the config with our
config management (cdist in our case).

This works, but has a bit of a write-reload instead of a set-and-forget
behaviour, and I was more looking to something like "set on a switch,
but don't issue the write command"-mode.

Any thoughts on this?

Best regards,

Nico

--
Sustainable and modern Infrastructures by ungleich.ch