I have the following configuration (testing for now): ... protocol direct { table testtable; interface "gre1"; } protocol kernel { table testtable; kernel table 200; export all; } /* Some other ospf configuration */ ... Then, we get: # birdc BIRD 1.0.5 ready. bird> show route table testtable 192.168.0.0/30 dev gre1 [direct1 18:36] (240) 192.168.4.0/24 via 192.168.1.2 on gre2 [testOSPF 18:46] I (150/30) bird> Great, that is what we want. On the other end: # ip route list table 200 192.168.4.0/24 via 192.168.1.2 dev gre1 proto bird # The ospf stuff has been exported, not the rest... Any reason? Guillaume.
Hello!
The ospf stuff has been exported, not the rest... Any reason?
Device routes are not exported, because the kernel handles them automatically and we don't want to interfere with it. If you _really_ want to export them, you can modify the krt_capable function in sysdep/linux/netlink/netlink.c. Have a nice fortnight -- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth COBOL -- Completely Outdated, Badly Overused Language
participants (2)
-
Guillaume Marcais -
Martin Mares