On 08/22/2018 04:34 PM, Grant Taylor wrote:
I'll do some more reading on what "learn" does (not) do in the kernel protocol context.
So it looks like learn is a way for BIRD to detect changes to the routing table /if/ it can identify the source of the change.
I think that Linux provides the information about the source.
It sounds like I will likely need to use a pipe to "leak" (is that the proper term?) the default route from kernel table 253 into RIP and filter the default out so that it doesn't get populated into kernel routing table 254.
After (re)reading the Pipe documentation (https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.8) it seems as if I'm going to logically have three different RIBs (if that's the proper term).
One for each kernel routing table (253 & 254) and the view that RIP has.I think that I will need to import from the default_rib (253) into RIP -and- filter said default from RIP so that it doesn't get into the main_rib (254).
Or am I going to need a 3rd table inside of BIRD which does the following: - Imports all from main_rib (254) - Exports all to main_rib (254) EXCEPT the default. - Imports all from default_rib (253) - Exports none to default_rib (253) Please stop me if that's not the track that I should be going down. -- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
