I think because in this query you are checking both IPv4 and IPv6 routes with v6 roa table, so IPv6 routes are getting statuses VALID/INVALID/UNKNOWN, and all IPv4 routes are getting UNKNOWN. So you see in the result. I think you might want to add something like that to your filter: net.type = NET_IP6 && roa_check(r6) = ROA_UNKNOWN
On Tue, Mar 25, 2025 at 10:13 AM <ushi...@ate-mahoroba.jp> wrote: > Thanks Alexander for the response. > > I confirmed that the following commands were executed and the results of > VALID and INVALID were displayed. > > bird> show route where roa_check(r6) = ROA_VALID > bird> show route where roa_check(r6) = ROA_INVALID > > In the case of VALID and INVALID, the results for v6 are displayed, but in > the case of UNKNOWN, even if the following command is executed, the results > for both v4 and v6 are displayed. > > Is it because ROA_UNKNOWN cannot distinguish between v4 and v6, or is it a > bug in bird? > (The version of bird is 2.14) > > > On Sun, 23 Mar 2025 13:58:55 +0100 > Alexander Zubkov <gr...@qrator.net> wrote: > > > Hi, > > > > Doesn't it work when using in CLI expressions? Like this: > > show route where roa_check(...) = ROA_VALID > > > > On Sun, Mar 23, 2025 at 10:24?AM <ushi...@ate-mahoroba.jp> wrote: > > > > > Hi > > > > > > I am using roa_check(). > > > Is there a bird command that checks the result of roa_check() on the > > > command line, not just in the conf processing? > > > > > > > >
