> We are developing an application on top of Babel. In this application, we > have to decide how to communicate with one hop and two hop nodes, and > treat these connections differently.
Babel (the protocol) does not have this information. If the announced metric of a route is 0, then you can be pretty confident that it is being announced by a neighbour. If the announced metric is not 0, then there's nothing that can be said -- it could be announced by a non-neighbouring node, or it could be the effect of route filtering increasing the metric. > Is there a simple way of detecting one-hop and two-hop nodes? You would need to define an extension. For example, you could have nodes announce their router-id, or you could carry the hop count in a sub-TLV of the update TLV. -- Juliusz _______________________________________________ Babel-users mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users
