Re: Bird does not include next hop information in babel retractions, while babeld requires them

Fabian Bläse writes: > Hi, > > when using both bird and babeld in our babel network, babeld regularly > complains about malformed packets. This happens when bird sends route > retractions without including router-id and next-hop TLVs first. > According to rfc6126 the router-id is not used for ret

Bird does not include next hop information in babel retractions, while babeld requires them

Hi, when using both bird and babeld in our babel network, babeld regularly complains about malformed packets. This happens when bird sends route retractions without including router-id and next-hop TLVs first. According to rfc6126 the router-id is not used for retractions. The resulting error