Thanks Benjamin for that tidbit. I must have misread that part of the docs. (And missed in the the archives when I searched.) Added this to my bird.conf: protocol direct { interface "*"; } Results in this : bird> show route 0.0.0.0/0 via 207.251.204.10 on eth0 [kernel1 09:56] * (10) 207.251.204.0/28 dev eth0 [direct1 09:56] * (240) bird> That much I follow, but the 172 route still doesn't appear. To clarify, I manually added that with : route add -host 172.16.100.100 dev eth0 It was my assumption that because the 172 route was manually added I needed to access it through the kernel protocol, which is why that's why I was going in that direction. Am I missing something else simple here? Thanks. On 10/19/2012 6:06 AM, Benjamin Cama wrote:
Hi,
Le jeudi 18 octobre 2012 à 16:57 -0400, Tom Beecher a écrit :
Currently, I'm unable to get BIRD to import kernel routes into the BIRD process, aside from the system default route. BIRD doesn't import device routes with the kernel protocol. You want a “direct” protocol for that; see http://bird.network.cz/?get_doc&f=bird-6.html#ss6.3
(and there are some threads about that “issue” in the ML archives too, I think)
Regards, benjamin