Hi,
I recently observed a case where bird 2.0.7 emits sub-optimal route
updates during a reconfiguration.
Using the sample configuration of e.g.
ipv4 table seed;
ipv4 table announce;
protocol static {
route 203.0.113.0/24 unreachable;
ipv4 { table seed; };
}
protocol pipe {
table anno
Hello!
Well, this seems to be a forgotten part of the static protocol. I see
the bug, there is a missing reload hook in the appropriate channel.
Queuing this to be fixed soon.
Thank you for the report!
Maria
On 3/5/21 2:43 PM, Damian Zaremba wrote:
Hi,
I recently observed a case where bir
