Notices

Well, I've installed it as per the instructions, but their instruction to start the dtn daemon with "dtnd -c /etc/dtn.conf -l info" is a bit weird, it leaves you at a "dtn%" prompt. Are you supposed to just sit at that prompt? That strikes me as very odd.

The other thing is that I'm not sure what my EID is supposed to be; is it "dtn://millenium-falcon" or "dtn://millenium-falcon.dtn"? The second one is used by the daemon when it says,

I'll see if I can get things working when I bring my tablets together tonight...

You can interact in the dtnd shell. For example:
to show your routing table and links. Try "help" to see a list off commands to get more help on. You can daemonize the dtnd like so:

and then

to get back into the dtnd shell.

A good first test is:

There is also the other apps like dtntraceroute, dtnping, dtncat, etc. If you are feeling more adventurous, you could try adding a link (in the dtnd shell) or in the dtn.conf file (follwed by a dtnd restart) to my server, as below:

then to set up a route,

Whether you ad the link and route in the shell or edit the conf and restart the daemon, you'll need to run

To bring up the link.

My nodes run the Delay Tolerant Link State Router (dtlsr) instead of the Static router, so if you switch to that in the conf file, you should get a whole bunch of new routes added and be able to dtping and dtntraceroute to my nodes.

I'll see if I can get DT-Talkie working later. My N800 is at dtn://n800.delaytolerant.net

Appending .dtn is optional. I'd leave it off if your EID is for a host with a fully resolvable name that will offer an internet routable interface, but add it if its just a host on the local domain. In practice, it doesn't really matter.

Good luck.

Uuurgh. I've noticed that DT-Talkie doesn't work with my debs. I think its down to a change to 64-bit timestamps in the XDR for the RPC API in the hg repo. Shame, as all my nodes are using the 64-bit timestamps code, and they don't work well with nodes that aren't.

Best stick with their debs. I've edited my earlier post to note this.

Well, I would charitably call DT-Talkie 'proof-of-concept'.

Constantly segfaulting, no clear way to use items in the GUI, just over all not finished in any way.

DTN seems interesting, and I see the server discovering my tablets, but the talkie app isn't there yet. And without source code, I guess it won't be.

https://garage.maemo.org/plugins/scm...?root=dttalkie

OK, someone take the source and make it into an end-user app!

Thanks for the feedback. Now the DT-Talkie version 2.1 in the project homepage is workable with the latest dtn2.6.0 in the hg repository. This time you won't face any problem mentioned above.

Bluetooth convergence layer and discovery mechanism is used in the dtnd configuration file as an example. Now TCP convergence layer with IP discovery mechanism is added which allows DT-Talkie to communication over ad-hoc wi-fi as well. Basically, DTN architecture is designed to interoperate over heterogeneous underlying link layer technologies.

Thanks for that. I've installed the latest deb, and have had some degree of success.

As I have only one N800, I set up a destination EID in DT-Talkie to point at dtn://mbpro.delaytolerant.net/dttalkie (obviously dttalkie doesn't run on my macbook pro) and recorded a voice message with DT-Talkie. DT-Talkie and DTN2 did actually deliver the bundle to mbpro, where it will sit until it expires.

There does seem to be a minor issue in that DT-Talkie seems to append .dtn/dttalkie to both the EID it registers locally, and to destination EIDs. That seems a bit odd to me, and may cause routing issues. I would have expected DT-Talkie to just append /dttalkie to the EID in the account file in order to create its own local EID, and also to the entry from the Individual or Group Contact to form the destination EID. Having said this, it may well work as is, but is probably best changed.

If anyone else fancies sending a voice message to me, you can add a link and a route via delaytolerant.net as shown in my post above). The destination EID should be dtn://n800.delaytolerant.net in the Individual Contacts field.

Then you may need to change the router type in /etc/dtn.conf to be dtlsr - I'm not entirely sure whether bundles will get routed through my DTN if you don't.

You need to press the fullscreen button to start recording, and again to stop recording and send the bundle. Note that there is nothing to show that you are actually recording a message, and if you don't stop recording, you'll fill up the file-system eventually. If you run dttalkie from the terminal, you can see the current state of recording in the output there, and the GUI does indicate when a bundle has been sent, although there is no perceptible difference in the display when sending or 2nd or subsequent bundle to the same destination, so a little bit more feedback in the GUI would be a great thing.

Note that because of the store and forward mechanism involved, you can send messages (as bundles) to nodes that aren't connected, or even to nodes that don't exist yet, and those bundles will still get delivered, as long as those destination nodes (exist and) connect into the same DTN before the bundles expire. That is, of course, unless the node storing them happens to fail.

It was little things like, "Note that there is nothing to show that you are actually recording a message, and if you don't stop recording, you'll fill up the file-system eventually" that made me say that DT-Talkie is proof-of-concept level still. There are no cues to tell you what button to push in the app itself, and no cues to show that anything is being done...

EDIT: Here are some more things that make this a rough-edged app:

There is also no way to delete contacts, and contacts that are discovered by your tablet are not added to your list or shown in the GUI in any way...