Re: [Babel-users] babel topologie

A already connected to the socket for the frontend, but afaik i gives me just one worldview. Because babel itself does not know the complete topology. More precisely, every Babel node knows which are its neighbours. It cannot distinguish between a second order and a third order neighbour --

Re: [Babel-users] babel topologie

Juliusz Chroboczek juliusz.chroboc...@pps.jussieu.fr writes: Because babel itself does not know the complete topology. What I have considered doing at some point (when we get around to rewriting BabelDraw) would be to have the controller simultaneously connected to multiple Babel nodes, and

Re: [Babel-users] babel topologie

Could the controller build up the topology via route request messages (section 3.4.10 of the rfc) unicast with a prefix of 0, instead? In principle, it could. But consider what I say in Section 3 of the draft: A Babel packet MUST be silently ignored unless [...] its source port is the