<WARN> xxxx.ipv4: Automatic RPKI reload not active for import

[ushiroz at ate-mahoroba.jp]

Thank you, as always, for your quick answers!

Currently using RPKI functionality and calls roa_check().

Allowing the output of warning messages and

RPKI reload is ON and import table on is not defined.

I am thinking of doing this.
Is this a problem?


On Mon, 9 Sep 2024 09:55:04 +0200
Maria Matejka <maria.matejka at nic.cz> wrote:

> > > Therefore you can use import table, the only problem will be that if you
> > > show routes from the import table, you should disregard what is shown as
> > > the local nexthop.
> > 
> > The logs “Cannot reconfigure channel xxxx .ipv4” and “Cannot
> > reconfigure channel xxxx .ipv6” that are output when the import table
> > on <-> import table off setting is changed and the logs ” Restarting
> > protocol xxxx” logs, but does it mean that when the import table
> > setting is changed, a restart is performed?
> 
> Yes. You have to fill the table with something, and although it could be
> technically possible to refill it just by requesting route refresh, it
> seems that nobody actually implemented this fast track, so it's resolved
> by restarting the peer.
> 
> It should not be too difficult to implement, yet with the BIRD 3
> upcoming (where the import table is implemented differently) this may
> get a little bit trickier. If there is anybody willing to do it, just
> let us know please to get some hints and directions.
> 
> Maria
> 
> -- 
> Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.