On Tue, 26 May 2015 12:44:06 +0100 (BST) Paul Jakma <[email protected]> wrote:
> On Tue, 26 May 2015, Paul Jakma wrote: > > > Anything sensible would probably do. This is for the link-layer > > header type? > > libpcap might have useful headers on this, maybe. It has LINKTYPE_* and DLT_*. Both are bad choices, as same #define can have different value on different platforms (at least for DLT_*). And they contain more of the "the next header is of type XXX" than "this device type X". In fact, on Linux it'll just usually say DLT_LINUX_SLL "This is linux cooked capture header next", which will contain the ARPHRD_* info. They have defines for pretty much all possiblities, as they don't want to lose info received from upstream... But yeah, it really looks like there's no simple choice for this. Re: zapi. If fixing this, we should really fix the way routes are adverticed too. Nexthops are encoded differently depending if it's zebra receiving or announcing it... They are not really AFI independent... And there's no simple way to extend the protocol without breaking ABI. To be honest, the whole protocol would need an update if we wanted to make it usable for out-of-tree users (not to speak about cross-platform) users. /Timo _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
