Hello Mr. Baron,
see my comments below inline...
Am 04.08.2015 um 14:00 schrieb Kevin Baron:
During my work and research i found your instruction to use AgeBlock and the argument --badclock to avoid problems with unsynchronized clocks. If you use it the way you described it "dtnd -i eth0 --badclock" you will recieve the error message "dtnd: unrecognized option '--badclock'". So somehow your documentation is wrong or the feature isn´t included as it was planed. If you check every function of IBR-DTN with the --help-argument you will never find a possibility to use a argument called --badclock.
That is correct. At least since version 1.0 this option is no longer present. Instead a node configured with "time_reference = no" which has not been synchronized yet will act as if it was configured with "--badclock" before.
An other thing i found out is the fact, that you can abuse the built-in DT-NTP for automatic time-synchronization. If you set all knotes of the DTN to the slave mode, time-synchronization isn´t working the way it should anymore. The clocks can be very unsynchronisted, you can ping each other, and no "bundle expire" appears. In the same setting but with outcommented arguments in the .conf-file you will receive the error-message.
That is also correct. If no node in the network knows about the correct time, there is no way to figure out when bundles should be purged. The time synchronization approach always requires at least one master in the network. The corresponding paper [1] will explain the approach in more detail.
[1] https://www.ibr.cs.tu-bs.de/bib/xml/Morgenroth:Chants:2012.html
Last but not least there are some linking mistakes in the pdf-file for the api. For example on page 5 "...The available data formats are described in section ??....".
Oh, yes. You are right. Patches are welcome if you want to contribute a fix for that issue.
My .conf-file will be added in the appedix.
If you want to enable time synchronization, you should configure "time_discovery_announcements" to "yes" on slave nodes too or leave it commented out. Only that way, synchronization will be done across multiple hops.
Kind regards, Johannes Morgenroth