Re: [dtn-interest] dtn.conf

Michael Demmer <demmer@cs.berkeley.edu> Thu, 06 January 2005 13:30 UTC

Received: from relay0.EECS.Berkeley.EDU (relay0.EECS.Berkeley.EDU [169.229.60.163]) by webbie.berkeley.intel-research.net (8.11.6/8.11.6) with ESMTP id j06DUv106781 for <dtn-interest@mailman.dtnrg.org>; Thu, 6 Jan 2005 05:30:57 -0800
Received: from pisco (pisco.CS.Berkeley.EDU [128.32.37.175]) by relay0.EECS.Berkeley.EDU (8.13.2/8.12.10) with ESMTP id j06DUh4F015849; Thu, 6 Jan 2005 05:30:43 -0800 (PST)
Received: from demmer by pisco with local (Exim 4.34) id 1CmXio-0002Qq-3y; Thu, 06 Jan 2005 05:30:38 -0800
Date: Thu, 06 Jan 2005 05:30:38 -0800
From: Michael Demmer <demmer@cs.berkeley.edu>
To: Daniel Caughran <dfcaughran@comcast.net>
Cc: dtn-interest@mailman.dtnrg.org, colin.a@gmail.com, jeff@elkner.net, Scott.Burleigh@jpl.nasa.gov, sosolish@gmail.com
Subject: Re: [dtn-interest] dtn.conf
Message-ID: <20050106133038.GA8896@pisco.cs.berkeley.edu>
Mail-Followup-To: Daniel Caughran <dfcaughran@comcast.net>, dtn-interest@mailman.dtnrg.org, colin.a@gmail.com, jeff@elkner.net, Scott.Burleigh@jpl.nasa.gov, sosolish@gmail.com
References: <DJEOLFIKBMLMPLGGFKELCEHICAAA.dfcaughran@comcast.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DJEOLFIKBMLMPLGGFKELCEHICAAA.dfcaughran@comcast.net>
User-Agent: Mutt/1.4.2i
Sender: dtn-interest-admin@mailman.dtnrg.org
Errors-To: dtn-interest-admin@mailman.dtnrg.org
X-BeenThere: dtn-interest@mailman.dtnrg.org
X-Mailman-Version: 2.0.13
Precedence: bulk
List-Help: <mailto:dtn-interest-request@mailman.dtnrg.org?subject=help>
List-Post: <mailto:dtn-interest@mailman.dtnrg.org>
List-Subscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@mailman.dtnrg.org?subject=subscribe>
List-Id: Delay Tolerant Networking Interest List <dtn-interest.mailman.dtnrg.org>
List-Unsubscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://mailman.dtnrg.org/pipermail/dtn-interest/>

> I am one of the students working on the science project involving
> the DTN software. We are currently using DTN version 2.0.2 and
> having some problems with the configuration.  We are attempting to
> use three computers to send bundles from one to another using the
> third as a bundle relay. Could anybody send us an example dtn.conf
> file or explain the parameters.

You should start with the dtn.conf that's included in the software
distribution. It lists most of the configuration options with a little
comment blurb describing it.

For the three machine case you're looking at, you'll need to do the
following for each node (assuming your hosts are named
machineN.dns.org):

a) configure an interface to accept bundles
b) configure a link to each peer
c) configure routing to match certain bundle addresses to the
   configured links

So for your case, assuming you're using TCP (the only functional
convergence layer at the moment), the config snippets for each host
would be the following.

For the interface, you can just use the bit that's already included in
the default config:

   # interface add tcp host://<addr>:<port>/
   #
   # Add an input interface to listen on addr:port for incoming bundles
   # from other tcp convergence layers
   interface add tcp host://0.0.0.0:5000/

For links and routes, the config is different for each host:

   # machine 1
   link add tcp0 host://machine2.dns.org:5000 ONDEMAND tcp
   route add bundles://internet/host://machine2.dns.org/* tcp0
   route add bundles://internet/host://machine3.dns.org/* tcp0

   # machine 1
   link add tcp0 host://machine1.dns.org:5000 ONDEMAND tcp
   link add tcp1 host://machine3.dns.org:5000 ONDEMAND tcp
   route add bundles://internet/host://machine1.dns.org/* tcp0
   route add bundles://internet/host://machine3.dns.org/* tcp1

   # machine 3
   link add tcp0 host://machine2.dns.org:5000 ONDEMAND tcp
   route add bundles://internet/host://machine1.dns.org/* tcp0
   route add bundles://internet/host://machine2.dns.org/* tcp0

Note that I've followed a convention of naming the links similar to
network devices in a unix kernel (i.e. tcp0, tcp1, etc)

Hopefully this will help. If this does not work for you, let me
know. 

-m