On Wed, Feb 23, 2011 at 2:29 PM, <[email protected]> wrote: >> 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 >
So, as to recap the main point of the thread, is there someone interested in taking this duty? I.e. 1. study the messages that are exchanged between nodes when 2 networks meet and merge; 2. come up with an idea of what informations could be useful to deliver and how in a video (or 2 videos for different audience); 3. tell us what info the daemon should log and the format; 4. make the video. --Luca _______________________________________________ Netsukuku mailing list [email protected] http://lists.dyne.org/mailman/listinfo/netsukuku
