- Ibr-dtn - lists.ibr.cs.tu-bs.de

WARNING
by Leonardo 21 Nov '15

21 Nov '15

Hello, after having followed the procedure to install ibr-dtn source, I can not do dtnping between host1 and host2. The console show me the following message: Warning BundleFilter: bundle rejected due to invalid authentication… Someone could help me to fix this problem please?

3 2

./autogen.sh error
by Maël Auzias 20 Nov '15

20 Nov '15

Hi everyone! Wanting to work on the bleeding edge I went accross an error just after a git clone https://github.com/ibrdtn/ibrdtn.git && cd ibrdtn/ibrcommon/ && ./autogen.sh The error: ## enter directory ibrcommon ## ## run autogen.sh script ## set version to 1.0.1 configure.ac:49: error: possibly undefined macro: AC_SUBST If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:72: error: possibly undefined macro: AC_DEFINE configure.ac:77: error: possibly undefined macro: AC_CHECK_LIB configure.ac:97: error: possibly undefined macro: AC_MSG_ERROR configure.ac:200: error: possibly undefined macro: AC_MSG_WARN autoreconf: /usr/bin/autoconf failed with exit status: 1 Here is my uname -a output: Linux hh 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u4~bpo70+1 (2015-09-22) x86_64 GNU/Linux Did anyone go through this error already? You can find the output of dpkg -l in the attachment. Have a nice day! github issue related: https://github.com/ibrdtn/ibrdtn/issues/180 Best regards, --- Auzias Maël auzias.net <https://www.auzias.net/en/> - vcard <https://www.auzias.net/auzias.vcf> - thesis <http://people.irisa.fr/Mael.Auzias/> *GSM: 0033 695 118 774*

1 0

Only using IPv4 for dgram:udp
by Timo Wischer 06 Nov '15

06 Nov '15

Hi guys, I am looking for a way to run the dgram:udp cl only for IPv4. I want to test the throughput of IBR-DTN on an Raspberry Pi over IPv4, because I want to compare this implementation with my implementation. I have tried the following: Removed the IPv6 address from the discovery configuration discovery_address = 224.0.0.142 # ff02::142 But the bundles will send over IPv6 anyway. Switch off IPv6 support with $ echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 But then I get the following error message: Wed Oct 28 16:20:26 2015 ERROR ApiServer: Cannot bind to socket with address [::1]:4550 And no dtn application can connect to the daemon. If have seen that the multicast addresses are hard wired in https://github.com/ibrdtn/ibrdtn/blob/master/ibrdtn/daemon/src/net/UDPDatag… Is there a possibility for only using IPv4 without recompiling IBR-DTN? Best regards, Timo

3 2

Patch: dtnping
by Kevin Baron 06 Nov '15

06 Nov '15

To whom it might concern, while I was playing around with dtnping I found out, that you are not able to close dtnping in case you called it with the option --nowait. Neither helped CTRL+C nor a kill command. I looked at the code for the case without --nowait, and found a helping piece for the --nowait case. Now you are able to interrupt dtnping even if you called it with --nowait. Hope my solution, which is in the attachment, is okay. With best regards, Kevin Baron

1 0

Patch: dtninbox
by Kevin Baron 06 Nov '15

06 Nov '15

To whom it might concern, don't really know how to contribute with a little patch so I used the git option to implement patches to a mailing list. As I already mentioned there is a little bug in the function dtninbox with the option --quiet. It wasn't working. I fixed this and now everything should work as intended. The patch is in the attachment. Best regards, Kevin Baron

1 0

Patch: dtnconvert
by Kevin Baron 06 Nov '15

06 Nov '15

To whom it might concern, again I contribute a little patch to the IBR-DTN this time concerning dtnconvert. In case you called it with -h the help was printed twice. With this patch implemented the help should only get printed once. See the attachment for the patch. Best regards, Kevin Baron

1 0

Question: Bundle version and --workdir option
by Kevin Baron 06 Nov '15

06 Nov '15

To whom it might concern, I have two little questions and hope you can help me. My first question is about bundle versions. If I start the daemon with -d 10 and check the messages I found DEBUG.10 BinaryStreamClient: Bundle version differ from ours. DEBUG.10 BinaryStreamClient: unexpected API error! Conditional has been unblocked in the case of receiving bundles from dtnsend or the last ping of a series of pings. I checked the version in Serializer.cpp and saw that it is, despite of the last bundle, always 6 (as it is defined in dtn::data::BUNDLE_VERSION) and at the last bundle only 0. The stream _stream.get(version); isn't reading any version from the bundle, the version stays 0. Is it intended to be so? If yes why is it the way it is? My second question refers to the option -w|--workdir in the function dtninbox and dtnoutbox. I don't really understand how this is intended to work. Can someone explain me what I can accomplish with this feature? Thank you in advance. Best regards, Kevin Baron

1 0

[API] Multi-destinations bundle and flags
by Maël Auzias 05 Oct '15

05 Oct '15

Hi everyone, Looking through the API <http://trac.ibr.cs.tu-bs.de/project-cm-2012-ibrdtn/wiki/docs/api> documentation <https://www.ibr.cs.tu-bs.de/projects/ibr-dtn/apidoc/0.12/api.pdf> I could not find how to send a bundle to 2+ destinations. Should I just typed the following during my bundle put plain or will it overwrite the first one? [..] Destination: dtn://dest1/01 Destination: dtn://all/groupEID-02 [..] What about the flag if one destination is a singleton and the other is a group EID? Sorry for asking "should I do this" instead of trying it, so far I just did not had the time to test it but it's planned ;) and my question about the flags remains anyway. Have a nice day, and thanks again for all your work! Best regards, --- Auzias Maël auzias.net <https://www.auzias.net/en/> - vcard <https://www.auzias.net/auzias.vcf> - thesis <http://people.irisa.fr/Mael.Auzias/> *GSM: 0033 695 118 774*

2 2

RFC for datagram CL for UDP-CL
by Timo Wischer 29 Sep '15

29 Sep '15

Hello, I am looking for a specification or a RFC for the datagram convergence layer which can be used with UDP- and LoWPAN-CL. Where could I find a specification or is it an in-house development and there does not exist any RFC? Is it correct that only using the UDP-CL without dgram is not reliable, too? Greetings Timo Wischer

1 0

Bugreport: dtninbox, dtnrecv, dtnconvert, API And a little question
by Kevin Baron 25 Sep '15

25 Sep '15

Dear Sir or Madam, I still playing around with the IBR-DTN and found out some things that I would like to contribute. I hope this is helping. I got some code from GitHub under ibrdtn/ibrdtn/tools/src/*. First I will refer to ibrdtn/ibrdtn/tools/src/dtninbox.cpp. In the function read_configuration is a switch-case which controls the passed arguments. But there is no test for the argument --quiet. If you start dtninbox with -q or --quiet the script just instantly stops. I guess the missing part just looks like: ... case 'q': _conf_quiet = true; break; ... I guess this should fix the problem. Hope this is right. Further I gone cite Mr.Morgenroth and myself from my last post: > > Last but not least there are some linking mistakes in the pdf-file for > > the api. For example on page 5 "...The available data formats are > > described in section ??....". > > Oh, yes. You are right. Patches are welcome if you want to contribute a > fix for that issue. I looked at it. Just compile it once again with LaTex and it will be all okay. There are no changes in the code needed. I think there is also a bug in the dtnrecv-function. If you say, that you want to receive more then one bundle with --count x, x>1, every bundle will just get printed once. If you start dtnrecv without --count x, x>1, or with --count x, x=1, it often happens that the same bundle gets presented at the console more then once. But if you start it with for example --count 3 the first two bundles are only received once, the third bundle gets presented during this dtnrecv setup but if you start a new dtnrecv just after you closed the last one you will receive the third bundle again. It seems as if the last received bundle didn't get deleted or something like that. If I start dtnrecv without count I can receive the same bundle up to four times. With --count x only the last bundle twice. But if you set the lifetime of a bundle in dtnsend to 1 second the problem disappears. So there must be more then one bundle. I tested this with every routing algorithm and it was always the same. But I haven't found a solution in the code yet. Maybe you have an idea. I further have a question to the registration list command in the API. I am registered as dtn://piOne. If I use neighbour list on an other device the shown name is dtn://piOne but if I look at the registration list there is some thing like dtn://piOne/[[:alpha::]+. Is this right? Why does it look like it does? A little bug I found is in dtnconvert. If you type in dtnconvert -h the help text is printed twice. I guess is has to do with the switch case and following code. There is a case 'h' for the -h argument which prints the help. But there is the variable working_mode isn't changed, so it stays at 0, as it was since the beginning (in case 'r' or 'c' its changed) and so the following if (working_mode == 0) { print_help(); return -1; } prints the help again. Also checked it with echo $? and the exit code isn't as expected for a good running program / command zero, it is in my case always 255. An other thing I saw isn't just a feature to make the program more user-friendly. In the help for dtnping (dtnping -h) there is the option --size, but no further description how to use it. It would be create if there would be something like --size <bytes>. Just to make it more intuitive. My .conf-file will be added in the appendix. The used IBR-DTN version is: IBR-DTN version: 1.0.1 (build 294b543) Thanking you in advance. Yours sincerely, Kevin Baron ------------------------ .conf-file: ##################################### # IBR-DTN daemon # ##################################### # # the local eid of the dtn node # default is the hostname # local_uri = dtn://piOne # # routing strategy # # values: default | epidemic | flooding | prophet | none # # In the "default" the daemon only delivers bundles to neighbours and static # available nodes. The alternative module "epidemic" spread all bundles to # all available neighbours. Flooding works like epidemic, but do not send the # own summary vector to neighbours. Prophet forwards based on the probability # to encounter other nodes (see RFC 6693). # routing = flooding # # forward bundles to other nodes (yes/no) # routing_forwarding = yes # # set to yes if this node is connected to a high precision time reference # like GPS, DCF77, NTP, etc. # # Time-slave #time_reference = no #time_synchronize = yes # Time-master #time_reference = yes #time_discovery_announcements = yes ##################################### # DHTNameService settings # ##################################### # # Enable the DHT, if it was compiled # Default is no # dht_enabled = yes # # Set the udp port, the DHT should working on # Default is 9999 # If Port is 0, a random Port will be chosen for each run # dht_port = 9999 # # Here you can choose a static DHT ID, which is very common # Default is none -> a random ID per run will be generated # dht_id = DHTpiOne # # Enables DHT on IPv6 socket # Default is yes # dht_enable_ipv6 = no # # Enable DNS Bootstrapping for the DHT # dht_bootstrapping = no

1 0