KRT: Error sending route 192.168.x.x/32 to kernel: File exists

[Victor Sudakov]

Bernd Naumann wrote:
> 
> It's just a guess, but maybe re-enable `protocol direct` and add `interface
> "*";` so all device routes are known to bird?

This is what I did and it has probably fixed the problem:

1. Reenabled "protocol direct"
2. Set "export none" for protocol OSPF.

Now I have direct1 routes in the master table which are not propagated
to OSPF as external routes.

Now the question. Why did it work (that is, why did it stop the annoying
message about existing routes)?

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49 at fidonet http://vas.tomsk.ru/