Hello,

the first message says that 10.0.0.1 is either your own address or it isn’t considered reachable from what we can see on the interfaces.

To find out what causes the File exists message, we’ll need you to allow debug all; inside the ipv4 block of your protocol kernel and send us a log snippet around this message when it appears next time. Otherwise, we know nothing. It is possibly BIRD trying to export a colliding route.

Maybe, but that’s a wild guess, you’re running OpenBSD (?) and you have another route inside BIRD for xx.yy.zz.0/24. If that’s right, there is quite a lot additional questions about what you are trying to achieve and whether this is a good or bad state. But I’ll keep them for later.

Have a nice day!
Maria

On Wed, Jan 08, 2025 at 08:53:45PM +0000, LIU Chris via Bird-users wrote:

Classified as: {Hitachi Rail - Public}
 
Basically configured bird as below
 
protocol device  {
            scan time 10;
}
 
protocol kernel {
         scan time 10;
          learn;
          ipv4  {
                       export filter XXXX;
          }
}
 
bgp and bfd are established, everything is fine.
But only have some annoying log:
 
Every 10 seconds to print below bird log, assuming this is caused by kernel protocol scan time 10.  But why Netlink : File exists, it would write to kernel ???
KRT:     Received route xx.yy.zz.0/24 with strange next-hop 10.0.0.1
Netlink: File exists
 
Chris
 
 
 
{Hitachi Rail - Public}

–
Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.