Hello all,
I was trying to get some epidemic routing working using 0.4.4. However, I always see in the logs that the bundles expire, irrespective of when they were sent. Is there any config parameter that controls the epidemic routing timeout? Has there been any bugfixes w.r.t this in version 0.6?
Harsha
Hi, as far as I can see, some of the Epidemic Routing Control messages have a timeout of 60 sec., so for Epidemic routing to work the nodes should have their clocks synchronized with an error of less than a minute. This is not configurable at the moment. Johannes might have more insights or ideas for workarounds, but he is not available this week. MfG Sebastian
Harsha Chenji cjkernel@gmail.com hat am 13. März 2011 um 21:19 geschrieben:
Hello all,
I was trying to get some epidemic routing working using 0.4.4. However, I always see in the logs that the bundles expire, irrespective of when they were sent. Is there any config parameter that controls the epidemic routing timeout? Has there been any bugfixes w.r.t this in version 0.6?
Harsha
-- !! This message is brought to you via the `ibr-dtn' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to ibr-dtn-request@ibr.cs.tu-bs.de !! or look at https://mail.ibr.cs.tu-bs.de/mailman/listinfo/ibr-dtn.
Hello Harsha,
if you have trouble with clock syncronisation you could try the "--badclock" parameter. This enables relative timing and expiration using the bundle age block.
Johannes
Am 13.03.2011 21:19, schrieb Harsha Chenji:
I was trying to get some epidemic routing working using 0.4.4. However, I always see in the logs that the bundles expire, irrespective of when they were sent. Is there any config parameter that controls the epidemic routing timeout? Has there been any bugfixes w.r.t this in version 0.6?
participants (3)
-
Harsha Chenji -
Johannes Morgenroth -
Sebastian Schildt