Hi, I've just merged a bunch of stuff into master:
- branches xroute-nlogn and rfc6126bis are now obsolete; - please track master instead. This means that master now implements the new revision of the protocol, temporarily known as RFC 6126bis. Please see https://datatracker.ietf.org/meeting/103/materials/slides-103-babel-recent-changes-to-rfc-6126bis-00.pdf RFC 6126bis is almost compatible with RFC 6126. Versions of babeld since 1.8.2 and versions of BIRD since 2.0 understand both revisions of the protocol. In order to avoid a flag day: * upgrade all of your routers to babeld 1.8.3 or later (1.8.2 is buggy) or to BIRD 2.0 or later; * only then start deploying current master. If you are not sure whether all of your routers have been upgraded, you may add the following stanza to your babeld.conf: default rfc6126-compatible true The above is true for ordinary next-hop routing. It is not true for source-specific routing, which has changed in an incompatible way. The transition model here is "ships in the night" -- version 1.8.4 speaks the old source-specific protocol and ignores the new one, while current master speaks the new source-specific protocol and ignores the old one. Please get in touch with me if you're using source-specific routing and cannot afford a flag day. Happy upgrading, -- Juliusz
pgpYLLmaAvRhT.pgp
Description: OpenPGP Digital Signature
_______________________________________________ Babel-users mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users
