> I mean I can be much more detailed when I know what to log. > ETPs are actually implemented by several different messages (usually > udp packets in broadcast). > A general "debug" log is already there, but I can manage to format it > in particular ways, specifying any detail it could be best suited for > a capturing app to make it useful in a video. > > If someone is interested we'll discuss in detail. > Perhaps a new thread in the mailing list... vasaka could you handle it?
Ok, starting a new thread. This is how I see netsukuku visualization, at least a start point: Create two rectangular networks and establish connection between them, then log events for each node until connected networks reach new stable state. Each node is a pixel, and each event is associated with colour. Question is what events are interesting to track, my first guess is ETPs, if they are divided into several events, maybe it would be good to join them, note that I am not familiar with internals, so my guess can be wrong. Also there can be two kind of visualization, one made for debug purposes and one made for a good visual, they will need different data. _______________________________________________ Netsukuku mailing list [email protected] http://lists.dyne.org/mailman/listinfo/netsukuku
