Hi,
some short pointers
On 25 Mar 2014, at 20:31, Juliano julianofischer@gmail.com wrote:
I have a few questions about these messages.
A) I do not have idea what is the meaning of ERROR IPNDAgent: join failed on wlan0; 99: setsockopt(), someone faced the same problem? Any tip will be very appreciated.
Short answer: You can ignore it. See it as a warning at best. I think some discussion about it can be found on the mailing list
B) Note that I edited a configuration file and changed the URI, but even passing my configuration file with the -c, the local node name is always dtn://OpenWrt
#here is the option edited in my config file option uri dtn://NewID
In OpenWRT configuration is a little different. All configuration in /etc/config follows a common syntax in OpenWRT and can be edited with (l)uci . You will notice that the syntax is different from the normal IBR-DTN config file on other plattforms. The OpenWRT format is not understood by the daemon
When you look at the ibrdtn init script on OpenWRT, you will see that it converts the uci configuration to a valid IBR-DTN config file, storing it in /tmp and stats ibrdtn with it. When IBR DTN is running on OpenWRT, started by the init script, you can see via 'ps ax', what the currently used config file is by looking at the -c parameter.
If you change an option OpenWRT style in /etc/config, then you must use the init script to have this change converted and applied when starting IBR-DTN. Alternatively, if you want to start ibrdtn by hand using the -c parameter, start with an IBR-DTN config file from your PC installation, or a autogenerated one from /tmp that was generated by the init magic.
3 - the ping application
What exactly is the problem? Keep in mind the default endpoint for dtnping is „echo“, e.h. dtnping dtn://mynode/echo and not „ping“ (for CBHE IPN addresses it would be 11 IIRC)
Sebastian