Hello,
Thank you for your information. The idea is that dtnd may use IP routing information obtained from outside. For example, when some IP routing protocol gathers routing information, it could be reflected to the DTN neighbor list. Do you catch my idea?
Thanks, Yoshimi Fujii
2012/9/20 Johannes Morgenroth morgenro@ibr.cs.tu-bs.de:
Hello,
there are already methods to add discovered connection to the daemon via the API. There methods are part of the ManageClient:
addLink - Add an additionally IP address to listen on. removeLink - Remove an previously added IP address to listen on.
addConnection - Add connection data for a specific node. removeConnection - Remove previously added connection data for a specific node.
The two latter methods allow to add/remove new discovered nodes to the neighbor list of the daemon.
Can you tell me more details of your work. What kind of discovery do you implement? Do you plan to contribute your work back to the community?
Kind regards, Johannes
Am 20.09.2012 07:53, schrieb Yoshimi Fujii:
Hello,
I didn't expect that we can't use Android NDK for building dtnd. However, we may need to build it from source code.
What we want to do is to modify dtnd to add some experimental feature for our research. That is, to manipulate its neighbor list from outside the daemon. I don't think this can be done with it's API from application.
I greatly appreciate your help.
Yoshimi Fujii
-- Johannes Morgenroth Institut fuer Betriebssysteme und Rechnerverbund Tel.: +49-531-391-3249 Muehlenpfordtstrasse 23 Fax.: +49-531-391-5936 TU Braunschweig D-38106 Braunschweig