Good morning!

The parameter --badclock is only required if the clocks of the nodes are not in sync and this approach has not been tested with DTN2 and might result in expiring bundles! It is better to leave this out.

Dtnping is working with DTN2, IBR-DTN and any combination of them. Important here is to address the right endpoint. IBR-DTN has ".../echo" and DTN2 has ".../ping".

If that is not enough to get your setup working, you should sent me at least the log output of all the daemon (IBR-DTN AND DTN2).

Kind regards, Johannes

-------- Weitergeleitete Nachricht -------- Von: Carlos Neves cneves777@hotmail.com An: morgenroth@ibr.cs.tu-bs.de Betreff: Urgent part2 - Dtn2 and ibr-dtn Datum: Fri, 14 Dec 2012 00:13:03 +0000

Hi again. We have try all afternoon and nothing.

I have this network configuration:

dtn://carlos.dtn (IBR-DTN) -------------- dtn://alameda (IBR-DTN) ------------------ dtn://gateway (DTN2) 192.168.3.19 192.168.3.1| 192.168.6.1 192.168.6.254 .....

discovery_version=0 discovery_version=0 ???http://www.dtnrg.org/wiki/DraftAutodiscoveryCode???

If i'am in dtn://gateway.dtn I received the bundles from dtn://carlos.dtn to dtn://gateway.dtn BUT the bundle the bundle get expired because they reach to DTN2 with expiration=0

we are starting the daemon's of ibr dtn with the arg --badclock i guess is related right? What should we do?

Also is it possible to ping from dtn2 (dtnping) and ibr-dtn(dtnping) ? i'm not sure... if you manage to that let us know ! :)