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

Bluetooth convergence layer support?
by Xiaoyang Zhu 23 Feb '16

23 Feb '16

Dear All, Recently, we launched a project to develop a set of the security interfaces using secret sharing method to enhance the security of DTN based on IBR-DTN. Since the project may use the Bluetooth as the communication protocol, we want to figure out whether there is any ongoing group developing the Bluetooth convergence layer adapter? Xiaoyang Zhu INL, INSA de Lyon Bâtiment Blaise Pascal 20, Avenue Albert Einstein 69621 Villeurbanne Cedex

4 3

Beacon issues when using IBR-DTN on Android
by Gwilherm Baudic 20 Feb '16

20 Feb '16

Hello everyone, I am currently experimenting with the IBR-DTN application for Android in order to get familiar with it. More specifically, my setup is as follows: * 2 Android smartphones (Android 4.1 and 6.1.0) running IBR-DTN from the Play store (app 1.0 dtnd 1.0.1 build 570f2b9) and Whisper 1.6, also downloaded from the Play store. Smartphones do not have any 3G/4G connection enabled and only have Wifi available for the experiment. * 1 Wifi access point to which both smartphones are connected. What I am trying to achieve is very simply, as a first step, to check if both phones can see each others as neighbours (in the Neighbor list of IBR-DTN), and try to transfer some Whisper text messages between them. The settings on IBR-DTN are: Epidemic routing Discovery policy always on Cloud connect Off Wifi direct Off Security is deactivated Time synchronization is also deactivated Log parameters are set to Debugging with verbosity level 99 and I chose to save the text files as well for further inspection. I experimented with several access points (ISP router at home, campus Wifi, dedicated router on my desk in the lab). From the observations I made from the phones and the log files, it seems that beacons are getting produced (and exchanged) only when the access point has a connection to the Internet. I feel like I am missing something here, and that the actual reason for the lack of beacons is totally unrelated to the Internet connectivity. Does anyone have any idea on this? On a side note, the naming scheme for the log files looks rather strange to me. For example, for a log file starting on February 15th, 2016 at 16:15:02, the resulting filename I obtain is 2016115154152 while I would expect something closer to 20160215161502. With the changing length, the current naming scheme has the drawback of breaking the alphabetical order, thus making it really inconvenient to work with lots of files with different start dates. Best regards, Gwilherm Baudic PhD student, ISAE-SUPAERO

3 3

Re: [ibr-dtn] Missing link on IBR-DTN site
by Kris Grala 05 Feb '16

05 Feb '16

Thank you Johannes... K‎ris From: morgenroth(a)ibr.cs.tu-bs.de Sent: Friday, February 5, 2016 11:18 AM To: Kris Grala; ibr-dtn(a)ibr.cs.tu-bs.de Subject: AW: [ibr-dtn] Missing link on IBR-DTN site Hello Kris, the page has been merged into a generic page for ARM based platforms. https://trac.ibr.cs.tu-bs.de/project-cm-2012-ibrdtn/wiki/platform/debian-arm Kind regards, Johannes Morgenroth Von: Ibr-dtn [mailto:ibr-dtn-bounces@ibr.cs.tu-bs.de] Im Auftrag von Kris Grala Gesendet: Donnerstag, 4. Februar 2016 23:03 An: ibr-dtn(a)ibr.cs.tu-bs.de Betreff: [ibr-dtn] Missing link on IBR-DTN site Hi, I have noticed that: The link in IBR-DTN (platform/raspberrypi) is not there anymore. Can you re-post the link so the link from https://www.ibr.cs.tu-bs.de/trac/ibr-dt ... aspberrypi will point to the correct location? Currently the link to: https://trac.ibr.cs.tu-bs.de/project-cm ... aspberrypi<https://trac.ibr.cs.tu-bs.de/project-cm-2012-ibrdtn/wiki/platform/raspberry…> has this error: Track Error: Page platform/raspberrypi not found Thank you.

1 0

Missing link on IBR-DTN site
by Kris Grala 05 Feb '16

05 Feb '16

Hi, I have noticed that: The link in IBR-DTN (platform/raspberrypi) is not there anymore. Can you re-post the link so the link from https://www.ibr.cs.tu-bs.de/trac/ibr-dt ... aspberrypi will point to the correct location? Currently the link to: https://trac.ibr.cs.tu-bs.de/project-cm ... aspberrypi<https://trac.ibr.cs.tu-bs.de/project-cm-2012-ibrdtn/wiki/platform/raspberry…> has this error: Track Error: Page platform/raspberrypi not found Thank you.

3 2

UDP Convergence Layer Ignored
by Nik Ansell 02 Feb '16

02 Feb '16

Thank you for the clarification Johannes. Kind Regards, Nik > > Message: 2 > Date: Sun, 31 Jan 2016 10:36:37 +0100 > From: <morgenroth(a)ibr.cs.tu-bs.de> > To: <nikansell00(a)gmail.com> > Cc: ibr-dtn(a)ibr.cs.tu-bs.de > Subject: Re: [ibr-dtn] UDP Convergence Layer Ignored > Message-ID: <020001d15c0a$e1eae0f0$a5c0a2d0$(a)ibr.cs.tu-bs.de> > Content-Type: text/plain; charset="utf-8" > > Just to clarify the confusion. > > The parameter “-i <interface>” is a short-cut for a TCP Convergence Layer > entry bound on that interface. It just adds an entry to the existing ones > within the configuration. > > > > Kind regards, > > Johannes Morgenroth > > > > > > Von: Ibr-dtn [mailto:ibr-dtn-bounces@ibr.cs.tu-bs.de] Im Auftrag von Nik > Ansell > Gesendet: Montag, 18. Januar 2016 15:11 > An: Stephan Rottmann <rottmann(a)ibr.cs.tu-bs.de> > Cc: ibr-dtn(a)ibr.cs.tu-bs.de > Betreff: Re: [ibr-dtn] UDP Convergence Layer Ignored > > > > Yes, this fixed it. > > > > The -i <interface> dtnd startup option was conflicting with the interface > definition in the conf file. > > Starting dtnd without the -i option worked fine. > > > > > Kind Regards, > Nik > > > > On Mon, Jan 18, 2016 at 4:02 PM, Nik Ansell <nikansell00(a)gmail.com > <mailto:nikansell00@gmail.com> > wrote: > > Hi Stephan, > > > > I have just tried again on a brand new installation and observed something > strange, hopefully I have found a fix to the problem. > > I tried to troubleshoot in stages, this is what I did: > > > > 1. Start dtnd with default conf file - Started OK with no convergence layer > > 2. Add custom conf file (below conf1), but do not specify the correct > interface name, also do not start dtnd with -i option - Started OK with UDP > Convergence layer (Datagram ConvergenceLayer (UDP) added on eth0:4556) > > 3. Add custom conf file (below conf2) with correct interface name and use > -i option - Fails: (TCP ConvergenceLayer added on eno16777736:4556) > > 4. Revert back to step 2 - Started OK with UDP Convergence layer (Datagram > ConvergenceLayer (UDP) added on eth0:4556) > > 5. Add custom conf file (below conf2) with correct interface name and > _do_not_ use -i dtnd startup option - Works: (Datagram ConvergenceLayer > (UDP) added on eno16777736:4556) > > > > I think perhaps the net_eth_interface option in the conf file and the -i > dtnd startup option may be conflicting with each other. It appears to start > OK using only the net_eth_interface option in the conf file. > > When I am logged on to my test bed in a few hours I will try some data > transfers and report back. > > > > Kind Regards, > > Nik > > > > Conf1: > > local_uri = dtn://rx > > net_eth_type = dgram:udp > > #net_internet = eth0 > > net_eth_interface = eth0 > > net_eth_port = 4556 > > net_interfaces = eth > > > > # Create a route to tx > > static1_uri = dtn://tx > > static1_port = 4556 > > static1_address = 10.0.0.1 > > static1_proto = dgram:udp > > static1_immediately = yes # connect immediately to this node > > #static1_global = no # this node is only reachable with internet access > > > > Conf2: > > local_uri = dtn://rx > > net_eth_type = dgram:udp > > #net_internet = eno16777736 > > net_eth_interface = eno16777736 > > net_eth_port = 4556 > > net_interfaces = eth > > > > # Create a route to tx > > static1_uri = dtn://tx > > static1_port = 4556 > > static1_address = 10.0.0.1 > > static1_proto = dgram:udp > > static1_immediately = yes # connect immediately to this node > > #static1_global = no # this node is only reachable with internet access > > > > routing = default > > stats_traffic = yes > > api_interface = lo > > > > **dtnd startup line and output (UDP starts OK, but not bound to a working > nic) > > /home/alarm/downloads/ibr-dtn/install/sbin/dtnd -c > /home/alarm/downloads/ibr-dtn/source/ibrdtn-repo/ibrdtn/daemon/etc/rx.conf > > Mon Jan 18 15:33:05 2016 INFO NativeDaemon: IBR-DTN daemon 1.0.1 (build > a5f9012) > > Mon Jan 18 15:33:05 2016 INFO Configuration: Configuration: > /home/alarm/downloads/ibr-dtn/source/ibrdtn-repo/ibrdtn/daemon/etc/rx.conf > > Mon Jan 18 15:33:05 2016 INFO BundleCore: Local node name: dtn://rx > > Mon Jan 18 15:33:05 2016 INFO BundleCore: Forwarding of bundles enabled. > > Mon Jan 18 15:33:05 2016 INFO BundleCore: Non-singleton bundles are > accepted. > > Mon Jan 18 15:33:05 2016 INFO NativeDaemon: using bundle storage in > memory-only mode > > Mon Jan 18 15:33:05 2016 INFO NativeDaemon: API initialized using tcp > socket: lo:4550 > > Mon Jan 18 15:33:05 2016 INFO NativeDaemon: Datagram ConvergenceLayer > (UDP) added on eth0:4556 > > Mon Jan 18 15:33:05 2016 INFO DiscoveryAgent: listen to [ff02::142]:4551 > > Mon Jan 18 15:33:05 2016 INFO DiscoveryAgent: listen to [224.0.0.142]:4551 > > Mon Jan 18 15:33:05 2016 INFO DiscoveryAgent: add interface eth0 > > Mon Jan 18 15:33:05 2016 INFO NativeDaemon: Using default routing > extensions > > > > ** dtnd startup line and output (Always uses TCP Convergence layer) > > /home/alarm/downloads/ibr-dtn/install/sbin/dtnd -c > /home/alarm/downloads/ibr-dtn/source/ibrdtn-repo/ibrdtn/daemon/etc/rx.conf > -i eno16777736 > > Mon Jan 18 15:37:33 2016 INFO NativeDaemon: IBR-DTN daemon 1.0.1 (build > a5f9012) > > Mon Jan 18 15:37:33 2016 INFO Configuration: Configuration: > /home/alarm/downloads/ibr-dtn/source/ibrdtn-repo/ibrdtn/daemon/etc/rx.conf > > Mon Jan 18 15:37:33 2016 INFO BundleCore: Local node name: dtn://rx > > Mon Jan 18 15:37:33 2016 INFO BundleCore: Forwarding of bundles enabled. > > Mon Jan 18 15:37:33 2016 INFO BundleCore: Non-singleton bundles are > accepted. > > Mon Jan 18 15:37:33 2016 INFO NativeDaemon: using bundle storage in > memory-only mode > > Mon Jan 18 15:37:33 2016 INFO NativeDaemon: API initialized using tcp > socket: lo:4550 > > Mon Jan 18 15:37:33 2016 INFO NativeDaemon: TCP ConvergenceLayer added on > eno16777736:4556 > > Mon Jan 18 15:37:33 2016 INFO DiscoveryAgent: listen to [ff02::142]:4551 > > Mon Jan 18 15:37:33 2016 INFO DiscoveryAgent: listen to [224.0.0.142]:4551 > > Mon Jan 18 15:37:33 2016 INFO DiscoveryAgent: add interface eno16777736 > > Mon Jan 18 15:37:33 2016 INFO NativeDaemon: Using default routing > extensions > > > > > Kind Regards, > Nik > > > > On Mon, Jan 18, 2016 at 2:18 PM, Nik Ansell <nikansell00(a)gmail.com > <mailto:nikansell00@gmail.com> > wrote: > > Hi Stephan, > > > > Thank you for your kind reply. > > > > I originally tried both net_eth_type = udp & static1_proto = udp, but this > didn't work. > > I will try them both as dgram:udp later and respond back. > > > > > Kind Regards, > Nik > > > > On Mon, Jan 18, 2016 at 2:00 PM, Stephan Rottmann < > rottmann(a)ibr.cs.tu-bs.de <mailto:rottmann@ibr.cs.tu-bs.de> > wrote: > > Hi Nik, > > > static1_uri = dtn://rx > > static1_port = 4556 > > static1_address = 10.0.1.3 > > static1_proto = udp > Have you tried dgram:udp at this point? > > > Best regards, > Stephan > > > > > > > > > >

1 0

Discovery via broadcast
by Maël Auzias 31 Jan '16

31 Jan '16

Hi y'all! Aiming to use broadcast for the discovery, the dtn daemon log: > Wed Jan 27 14:51:55 2016 DEBUG.5 IPNDAgent: can not send message to > [10.0.0.255]:4551 via [10.0.0.12]:4551 (universe)/eth0; socket exception: > 13: Permission denied but I can find where does the permission is denied from. The daemon is run as root. Any suggestion or idea on how to work around this? Is there a way to perform a static discovery (for test purposes)? 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*

3 3

UDP Convergence Layer Ignored
by Nik Ansell 31 Jan '16

31 Jan '16

Hi, I have a strange problem that I hope someone could help me with. When I use the TCP Convergence Layer, this works fine, however when I attempt to use the UDP convergence layer, it seems to remember some old configuration, or fallback to TCP and does not use the UDP convergence layer. The conf file of my source node is below: local_uri = dtn://tx net_eth_type = dgram:udp #net_internet = eth0 net_eth_interface = eth0 net_eth_port = 4556 net_interfaces = eth # Create a route to rx static1_uri = dtn://rx static1_port = 4556 static1_address = 10.0.1.3 static1_proto = udp static1_immediately = yes # connect immediately to this node #static1_global = no # this node is only reachable with internet access routing = default stats_traffic = yes api_interface = lo However, when I start the daemon: dtnd -c /home/alarm/downloads/ibr-dtn/configs/2node-udpcl/tx.conf -v -i eth0 The log shows the following entry: Sun Jan 17 21:38:50 2016 INFO NativeDaemon: TCP ConvergenceLayer added on eth0:4556 If anyone could offer any help, this would be very much appreciated! Kind Regards, Nik

3 5

Docker and IBR-DTN bleeding edge
by Maël Auzias 30 Jan '16

30 Jan '16

Hi y'all! If you looking for an easy way to compile the bleeding edge source code of IBR-DTN, this Dockerfile may be useful: FROM debian:8.2 > MAINTAINER Mael Auzias <docker(a)mael.auzias.net> > LABEL Description="This image is used to run an ibrdtn daemon from Debian > 8 package with the most up-to-date source code" > RUN apt-get update && apt-get install -y \ > git tmux g++ libpth-dev make dh-autoreconf ca-certificates libicu52 > libpsl0 libssl1.0.0 openssl pkg-config \ --no-install-recommends \ > && apt-get clean \ > && rm -rf /var/lib/apt/lists/* > RUN cd \ > && git clone https://github.com/ibrdtn/ibrdtn.git \ > && cd ibrdtn/ibrcommon/ \ > && ./autogen.sh \ > && ./configure && make && make install \ > && cd ../ibrdtn/ \ > && ./autogen.sh \ > && ./configure && make && make install \ > && echo "include /usr/local/lib/*" >> /etc/ld.so.conf && ldconfig > EXPOSE 4556 > ENTRYPOINT ["/bin/bash"] You can then run $docker run --hostname nodeName -it --rm -v /tmp/dtn.conf:/dtn.conf ibrdtnbleeingedge and execute #dtnd -c /dtn.conf, add the flag --net=host if the aim is to use your host interface. 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

UDP Convergence Layer problem (TCP works fine)
by mazur221 18 Dec '15

18 Dec '15

Hi, i connected 2 laptops (LAN). Both computer have network interface eth0. I installed also IBRDTN(IBR-DTN daemon 1.0.1 (build 294b543)) on both computers (via apt-get install in UBUNTU 14.04.2 LTS). I tested epidemic, flooding and prophet routing protocols root@vm1:/# dtnping dtn://vm2/echo ECHO dtn://vm2/echo 64 bytes of data. 64 bytes from dtn://vm2/echo: seq=1 ttl=30 time=36.39 ms 64 bytes from dtn://vm2/echo: seq=2 ttl=30 time=39.86 ms 64 bytes from dtn://vm2/echo: seq=3 ttl=30 time=43.78 ms 64 bytes from dtn://vm2/echo: seq=4 ttl=30 time=34.04 ms 64 bytes from dtn://vm2/echo: seq=5 ttl=30 time=40.22 ms and they work fine. Nevertheless, when i try to use UDP convergence layer by setting ibrdtnd.conf on both computers: net_interfaces = lan0 net_lan0_type = udp net_lan0_interface = eth0 net_lan0_port = 4556 ping does not work(neither dtnsend)! Ibrdtn daemon does not show any errors(see below). In wireshark i can only see Discovery packets. Moreover i can see that both nodes can see each other (by using ibrdtn api neighbor list command). Wed Dec 16 15:31:16 2015 INFO NativeDaemon: IBR-DTN daemon 1.0.1 (build 294b543) Wed Dec 16 15:31:16 2015 INFO Configuration: Configuration: /etc/ibrdtn/ibrdtnd.conf Wed Dec 16 15:31:16 2015 INFO NativeDaemon: use logfile for output: /var/log/ibrdtn/ibrdtn.log Wed Dec 16 15:31:16 2015 INFO NativeDaemon: Parallel event processing enabled using 4 processes. Wed Dec 16 15:31:16 2015 INFO BundleCore: Local node name: dtn://vm1 Wed Dec 16 15:31:16 2015 INFO BundleCore: Forwarding of bundles enabled. Wed Dec 16 15:31:16 2015 INFO NativeDaemon: using bundle storage in memory-only mode Wed Dec 16 15:31:16 2015 INFO NativeDaemon: API initialized using tcp socket: loopback:4550 Wed Dec 16 15:31:16 2015 INFO NativeDaemon: UDP ConvergenceLayer added on eth0:4556 Wed Dec 16 15:31:16 2015 INFO DiscoveryAgent: listen to [224.0.0.142]:4551 Wed Dec 16 15:31:16 2015 INFO DiscoveryAgent: listen to [ff02::142]:4551 Wed Dec 16 15:31:16 2015 INFO DiscoveryAgent: add interface eth0 Wed Dec 16 15:31:16 2015 INFO NativeDaemon: Using flooding routing extensions Wed Dec 16 15:31:16 2015 INFO FloodRoutingExtension: Initializing flooding routing module ibrdtn log looks the same on the second computer (except of course local node name:) Ubuntu instalation were made just before testing IBRDTN (ports are open, IPTABLES do not block anything, time on each computer differs by only 2 seconds) I would be very grateful if you could provide me with any hints or maybe someone experienced this issue and already know the solution for this problem. Best Regards Michał

2 3

Prophet Routing configuration
by Mohammad Rifqi 17 Dec '15

17 Dec '15

dear all, i want to run 3 node DTN (raspberry pi) in 2 hop toplogy scenario. node 1 - node 2 - node 3 node 1 is not directly connected to node 3. so, if node 1 want to commmunicate to node 3 it should be through node 2. The problem is node 2 can not forward the bundle to node 3. so, when i ping node 1 to node 3, the result is timeout. which part of ibrdtn.conf file configuration that should edited? this is my current ibrdtn.conf configuration local_uri = dtn://dtn-node2.dtn discovery_address = 255.255.255.255 discovery_announce = 0 net_interfaces = wlan0 net_wlan0_type = tcp net_wlan0_interface = wlan0 net_wlan0_port = 4556 routing = prophet routing_prefer_direct = yes #node 2 static1_address = 192.168.10.12 static1_uri = dtn://dtn-node2.dtn static1_proto = tcp #node 1 static2_address = 192.168.10.11 static2_uri = dtn://dtn-node1.dtn static1_proto = tcp time_reference = yes time_synchronize = yes time_discovery_announcements = yes in your opinion, what's wrong with my configuration? what it should be? Thanks, Rifqi

3 3