Subject: Re: [dtn-users] EthConvergenceLayer
From: Jeff Wilson <[email-masked]>
To: [email-masked]
Date: Wed, 27 Apr 2005 15:38:00 -0500
List-Id: discussion/answers list for users of the dtn reference implementation <dtn-users.mailman.dtnrg.org>

You know, I like it when you guys reply so fast.  I could get spoiled
to that quick turn around ... :D   Keep it up!!

         Thanks so much,
           jw

On 4/27/05, Jakob Eriksson <[email-masked]> wrote:
> Hi Jeff,
> 
> Sorry, I need to change that. The type is supposed to be
> "neighborhood". You specify that in dtn.conf
> using the command
> 
> route set type neighborhood
> 
> In retrospect, embedding instructions in the cvs log is pretty daft. =)
> I'll add something to the code asap.
> 
> - Jakob
> 
> On Apr 27, 2005, at 1:26 PM, Jeff Wilson wrote:
> 
> > Hi Jakob,
> >
> > In the CVS log on r1.4 of EthConvergenceLayer, you embedded these
> > instructions:
> >
> > <quote>
> > Tested bundle sending & receiving, seems to be working properly. Fixed
> > some byte-order problems, logging in DynamicBundleRouter.
> >
> > To test it, set up a couple of routers on the same lan with type
> > "dynamic". You'll see them discover each other. Then send a bundle
> > using the command prompt:
> >
> > bundle inject eth://<source> eth://<dest> Hello 5
> >
> > will send a bundle with payload "Hello" from source to destination.
> > Unfortunately, there's nobody listening on the other side yet...
> > </quote>
> >
> > My question, is where do I specify type "dynamic"?
> >
> >          thanks,
> >            jw
> > _______________________________________________
> > dtn-users mailing list
> > [email-masked]
> > http://mailman.dtnrg.org/mailman/listinfo/dtn-users
> >
> Jakob Eriksson
> Ph.D. Candidate
> http://www.cs.ucr.edu/~jeriksson
> 
> _______________________________________________
> dtn-users mailing list
> [email-masked]
> http://mailman.dtnrg.org/mailman/listinfo/dtn-users
>

From: Jakob Eriksson <[email-masked]>
Subject: Re: [dtn-users] EthConvergenceLayer
Date: Wed, 27 Apr 2005 13:31:47 -0700
To: [email-masked]
Sender: [email-masked]
Reply-To: [email-masked]

Hi Jeff,

Sorry, I need to change that. The type is supposed to be 
"neighborhood". You specify that in dtn.conf
using the command

route set type neighborhood

In retrospect, embedding instructions in the cvs log is pretty daft. =) 
I'll add something to the code asap.

- Jakob

On Apr 27, 2005, at 1:26 PM, Jeff Wilson wrote:

> Hi Jakob,
>
> In the CVS log on r1.4 of EthConvergenceLayer, you embedded these 
> instructions:
>
> <quote>
> Tested bundle sending & receiving, seems to be working properly. Fixed
> some byte-order problems, logging in DynamicBundleRouter.
>
> To test it, set up a couple of routers on the same lan with type
> "dynamic". You'll see them discover each other. Then send a bundle
> using the command prompt:
>
> bundle inject eth://<source> eth://<dest> Hello 5
>
> will send a bundle with payload "Hello" from source to destination.
> Unfortunately, there's nobody listening on the other side yet...
> </quote>
>
> My question, is where do I specify type "dynamic"?
>
>          thanks,
>            jw
> _______________________________________________
> dtn-users mailing list
> [email-masked]
> http://mailman.dtnrg.org/mailman/listinfo/dtn-users
>
Jakob Eriksson
Ph.D. Candidate
http://www.cs.ucr.edu/~jeriksson

Date: Wed, 27 Apr 2005 13:30:01 -0700
From: Michael Demmer <[email-masked]>
To: [email-masked]
Subject: Re: [dtn-users] EthConvergenceLayer
Sender: [email-masked]
Reply-To: [email-masked]

The original DynamicBundleRouter that Jacob referred to has been
renamed (for sanity) the NeighborhoodRouter.

You enable it by putting "route set type neighborhood" in dtn.conf.

-m

> Hi Jakob,
> 
> In the CVS log on r1.4 of EthConvergenceLayer, you embedded these instructions:
> 
> <quote>
> Tested bundle sending & receiving, seems to be working properly. Fixed
> some byte-order problems, logging in DynamicBundleRouter.
> 
> To test it, set up a couple of routers on the same lan with type
> "dynamic". You'll see them discover each other. Then send a bundle
> using the command prompt:
> 
> bundle inject eth://<source> eth://<dest> Hello 5
> 
> will send a bundle with payload "Hello" from source to destination.
> Unfortunately, there's nobody listening on the other side yet...
> </quote>
> 
> My question, is where do I specify type "dynamic"?
> 
>          thanks,
>            jw
> _______________________________________________
> dtn-users mailing list
> [email-masked]
> http://mailman.dtnrg.org/mailman/listinfo/dtn-users

Date: Wed, 27 Apr 2005 15:26:37 -0500
From: Jeff Wilson <[email-masked]>
To: [email-masked]
Subject: [dtn-users] EthConvergenceLayer
Sender: [email-masked]
Reply-To: [email-masked]

Hi Jakob,

In the CVS log on r1.4 of EthConvergenceLayer, you embedded these instructions:

<quote>
Tested bundle sending & receiving, seems to be working properly. Fixed
some byte-order problems, logging in DynamicBundleRouter.

To test it, set up a couple of routers on the same lan with type
"dynamic". You'll see them discover each other. Then send a bundle
using the command prompt:

bundle inject eth://<source> eth://<dest> Hello 5

will send a bundle with payload "Hello" from source to destination.
Unfortunately, there's nobody listening on the other side yet...
</quote>

My question, is where do I specify type "dynamic"?

         thanks,
           jw

Date: Fri, 22 Apr 2005 10:58:36 -0700
From: Michael Demmer <[email-masked]>
To: Jeff Wilson <[email-masked]>
Cc: [email-masked], [email-masked]
Subject: [dtn-users] Re: [dtn-bugs] Fwd: segmentation fault with latest CVS
Sender: [email-masked]
Reply-To: [email-masked]

I just checked in a fix that should take care of this. Please update
and see if the problem is taken care of.

Thanks,
-m

> Sorry for the cross post, I just realized I should've posted to this list first!
> 
>      Regards,
>      jw
> 
> 
> ---------- Forwarded message ----------
> From: Jeff Wilson <[email-masked]>
> Date: Apr 21, 2005 10:19 PM
> Subject: segmentation fault with latest CVS
> To: [email-masked]
> 
> 
> My custom lately has been, issue a cvs up -Pd, then make, then start
> up dtnd and continue wherever I left off last.  This evening I
> encountered segmentation fault when I tried to start ./daemon/dtnd ...
> To confirm that I hadn't messed up my dtn.conf or something simple
> like that, I went back to download v. 2.1.1.  After tar -zxf && config
> -C && make, I was up and running again, no problems.  Is anyone else
> having this trouble?
> 
>       Thanks for your time,
>          jw
> _______________________________________________
> dtn-bugs mailing list
> [email-masked]
> http://mailman.dtnrg.org/mailman/listinfo/dtn-bugs

Date: Thu, 21 Apr 2005 22:19:48 -0500
From: Jeff Wilson <[email-masked]>
To: [email-masked]
Subject: [dtn-users] segmentation fault with latest CVS
Sender: [email-masked]
Reply-To: [email-masked]

My custom lately has been, issue a cvs up -Pd, then make, then start
up dtnd and continue wherever I left off last.  This evening I
encountered segmentation fault when I tried to start ./daemon/dtnd ...
To confirm that I hadn't messed up my dtn.conf or something simple
like that, I went back to download v. 2.1.1.  After tar -zxf && config
-C && make, I was up and running again, no problems.  Is anyone else
having this trouble?

      Thanks for your time,
         jw

Date: Mon, 18 Apr 2005 16:47:20 -0600
From: Jeff Allen <[email-masked]>
To: Jeff Wilson <[email-masked]>, [email-masked]
Subject: Re: [dtn-users] LOG_DEBUG
Sender: [email-masked]
Reply-To: [email-masked]

Jeff Wilson asked:
> Is there anything I could do to help with the (manual) effort?

Write pages!

I am out of commission because I am in Guatemala learning Spanish for
another three weeks. After that, I'll probably return to here for a
volunteer job for several months. During that time, I will probably
start working on DTN2 again, but I'll write all the documentation in
Spanish. (just kidding about the spanish part...)

The best way to get involved with the manual is to choose a piece that
is not done. Claim it to make sure no one else is duplicating the
effort by sending a note to the mailing list. When you have a
completed file, or a patch to an existing file, send it to the list so
that Michael or someone else can check it in for you.

Here's a todo list of things you could choose to do. It is in order
from easy and immediate to harder and longer term:

 * write more tutorials. One that shows how to make a link between two
dtnd's is the next required one. After that, a debugging one would be
good.
 * write the arch.html page, which will draw heavily on Mike's (and
other people's) paper.
 * document one of the commands for the main reference page. You
usually need to read the source to know exactly how things work. This
is critical, because somethings things do not work like you expect
from their names... typically this a bug, and you can ask someone to
fix it, or document it as is if it will take several releases to get a
complete fix done.
 * write the first man page, probably for something easy like dtnrecv,
since the first man page is more about process than content: You
should add hooks into the makefiles to arrange for your man page to be
converted into text (nroff -man $file.1 > $file.txt) and (hopefully)
html (but I don't know which tool to use for this). This is obviously
the hardest project waiting to be done, but it blocks other man pages,
so it is important to do it and get it done right.
 * choose a documentation markup system (like docbook) and setup a
system to generate .html, .pdf, etc from it. Convert everything that's
done so far into the new system and write a document for manual
writers who come behind you explaining what you did. This is not a
required project, but it might be nice to do. The sooner we do it, the
less work the conversion step will be. But it could never happen and
no harm would come from it.

Hopefully my answer to Jeff will get other people interested in
writing a piece of the manual!

  -jeff

Date: Thu, 14 Apr 2005 08:36:26 -0700
From: Michael Demmer <[email-masked]>
To: [email-masked]
Subject: Re: [dtn-users] doxygen updates
Sender: [email-masked]
Reply-To: [email-masked]

> I just noticed the new EthConvergenceLayer when I recently ran CVS
> update.  How often does Doxygen
> (http://www.dtnrg.org/docs/code/DTN2/doc/doxygen/html/index.html) get
> updated?  I'd love to read up on the new CL ...

We've been updating that one whenever we make a new release, which has
been around every month or so.

It is, however, easy to generate for yourself, just install doxygen,
check out the HEAD of the cvs tree, and run 'make doxygen' in the
top-level directory.

-m

Date: Thu, 14 Apr 2005 09:22:22 -0500
From: Jeff Wilson <[email-masked]>
To: [email-masked]
Subject: [dtn-users] doxygen updates
Sender: [email-masked]
Reply-To: [email-masked]

Howdy,

I just noticed the new EthConvergenceLayer when I recently ran CVS
update.  How often does Doxygen
(http://www.dtnrg.org/docs/code/DTN2/doc/doxygen/html/index.html) get
updated?  I'd love to read up on the new CL ...

        Thanks,
          jw

Date: Wed, 13 Apr 2005 16:05:58 -0500
From: Jeff Wilson <[email-masked]>
To: [email-masked]
Subject: Re: [dtn-users] LOG_DEBUG
Sender: [email-masked]
Reply-To: [email-masked]

Thank you!  Exactly the helpful hint I needed!

     thanks,
     jw

On 4/13/05, Michael Demmer <[email-masked]> wrote:
> 
> The debugging output is controlled by a file in ~/.dtndebug -- the
> format of which is a series of lines of the form '<path> <level>'
> where path corresponds to the particular logging target and level is
> one of the debug levels. The level for a particular message is chosen
> by the longest match in the file
> 
> For example:
> 
> # my ~/.dtndebug file
> /               debug
> /test           info
> /test/xyz       debug
> 
> Would emit debug level messages for all log targets, including
> those starting with /test/xyz but not others starting with /test.
> 
> Take a look at DTN2/doc/manual/logging.html for a longer description.
> 
> -m

Date: Wed, 13 Apr 2005 13:32:14 -0700
From: Michael Demmer <[email-masked]>
To: [email-masked]
Subject: Re: [dtn-users] LOG_DEBUG
Sender: [email-masked]
Reply-To: [email-masked]

The debugging output is controlled by a file in ~/.dtndebug -- the
format of which is a series of lines of the form '<path> <level>'
where path corresponds to the particular logging target and level is
one of the debug levels. The level for a particular message is chosen
by the longest match in the file

For example:

# my ~/.dtndebug file
/		debug
/test		info
/test/xyz	debug

Would emit debug level messages for all log targets, including
those starting with /test/xyz but not others starting with /test.

Take a look at DTN2/doc/manual/logging.html for a longer description.

-m

> How do I get the test modules and other code to start outputting the
> LOG_DEBUG messages?  Is that a -D somewhere in a Makefile?
> 
>       thanks,
>           jw
> _______________________________________________
> dtn-users mailing list
> [email-masked]
> http://mailman.dtnrg.org/mailman/listinfo/dtn-users

Date: Wed, 13 Apr 2005 15:07:05 -0500
From: Jeff Wilson <[email-masked]>
To: [email-masked]
Subject: [dtn-users] LOG_DEBUG
Sender: [email-masked]
Reply-To: [email-masked]

How do I get the test modules and other code to start outputting the
LOG_DEBUG messages?  Is that a -D somewhere in a Makefile?

      thanks,
          jw

Date: Fri, 8 Apr 2005 12:54:24 -0700
From: Michael Demmer <[email-masked]>
To: [email-masked]
Subject: Re: [dtn-users] adding library to autoconf
Sender: [email-masked]
Reply-To: [email-masked]

> I'm playing around with the DTN source tree, toying with the idea of
> contributing a convergence layer ... if I can figure out how.  I have
> a few copy-paste-edit additions already -- these modules seem to
> compile OK.  Now I'm in oasys/test, trying to emulate tcp-socket-test,
> but I can't figure out where in autoconf/Makefile to add a new library
> to get my executable to link.  Where can I read more about autoconf? 

The info page for autoconf is pretty good at documenting specific
macros, though I have yet to find a good top-down reference.

> Or does someon on-list have a quick pointer on this particular case? 
> I can be more specific if need be.

Look for the use of AC_SEARCH_LIBS for common system libraries, or the
checks that are in oasys/aclocal/db.ac for an optional library
(berkeley db) that checks in various places for different versions.

-m

Date: Fri, 8 Apr 2005 14:28:12 -0500
From: Jeff Wilson <[email-masked]>
To: [email-masked]
Subject: [dtn-users] adding library to autoconf
Sender: [email-masked]
Reply-To: [email-masked]

Hi

I'm playing around with the DTN source tree, toying with the idea of
contributing a convergence layer ... if I can figure out how.  I have
a few copy-paste-edit additions already -- these modules seem to
compile OK.  Now I'm in oasys/test, trying to emulate tcp-socket-test,
but I can't figure out where in autoconf/Makefile to add a new library
to get my executable to link.  Where can I read more about autoconf? 
Or does someon on-list have a quick pointer on this particular case? 
I can be more specific if need be.

         Thanks for your time,
           Jeff