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

RFC 6258 Metadata Extension Block
by Maël Auzias 25 Sep '15

25 Sep '15

Hi dear list, According to some of source-code files <https://github.com/ibrdtn/ibrdtn/search?utf8=%E2%9C%93&q=extension+block&ty…>, mostly -if not all- written by Johannes Morgenroth, the security extension (RFC 6257 <https://tools.ietf.org/html/rfc6257>) block has been implemented. However I cannot find any specific code on Metadata Extension Block (RFC 6258 <https://tools.ietf.org/html/rfc6258>) that I would like to use to trigger specific processing on the application level (not on the BP daemon side). I know that a SeNDA <http://senda.uab.es/adtn> developed its own BP implementation <http://senda.uab.es/Active-DTN> to execute some code present in the metadata of the Metadata Extesion Block. Am I well searching? Did I miss something? What would be the correct way to implement the Metadata Extension Block into IBR-DTN to trigger specific application-level processing? Thanks (again) for your work and have a nice day! 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 1

MUSL compilation issue
by Brendan Heading 19 Sep '15

19 Sep '15

Hi guys, You may be aware of the musl project, a new/clean implementation of the C library focussed on strict standards compliance and security. The ibrcommon repository doesn't compile against musl. When I looked I found out that the problem was due to a call to basename(3) in ibrcommon/data/File.cpp. basename expects a char*, but the code passes a std::string.c_str() which is a const char*. The compiler refuses to build. The reason why it works on glibc is because they overload basename() by supplying a version which accepts a const char*. This is GNU extension; musl doesn't supply this due to the aforementioned focus on standards compliance. I have a patch that fixes this which I'm happy to share - is this mailing list the appropriate place to submit patches or is there a preferred mechanism ? Brendan

2 1

Double usage of routing protocol
by Maël Auzias 15 Sep '15

15 Sep '15

Hi dear list! I was wondering if it is possible to use two different routing protocol among a network. The easiest one I can think, and fastest to deploy, of is: - One dynamic routing protocol (BATMAN, spray-and-wait, prophet...) - One static routing protocol based on destination, i.e., all bundles with dtn://all/* as destination are forwarded to all nodes (and thus we deploy an epidemic routing protocol for a specific type of messages). Did anyone work on such a case? Do you have any idea or suggestion on how to do that? Is using the MEB a way to achieve this? Isn't MEB too much (or not enough) for this? Have a nice day, and thanks for further response (if any). Best regards, --- Auzias Maël auzias.net <http://www.auzias.net/en/> - vcard <http://www.auzias.net/auzias.vcf> - thesis <http://people.irisa.fr/Mael.Auzias/> *GSM: 0033 695 118 774*

3 6

[IBR-DTN] " ERROR IPNDAgent: failed "
by MATHEUS CARMO OLIVEIRA 04 Sep '15

04 Sep '15

Hello guys! I'm a graduate student in Computer Science from the Federal University of Amazonas. Sorry my English, because I'm trying to translate in parallel with Google Translate. Anyway, I'm on a research project on DTN, and I'm interested in using the IBR-DTN to assist me in the search. I'm using IBR-DTN program Raspberry Pi and BEAGLEBONE, both with Raspbian. It generates the output below: Thu Jul 16 16:43:13 2015 INFO NativeDaemon: IBR-DTN daemon 1.0.1-433 (build 916f576) Thu Jul 16 16:43:13 2015 INFO Configuration: Configuration: ibrconf Thu Jul 16 16:43:13 2015 INFO NativeDaemon: use logfile for output: /home/pi/ibrdtn.log Thu Jul 16 16:43:13 2015 INFO NativeDaemon: Parallel event processing enabled using 4 processes. Thu Jul 16 16:43:13 2015 INFO BundleCore: Local node name: dtn://node1.dtn Thu Jul 16 16:43:13 2015 INFO BundleCore: Forwarding of bundles enabled. Thu Jul 16 16:43:13 2015 NOTICE GlobalEvent: Internet connection is available. Thu Jul 16 16:43:13 2015 INFO SecurityKeyManager: initialized; path: /etc/ibrdtn/bpsec Thu Jul 16 16:43:13 2015 INFO NativeDaemon: using bundle storage in memory-only mode Thu Jul 16 16:43:13 2015 INFO NativeDaemon: API initialized using unix domain socket: /tmp/ibrdtn.sock Thu Jul 16 16:43:13 2015 INFO DiscoveryAgent: listen to [224.0.0.142]:4551 Thu Jul 16 16:43:13 2015 INFO DiscoveryAgent: listen to [ff02::142]:4551 Thu Jul 16 16:43:13 2015 INFO DHTNameService: DHT initialized on Port: 36803 with ID: Thu Jul 16 16:43:13 2015 ERROR IPNDAgent: failed to set-up multicast socket on <any>:4551: 97: cannot create socket Thu Jul 16 16:43:13 2015 INFO NativeDaemon: Using default routing extensions Thu Jul 16 16:43:14 2015 WARNING DHTNameService: bootstrapping from domain dtndht.ibr.cs.tu-bs.de failed with error: -2 Thu Jul 16 16:43:15 2015 INFO DHTNameService: DHT shut down Thu Jul 16 16:43:15 2015 NOTICE GlobalEvent: Shutdown initiated. The message "Daemon is ready" never appears. Can you help me with this! Greetings !!

4 4

IBR-DTN algorithm???
by abu fahruddin 10 Aug '15

10 Aug '15

Dear All, I just make implementation of IBR-DTN on my laptop and all already working. But I still can not get reference for IBR-DTN algorithm to compare with TCP/IP algorithm. Could you inform me some of reference paper/journal about algorithm of IBR-DTN....? thanks very much Herman Yuliandoko al Abu Fahruddin Lecture at State Polytechnic of Banyuwangi, Indonesia Herman.Yuliandoko(a)yahoo.com; abu.fahruddin(a)gmail.com; herman(a)poliwangi.ac.id

2 2

Bug Report: --badclock, clocksynchronisation
by Kevin Baron 05 Aug '15

05 Aug '15

Dear Sir or Madam, i am currently experimenting with your IBR-DTN-implementation. During my work and research i found your instruction to use AgeBlock and the argument --badclock to avoid problems with unsynchronized clocks. If you use it the way you described it "dtnd -i eth0 --badclock" you will recieve the error message "dtnd: unrecognized option '--badclock'". So somehow your documentation is wrong or the feature isn´t included as it was planed. If you check every function of IBR-DTN with the --help-argument you will never find a possibility to use a argument called --badclock. An other thing i found out is the fact, that you can abuse the built-in DT-NTP for automatic time-synchronization. If you set all knotes of the DTN to the slave mode, time-synchronization isn´t working the way it should anymore. The clocks can be very unsynchronisted, you can ping each other, and no "bundle expire" appears. In the same setting but with outcommented arguments in the .conf-file you will receive the error-message. 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 ??....". My .conf-file will be added in the appedix. The used IBR-DTN version is: IBR-DTN version: 1.0.1 (build 294b543) I hope that the described bugs are real and not just a product of my incompetence. If you have further questions, don´t hasitate to ask. I would be very thankful if you could answer my questions or problems. 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 neighbors and static # available nodes. The alternative module "epidemic" spread all bundles to # all available neighbors. Flooding works like epidemic, but do not send the # own summary vector to neighbors. 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

2 1

[ibrdtnd 1.0.1] install failing inside of buildroot
by Tom Sparks 04 Aug '15

04 Aug '15

I am in the process of submitting a patch to buildroot for ibr-dtn but I cant get ibrdtnd-1.0.1 to install PATH="/home/kobodev/buildroot/output/host/bin:/home/kobodev/buildroot/output/host/sbin:/home/kobodev/buildroot/output/host/usr/bin:/home/kobodev/buildroot/output/host/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" /usr/bin/make -j2 prefix=/home/kobodev/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr exec_prefix=/home/kobodev/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr PKG_DEVLIB_DIR=/home/kobodev/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib install -C /home/kobodev/buildroot/output/build/ibrdtnd-1.0.1/ Making install in src <snipped> /bin/mkdir -p '/home/kobodev/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/sbin' /bin/sh ../libtool --mode=install /usr/bin/install -c dtnd '/home/kobodev/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/sbin' libtool: install: /usr/bin/install -c dtnd /home/kobodev/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/sbin/dtnd Making install in etc make[4]: Nothing to be done for `install-data-am'. /bin/mkdir -p '/etc' /usr/bin/install -c -m 644 ibrdtnd.conf '/etc' /usr/bin/install: cannot create regular file ‘/etc/ibrdtnd.conf’: Permission denied make[4]: *** [install-dist_sysconfDATA] Error 1 make[3]: *** [install-am] Error 2 make[2]: *** [install-recursive] Error 1 make[1]: *** [/home/kobodev/buildroot/output/build/ibrdtnd-1.0.1/.stamp_staging_installed] Error 2 -- tom sparks x86? We ain't got no x86. We don't need no stinking x86!

1 0

Re: [ibr-dtn] Using ibrdtn stack as an external library
by Johannes Morgenroth 22 Jul '15

22 Jul '15

Hello Mathias, the tools package can be compiled standalone as long as libribcommon and libibrdtn is installed. The necessary checks and linker parameters are gathered by pkgconfig. It is good practice to use autotools to manage dependencies in new applications. In that case, the configure.ac only needs to include these lines: # check for ibrcommon library PKG_CHECK_MODULES([ibrdtn], [ibrdtn >= 1.0], [ AC_SUBST(ibrdtn_CFLAGS) AC_SUBST(ibrdtn_LIBS) ]) And this code must be included within the Makefile.am: # what flags you want to pass to the C compiler & linker AM_CPPFLAGS = @ibrdtn_CFLAGS@ AM_LDFLAGS = @ibrdtn_LIBS@ That should be sufficient to link against the ibrdtn library. Kind regards Johannes PS: I have had CC'd this mail to the mailinglist, because the topic might be interesting for others too. In order to get fast answers to your question, I recommend you to do the same for future questions. Am 22.07.2015 um 14:06 schrieb Mathias Brulatout: > Hello again ! > After a while I did end up finding the answer, which was just a mistake > by my side ... Two of my colleagues were also fooled by it ! > Don't spend time to answer that :) > > Have a nice day, > > Mathias > > 2015-07-22 11:56 GMT+02:00 Mathias Brulatout > <mathias.brulatout(a)gmail.com <mailto:mathias.brulatout@gmail.com>>: > > Hi Johannes, > > I'm basically trying to create two new applications (client/server) > using ibrdtn. > I started devloping these inside the ibrdtn stack (in the tools > folder) but it implies the compilation of the whole stack again and > I don't need that. > Moreover, I'll have some external depedencies (a JSON lib and a REST > client lib too) which may not be easy to include in the ibr > compilation chain. And it surely is not the way to go. > > Now I'm trying to use IBR stack (v1.0) as an external library ! I > guess it should work fine since libibrcommon.* and libibrdtn.* can > be found at /usr/local/include (btw the stack is properly installed > on my system for a while now) > > I have a program test.cpp (which is heavily based on dtnping and > does nothing else for now) and I compile it using this line : > g++ -I/usr/local/include/ibrcommon-1.0 > -I/usr/local/include/ibrdtn-1.0 -L/usr/local/lib -librcommon > -librdtn -o test test.cpp > > The includes are like this : > #include <ibrdtn/api/Client.h> > #include <ibrcommon/Logger.h> > > Compilation is OK (it couldn't find the headers until I added the -I > paths) but the linker fails and gives me undefined references to > each ibrdtn/ibrcommon functions used. > > Am I missing something ? > > Thanks in advance! > > Mathias > >

1 0

Re: [ibr-dtn] modifying source code , what else should be done in order to install modified version?
by Sebastian Schildt 22 Jul '15

22 Jul '15

Hi Tadewos, I am reflecting your message to the IBR-DTN mailing list, as there is a higher chance meeting knowledgeable people there. If you have not done so yet, you should join it https://mail.ibr.cs.tu-bs.de/mailman/listinfo/ibr-dtn (just searching the mailing list archives is easier with: http://news.gmane.org/gmane.network.ibrdtn ) As for your question: I do not know much about autotools and most of the time only hope they work :) But if I am not mistaken the basic idea is modifying the Makefile.am files. If you checked out the sourcecode from the git, in the top level directory should be a file autogen.sh . This will use some autoconf/automake magic to create the .in files. Those are then used by configure to create the actual make files. MfG Sebastian > On 22 Jul 2015, at 13:55, tadewos somano <tadewos85(a)gmail.com> wrote: > > Hi again , > Just a bit detail of my previous question: > I added one .cpp and one .h file within prophet. And its interaction is solely with prophet classes. > Best, > > > > Tadewos Somano > > > On Wed, Jul 22, 2015 at 1:51 PM, tadewos somano <tadewos85(a)gmail.com> wrote: > Hi Sebastian , > I have the following question regarding IBR-DTN > 1) what is the format for PRoPHET message? > 2)I modified the source code of IBR-DTN for my purpose . But I am not sure what other files(shell , .am,.in, makefile ,...) should be modified so that I can install for my purpose.Should I modify the makefile within the module only ? Or what should I do.[I am new to Autotools] > Best, > > > > Tadewos Somano > >

1 0

Re: [ibr-dtn] [IBR-DTN] " ERROR IPNDAgent: failed "
by Stephan Rottmann 19 Jul '15

19 Jul '15

Hi Matheus, again, I'm replying in public (cc: ibr-dtn(a)ibr.cs.tu-bs.de). Please do so, too, since I won't be able to reply the next two weeks... Maybe you should have at first a look at the DTN architecure. In order to transmit data, you need to define on which interfaces nodes will be able to exchange data. These are the "convergence layers". What you will need in your ibrdtnd.conf is something like this, for all embedded platforms: ----------------------- #routing: # use prophet/epidemic/flodding instead of # "default" to be able to transmit bundles from # the banana pi to the raspberry via BB routing = prophet #could be lo, to allow connections only from the loopback interface #api_interface is used to define where applications connect to #the local dtnd api_interface = any #which interfaces to use net_interfaces = wlan0 wlan1 #wireless interface wlan0: net_wlan0_type = tcp #we want to use TCP as protocol net_wlan0_interface = wlan0 #listen on interface wlan0 net_wlan0_port = 4556 #with port 4556 (default) #wireless interface wlan1: net_wlan1_type = tcp #we want to use TCP as protocol net_wlan1_interface = wlan1 #listen on interface eth0 net_wlan1_port = 4556 #with port 4556 (default) ----------------------- This part of the config file could be used on the embeded platforms, maybe you have to adjust the interfaces for the node with internet. Best regards and good luck, Stephan On Sa, 2015-07-18 at 15:07 -0300, matheus oliveira wrote: > Hello Stephan, > > > I confess I did not understand much how to define a convergence layer > for my goal. What I want is basically using the wlan0 as a point of > access and the wlan1 to connect to other nodes. That's because like > each node could provide both access points as well as connect to other > nodes. If you give to use only the wlan0 to do both better. The > connection between the nodes has to be via Wireless, with the > exception of the node connected to the Internet. It would then be > Ethernet to connect to the internet and Wifi to connect to other > nodes. > > > Node with Internet Raspberry Beaglebone > BananaPi > --------- -------- > -------- -------- > | wlan0 |<------------------- | wlan1 | | wlan0 | < > ----------- | wlan1 | > --------- -------- > -------- -------- > | -------- > --------- --------- > | Internet | | wlan0 | <-------------- | wlan1 | > | wlan0 | > -------- > --------- --------- > > > Greetings! > > > > 2015-07-18 8:02 GMT-03:00 Stephan Rottmann <rottmann(a)ibr.cs.tu-bs.de>: > > Hi Matheus, > > I'm replying public to the IBR-DTN-list since there are many > other > people reading and might have an idea, too. Thus, I also > attached the > files, too. > > Can you draw an (ASCII-Art) image of the setup (network > interfaces, ...) > of what you are trying to do, please? > > In the mail you said, you are using wlan0 for communication, > but in the > config, you defined wlan1 as the device, where you can reach > the API. > This means, that tools like dtnsend can connect to the deamon > via this > interface. > If I get it right, there are no convergence layers defined in > your > config, which are needed for communication between the nodes. > > How are the Raspberry and BeagleBone connected to each other, > via > Ethernet or WLAN? > > Best regards, > Stephan > > On Fr, 2015-07-17 at 13:39 -0300, MATHEUS CARMO OLIVEIRA > wrote: > > Thanks for answering! > > The corresponding configuration file log of the previous > email is > > ibrconf. > > > > > > I tested again using the default setting when installing the > program, > > the ibrdtnd_default.conf. The corresponding log is > ibrdtn_default.log. > > Attached are also the interfaces settings. > > > > > > I would like to stress that I am only interested in > connecting a > > Raspberry Pi to others who are running the daemon to measure > protocols > > performances, be a BEAGLEBONE or Raspberry well. Oh yeah, > I'm using > > hostapd Program wlan0 interface. This affects something? > > > > > > (Code attached). > > > > 2015-07-17 12:44 GMT-03:00 Stephan Rottmann > > <rottmann(a)ibr.cs.tu-bs.de>: > > Hi Matheus, > > > > can you please attach your configuration file? > > > > Best regards to Manaus, > > Stephan > > > > Am Freitag, den 17.07.2015, 11:46 -0300 schrieb > MATHEUS CARMO > > OLIVEIRA: > > > Hello guys! I'm a graduate student in Computer > Science from > > the > > > Federal University of Amazonas. Sorry my English, > because > > I'm trying > > > to translate in parallel with Google Translate. > Anyway, I'm > > on a > > > research project on DTN, and I'm interested in > using the > > IBR-DTN to > > > assist me in the search. I'm using IBR-DTN program > Raspberry > > Pi and > > > BEAGLEBONE, both with Raspbian. It generates the > output > > below: > > > > > > > > > Thu Jul 16 16:43:13 2015 INFO NativeDaemon: > IBR-DTN daemon > > 1.0.1-433 > > > (build 916f576) > > > Thu Jul 16 16:43:13 2015 INFO Configuration: > Configuration: > > ibrconf > > > Thu Jul 16 16:43:13 2015 INFO NativeDaemon: use > logfile for > > > output: /home/pi/ibrdtn.log > > > Thu Jul 16 16:43:13 2015 INFO NativeDaemon: > Parallel event > > processing > > > enabled using 4 processes. > > > Thu Jul 16 16:43:13 2015 INFO BundleCore: Local > node name: > > > dtn://node1.dtn > > > Thu Jul 16 16:43:13 2015 INFO BundleCore: > Forwarding of > > bundles > > > enabled. > > > Thu Jul 16 16:43:13 2015 NOTICE GlobalEvent: > Internet > > connection is > > > available. > > > Thu Jul 16 16:43:13 2015 INFO SecurityKeyManager: > > initialized; > > > path: /etc/ibrdtn/bpsec > > > Thu Jul 16 16:43:13 2015 INFO NativeDaemon: using > bundle > > storage in > > > memory-only mode > > > Thu Jul 16 16:43:13 2015 INFO NativeDaemon: API > initialized > > using unix > > > domain socket: /tmp/ibrdtn.sock > > > Thu Jul 16 16:43:13 2015 INFO DiscoveryAgent: > listen to > > > [224.0.0.142]:4551 > > > Thu Jul 16 16:43:13 2015 INFO DiscoveryAgent: > listen to > > > [ff02::142]:4551 > > > Thu Jul 16 16:43:13 2015 INFO DHTNameService: DHT > > initialized on Port: > > > 36803 with ID: > > > Thu Jul 16 16:43:13 2015 ERROR IPNDAgent: failed > to set-up > > multicast > > > socket on <any>:4551: 97: cannot create socket > > > Thu Jul 16 16:43:13 2015 INFO NativeDaemon: Using > default > > routing > > > extensions > > > Thu Jul 16 16:43:14 2015 WARNING DHTNameService: > > bootstrapping from > > > > > domain dtndht.ibr.cs.tu-bs.de failed with error: > -2 > > > Thu Jul 16 16:43:15 2015 INFO DHTNameService: DHT > shut down > > > Thu Jul 16 16:43:15 2015 NOTICE GlobalEvent: > Shutdown > > initiated. > > > > > > > > > > > > > > > The message "Daemon is ready" never appears. Can > you help me > > with > > > this! > > > > > > > > > Greetings !! > > > > > > > > > > > > > > > >

1 0