DTN Disconnectathon July 29, 30 and Stockholm / North America Will Ivancic

Hosts Registered to Ohio University DTN dtnbone.ocp.ohiou.edu name server lin5.its.ohiou.edu. < Name server URL bbn-dtnbone-m04.dtnbone.ocp.ohiou.edu has address bbn-dtnbone-m05.dtnbone.ocp.ohiou.edu has address bbn-dtnbone-m06.dtnbone.ocp.ohiou.edu has address bbn-dtnbone-m10.dtnbone.ocp.ohiou.edu has address daedalus.dtnbone.ocp.ohiou.edu has address dax.dtnbone.ocp.ohiou.edu has address dtngateway dtnbone.ocp.ohiou.edu has address dtnmule-2-10.dtnbone.ocp.ohiou.edu has address dtnmule-2-31.dtnbone.ocp.ohiou.edu has address haruman.dtnbone.ocp.ohiou.edu has address jishac-laptop.dtnbone.ocp.ohiou.edu has address laren.dtnbone.ocp.ohiou.edu has address miles.dtnbone.ocp.ohiou.edu has address quest.dtnbone.ocp.ohiou.edu has address sphere.dtnbone.ocp.ohiou.edu has address teemu.dtnbone.ocp.ohiou.edu has address dtnbone.commet.tkk.fi (Camera Application) <---- Registered in other DNS testbed1.dtnbone.ocp.ohiou.edu has address testbed2.dtnbone.ocp.ohiou.edu has address testbed3.dtnbone.ocp.ohiou.edu has address testbed4.dtnbone.ocp.ohiou.edu has address testbed5.dtnbone.ocp.ohiou.edu has address thegame.dtnbone.ocp.ohiou.edu has address unit017.dtnbone.ocp.ohiou.edu has address

Hosts on expect to remain on DTNbone laren.dtnbone.ocp.ohiou.edu has address (Ohio University – ION / UDP, s-TCP, TCP) miles.dtnbone.ocp.ohiou.edu has address (Ohio University – ION / UDP, s-TCP, TCP) quest.dtnbone.ocp.ohiou.edu has address (Ohio University – ION UDP, s-TCP, TCP) testbed4.dtnbone.ocp.ohiou.edu has address (Ohio University -– ION / TCP) unit017.dtnbone.ocp.ohiou.edu has address (Ohio University – ION and DTN2 / TCP and UDP) basil.dsg.cs.tcd.ie (Trinity College Dublin – DTN2) reeves.viagenie.ca (Viagenie – DTN2) (BBN - Spindle) (BBN - Spindle) (BBN - Spindle)

Ohio University Disconnectathon Testbed

Trinity College Dublin Disconnectathon Testbed

What was not done No Security tested. No LTP testing Need to add disconnection to the system Partial success with Camera request and bundle reply Joseph-Laptop Unit / -- Camera Joseph-Laptop --/-- Unit / -- Camera Joseph-Laptop --/-- Unit017 Camera Joseph-Laptop Unit / -- Camera (Bundle stuck in Unit017 and not forwarded - possible DTN2 Bug)

Routing All test were via static routing Except Teemu’s camera was flooding to all known DTN routes. Prophet was NOT run this week, but should be ready for N4C demonstration in August 2009 Perhaps we can add DLSR or something in the DTNbone backbone routers – or at least a few of them Known naming issues regarding routing between ION contact graph routing and dtn: naming scheme.

Successes (1) Variety of Multi-hop scenarios run on all platforms Applications Camera application was successful Non-interoperable ION and DTN standard tools Ping, send, echo, Ohio University test their API between their DTN and ION machines. Probable release later this month/year

Successes (2) Implementations DTN2 Combinations of UDP and TCP used for some multi-hop tests ION Combinations of UDP and TCP used for some multi-hop tests Objective-C (iPhone) Basic BP + TCPCL Java (Android) Basic BP + TCPCL Symbian implementation, new (some Nokia phones) DTNS60 DTN2 works DTNS60 TKK Java implementation (receiving works when connection initiated from the Symbian side) TKK iPhone implementation (same bug) DTNS60 --> BBN (probably the same bug as before)

Successes (3) Implementations BBN Spindle BBN Spindle ION, UDP CL, works BBN Spindle TKK Java, TCP CL, works BBN Spindle TKK iPhone, TCP CL Works TKK Java BBN Spindle BBN Spindle TKK iPhone, TCPCL, works BBN Spindle dtn2 (NASA, S Farrell), TCP CL, works Complicated multi-hop scenario involving: 2 BBN nodes, 4 Alex McMahon nodes, 2 Elwyn Davies nodes all TCP CL (still working on it, but looks like it will work) DTN2 on N810 Used to send

Successes(4) A multi hop network from the various pieces present in the IETf terminal Static routing was used. Connectivity was a mix of wired and infrastructure WLAN. Getting the routing tables correctly configured proved a little challenging Issues encountered links not coming up as expected resulting in 'jammed bundles bundle floods resulting from previously transmitted custodial bundles being transmitted when links did come up. [Disconnectathon multi-hop experiment: Record of bundles passed across 9 links] user1.nomadic.n4c.eu DTN2 on N810/Maemo-Diablo IETF, Stockholm elwynd.nomadic.n4c.eu DTN2 on Asus EeePc 1000/Xandros IETF, Stockholm gateway.nomadic.n4c.eu DTN2 on Epia/Gentoo Maidenhead, UK basil.dsg.cs.tcd.ie.dtn DTN2 on Ubuntu LPIA in PC Xen VM PC TCD, Dublin TCD gateway machine DTN2 on Asus EeePC 901/Ubuntu LPIA IETF. Stockholm TCD mule machine DTN2 on Asus EeePC 901/Ubuntu LPIA IETF, Stockholm Sphere, TCD DTN2 on 64 bit Laptop/Ubuntu LPIA IETF, Stockholm bbn-dtnbone-m05 BBN on Linux VM in Apple Mac IETF, stockholm bbn-dtnbone-m10 BBN on Linux IETF, stockholm user9.nomadic.n4c.eu DTN2 on N810/Maemo Diablo IETF, Stockholm

30 July 2009 Disconnectathon Team 9 Node multi-hop, multi-implementation test

Problems Time sync problems Ohio University experiencing shared memory issues with ION. DTN2 NASA GRC experiencing database issues with DTN2 requiring periodic cleanup. Potential bugs in the code? Packets not forwarded on disconnected links after they return. Manual configuration errors Simple things like forgetting that a machine is using non-default port numbers

Lessons Learned Dynamic DNS was useful Allowed use of IETF infrastructure Easier to keep track of names than addresses – particularly if addresses change Ohio University API Documentation at Learn a lot about diagnostics What works What doesn’t Additional needs

Lessons Learned Get a dedicated room early for all day. White board would be good to keep track of routes and network configuration - At least what we think we setup Jabber worked great Network diagrams on wiki where useful Would be good to try and upload whiteboard diagram to wiki periodically Web-based Network Monitoring tools Ohio University posted network logs Ohio University posted DNS (Local Name Resolver) entries Identified new monitoring / troubleshooting needs during tests.