Import directly connected routes

Damien Clabaut damien.clabaut at corp.ovh.com
Mon May 8 21:45:17 CEST 2017


Hello Ondrej,

Thank you for your answer.

I did not manage to do it with "device", but "direct" works:

protocol direct direct_numa0 {
   table numa0;
   interface "eth4.800", "eth4.801";
}

Thanks :)


On 08/05/17 03:16 PM, Ondrej Zajicek wrote:
> On Mon, May 08, 2017 at 02:51:55PM -0400, Damien Clabaut wrote:
>> Hello,
>>
>> I have an issue with latest stable Bird (1.6.3) on Debian8.
>>
>> I have a bunch of directly connected networks, with route in main routing
>> table:
>>
>> # ip route show
>> default via 10.21.136.126 dev eth0
>> 10.21.136.0/25 dev eth0  proto kernel  scope link  src 10.21.136.19
>> 192.168.1.0/31 dev eth4.800  proto kernel  scope link  src 192.168.1.1
>> 192.168.1.2/31 dev eth4.801  proto kernel  scope link  src 192.168.1.3
>> 192.168.1.4/31 dev eth4.802  proto kernel  scope link  src 192.168.1.5
>> 192.168.1.6/31 dev eth4.803  proto kernel  scope link  src 192.168.1.7
> ...
>
>> But only the default (static) route is imported:
>>
>> bird> show route table default1
>> 0.0.0.0/0          via 10.21.136.126 on eth0 [kernel_default 20:32:40] *
>> (10)
>>
>> Is there any way I can import them ?
> Hello
>
> Kernel protocol in 'learn' mode does not learn 'native' kernel routes,
> just routes added by other daemons/tools (like the default route).
>
> But 'device' protocol could do what you want.
>

-- 
Damien Clabaut
R&D vRouter
ovh.qc.ca



More information about the Bird-users mailing list