i chmod 777 the /tmp/blob and got no error anymore :)

but the problem is i still cannot dtnping, it always say timeout when i try to dtnping.

i will try to explain my configuration

1. i have nodeA, nodeB and nodeC

2. when i did not use routing nodeA-nodeB-nodeC can dtnping each other (with adhoc network)

3. i want to dtnping from nodeA to nodeC via nodeB

4. so i have this configuration (as you suggest before)

nodeA (ubuntu) :

limit_blocksize = 1.5G

limit_predated_timestamp = 604800

limit_lifetime = 604800

api_interface = any

fragmentation =yes

blob_path = /tmp/blob/

storage_path = /home/trie/ibrdtn/bundles

storage = default

limit_storage = 2.5G

#dht_enabled = yes

routing = none

routing_forwarding = yes

route1 = dtn://nodeC.dtn/* dtn://nodeB.dtn

time_reference = no

time_synchronize = yes

time_discovery_announcements = yes

nodeB (raspberry pi) :

limit_blocksize = 1.5G

limit_predated_timestamp = 604800

limit_lifetime = 604800

api_interface = any

fragmentation =yes

blob_path = /tmp/blob/

storage_path = /home/trie/ibrdtn/bundles

storage = default

limit_storage = 2.5G

#dht_enabled = yes

routing = default

routing_forwarding = yes

time_reference = yes
time_discovery_announcements = yes

nodeC (ubuntu) :

limit_blocksize = 1.5G

limit_predated_timestamp = 604800

limit_lifetime = 604800

api_interface = any

fragmentation =yes

blob_path = /tmp/blob/

storage_path = /home/trie/ibrdtn/bundles

storage = default

limit_storage = 2.5G

#dht_enabled = yes

routing = default

routing_forwarding = yes

route1 = dtn://nodeA.dtn/* dtn://nodeB.dtn

time_reference = no

time_synchronize = yes

time_discovery_announcements = yes

5. and i start ibrdtn using "dtnd -i wlan0 -c /etc/ibrdtn/ibrdtnd.conf -c"

6. when i try this from nodeA : dtnping dtn://nodeB/echo it still got 'timeout' and vice versa

7. did i miss something in my configuration ?

thanks for helping me to fix my problem :)

This means that the directory is owned by user root and only writable
for user root. If you are launching `dtnd` as any other user, there will
be insufficient permission. You can delete the directory (as root) and
re-create it as a user. Another option could be to use chown/chgrp or
set mode 777 for the directory...

If you are starting as root, then you can ignore this mail since I have
no idea what could be wrong...