Dear Elmar, import or export table is a command to note, that the routes will be locally stored in a table for import or export. So you do not need to write it down, it's just a switch. Check the documentation for BGP https://bird.nic.cz/doc/bird-2.16.2.html#bgp and tag "import table switch". I hope this helps. Kind regards, Jana Jana Babovakova (she/her) | BIRD Tech Support | CZ.NIC, z.s.p.o. On 21. 05. 25 12:29, Elmar K. Bins wrote:

Hi Job,

job@sobornost.net (Job Snijders) wrote:

...

...

<peer>: Automatic RPKI reload not active for import

I believe this message relates to "rpki reload _switch_" documented here:https://bird.network.cz/?get_doc&v=20&f=bird-3.html#proto-rpki-reload Thanks for the pointer! I see that this defaults to "On", so the message should not appear; but then the docs mention that it also "requires import table or export table". That formulation is unclear to me; does this mean I have to implement a separate table for every peer (which I, of course, don't)? nobody has that kind of time)?

I'm taking all prefixes into the master4/master6 tables, and atm I'm just tagging, not filtering upon import.

Am I thinking wrong?

Elmar.

job@sobornost.net (Job Snijders) wrote:

Of note - it is good practise to keep the table: it's 'more neighborly'!

Keeping the import table can help reduce the sending of BGP ROUTE-REFRESH messages (which are costly for your peers).

Oh yeah, I'd never not do it on "real routers", but these are anycast nodes advertising two prefixes that never change (only might go away or reappear), so I'm not concerned. CPU churn at these nodes is minimal anyway, but hey, what's two more tables, right? ;-) Thanks for your kind help folks! El Mar.

Hi Jana, bird-users@network.cz (Jana Babovakova via Bird-users) wrote:

import or export table is a command to note, that the routes will be locally stored in a table for import or export. So you do not need to write it down, it's just a switch.

Check the documentation for BGP https://bird.nic.cz/doc/bird-2.16.2.html#bgp and tag "import table switch".

Thanks - that makes it clearer. I'll have to live with the log entries for the near future and might look at implementing received-tables. Btw, as came up yesterday - I'd like to emphasize the necessity of being able to configure log output on a more granular level. Perhaps there's something in the works already? Yours, Elmar.

Dear El Mar. I'm glad it makes sense now. To the logging issue. We have an option how to add more messages using the 'debug' in the conf file :). Otherwise, any functionality to reduce the number of messages in a log file is not available now. There are some plans about that for the future, but not a priority now. Happy routing, Jana Jana Babovakova (she/her) | BIRD Tech Support | CZ.NIC, z.s.p.o. On 21. 05. 25 14:24, Elmar K. Bins wrote:

Hi Jana,

bird-users@network.cz (Jana Babovakova via Bird-users) wrote:

...

import or export table is a command to note, that the routes will be locally stored in a table for import or export. So you do not need to write it down, it's just a switch.

Check the documentation for BGPhttps://bird.nic.cz/doc/bird-2.16.2.html#bgp and tag "import table switch". Thanks - that makes it clearer. I'll have to live with the log entries for the near future and might look at implementing received-tables.

Btw, as came up yesterday - I'd like to emphasize the necessity of being able to configure log output on a more granular level. Perhaps there's something in the works already?

Yours, Elmar.