On Tue, May 03, 2016 at 01:37:37PM +0200, Toke Høiland-Jørgensen wrote:
I thought you were also exporting the router-id as an attribute, since it is shown in "show route all": It is exported, but as an opaque blob as far as the Bird core is concerned.
Would it make sense to export the router ID? It would allow to filter routes based on the originating router (babeld allows that, but I have no idea whether it's actually used by somebody).
It would, I guess, but that would require teaching the core about 64-bit router IDs, and the parser would need to learn a syntax for them. So it's not trivial, unfortunately, and so I've punted on that for now.
No worries then, as I said, it's probably not used much with babeld (I certainly don't use it).
Can you mention that it needs "protocol direct" to work? Maybe just add this at the beginning of the example:
protocol direct { interface "*"; }
Well I figured that is already in the example config file shipped with Bird, and that most people would just use that as a starting point...
Hmm, on Debian, it isn't. I think it couldn't hurt to at least mention that it is needed. Baptiste