Hi Ondrej,
That works! thanks!
I now just create a random number each time the config is generated:
# random number which forces the RPKI roa_table to be re-evaluated
define force_roa_table_update = {{ range(1, 100) | random }};
...
function RPKI_PrefixFiltering() {
if force_roa_table_up
On Fri, Jun 09, 2017 at 01:17:08PM +0200, Stefan Plug wrote:
> Hi guys,
>
> Bird 1.6.3
>
> Just testing about with the RPKI roa_check and it seems that my routes are
> not being re-evaluated after a "configure" when my roa table is updated.
> I do this check during the import phase so the routes
Thanks for the info!
Then I'll keep the implementation of this on hold for now :(
Stefan
On 09.06.2017 14:36, Jan Matejka wrote:
> Hi!
>
> On 06/09/2017 01:17 PM, Stefan Plug wrote:
>> Bird 1.6.3
>>
>> Just testing about with the RPKI roa_check and it seems that my routes are
>> not being re-e
Hi!
On 06/09/2017 01:17 PM, Stefan Plug wrote:
> Bird 1.6.3
>
> Just testing about with the RPKI roa_check and it seems that my routes are
> not being re-evaluated after a "configure" when my roa table is updated.
> I do this check during the import phase so the routes are already in the
> tabl
Hi guys,
Bird 1.6.3
Just testing about with the RPKI roa_check and it seems that my routes are not
being re-evaluated after a "configure" when my roa table is updated.
I do this check during the import phase so the routes are already in the table
once I update the roa table.
simple check examp
