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 direct
Maria Matejka wrote:
> Hello!
>
> What is the output of the following command?
>
> $ birdc show route
bird> show route table master4
Table master4:
0.0.0.0/0unicast [ospf4 00:00:52.893] E1 (150/11) [192.168.170.1]
via 192.168.170.1 on re1
192.168.89.0/27 unicast [o
Bernd Naumann wrote:
> Hi Viktor,
Hi Bernd!
>
> It's just a guess, but maybe re-enable `protocol direct` and add `interface
> "*";` so all device routes are known to bird?
I've tried enabling "protocol direct", this changes all OSPF Intra Area
routes into External routes. This is not a desirab
Hello!
What is the output of the following command?
$ birdc show route
Thanks
Maria
On 1/20/21 6:00 AM, Victor Sudakov wrote:
Dear Colleagues,
My system is full of the following messages:
bird[59366]: KRT: Error sending route 192.168.246.1/32 to kernel: File exists
bird[59366]: KRT:
Hi Viktor,
It's just a guess, but maybe re-enable `protocol direct` and add
`interface "*";` so all device routes are known to bird?
And also adding `interface "lo0" { stub yes; };` to OSPF?
Good luck,
Bernd
On 20.01.21 06:00, Victor Sudakov wrote:
Dear Colleagues,
My system is full of the
Dear Colleagues,
My system is full of the following messages:
bird[59366]: KRT: Error sending route 192.168.246.1/32 to kernel: File exists
bird[59366]: KRT: Error sending route 2001:470:ecba:2::1/128 to kernel: File
exists
bird[57195]: KRT: Error sending route 2001:470:ecba:4::1/128 to kernel:
