The second originator field of a vis client update packet looks a bit odd in wireshark. Sven :)? (have a look at the attached cap-file for an example)
I was also wondering about renaming this field maybe, in the beginning I got quite confused by seeing two identical originator fields in most vis packets. Maybe it should be renamed to previous sender or forwarding originator instead?
Cheers, Linus
Linus Lüssing wrote:
The second originator field of a vis client update packet looks a bit odd in wireshark. Sven :)? (have a look at the attached cap-file for an example)
Thanks. This is fixed in v2009.2.0-2-g6f93aff
I was also wondering about renaming this field maybe, in the beginning I got quite confused by seeing two identical originator fields in most vis packets. Maybe it should be renamed to previous sender or forwarding originator instead?
It is changed in v2009.2.0-3-g33f16bd
Nice catch and bug report :)
Best regards, Sven
b.a.t.m.a.n@lists.open-mesh.org
-
Linus Lüssing -
Sven Eckelmann