For example, a route reflector's job is to reflect routes between its client peers. Often a route reflector is not on the data path itself, and so does not need to program those routes into its own box's kernel.
On Fri, Mar 20, 2020 at 9:50 AM Alexander Zubkov <gr...@qrator.net> wrote: > Hi, > > It depends on what you are trying to achieve. Of course bird can > function without an instance of the kernel protocol. But in that case > it can not push any routes into the routing table of your os. If you > need those routes only to spread them for some other reasons then it > is probable that you do not need to use the kernel protocol. > > On Fri, Mar 20, 2020 at 9:07 AM Irene Lalioti <irene.lali...@restena.lu> > wrote: > > > > Hello guys! > > > > I would like to ask you what would you think the better practice would > > be: Can we remove totally the kernel protocol? > > > > I thought no but we tested it and it works. Now we have on our linuxbox > > set the static routes outside bird daemon, where we specify that the > > caches we have are behind the border routers. > > > > Would it be safe to totally remove this from the system configs and only > > use the Direct protocol as we said yesterday, and rely on the direct > > protocol that it learns the connected network and the multihop of the > > caches which reside behind the border routers? > > > > Thanks a lot!! > > > > Irene > > > > -- > > Irene Lalioti > > Network Engineer > > Fondation RESTENA > > 2, avenue de l'Université > > L-4365 Esch/Alzette > > > > Tel: +352 424409 1 > > Fax: +352 422473 > > > >
