Re: [dtn-interest] problem of using discovery of ad-hoc mode

"Long, Darren" <Darren.Long@uk.thalesgroup.com> Fri, 23 November 2007 11:07 UTC

Received: from crawsmail1.uk.thalesgroup.com (mail.uk.thalesgroup.com [192.93.164.29]) by maillists.intel-research.net (8.13.8/8.13.7) with ESMTP id lANB7ct9007599 for <dtn-interest@mailman.dtnrg.org>; Fri, 23 Nov 2007 03:07:39 -0800
Received: from crawsmail1.uk.thalesgroup.com (mailsweeper1.int.rdel.co.uk) by crawsmail1.uk.thalesgroup.com (Content Technologies SMTPRS 4.3.14) with ESMTP id <T8378985131c0a85c02900@crawsmail1.uk.thalesgroup.com> for <dtn-interest@mailman.dtnrg.org>; Fri, 23 Nov 2007 11:06:03 +0000
Received: from mail.uk.thalesgroup.com (lisc0021.int.rdel.co.uk) by crawsmail1.uk.thalesgroup.com (Clearswift SMTPRS 5.2.9) with ESMTP id <T83789b31e2c0a85c09c28@crawsmail1.uk.thalesgroup.com> for <dtn-interest@mailman.dtnrg.org>; Fri, 23 Nov 2007 11:09:12 +0000
Received: from exchange.wvintenltd.com (exchange.int.rdel.co.uk [172.26.96.27]) by mail.uk.thalesgroup.com (8.12.8/8.12.8) with ESMTP id lANB7Y6i006505 for <dtn-interest@mailman.dtnrg.org>; Fri, 23 Nov 2007 11:07:34 GMT
Received: by exchange.wvintenltd.com with Internet Mail Service (5.5.2657.72) id <W5DJJSB4>; Fri, 23 Nov 2007 11:08:18 -0000
Message-ID: <E713D692AAD2D6498AFC94BE27CB38A51B70AE@exchange.wvintenltd.com>
From: "Long, Darren" <Darren.Long@uk.thalesgroup.com>
To: 'Delay Tolerant Networking Interest List' <dtn-interest@mailman.dtnrg.org>
Date: Fri, 23 Nov 2007 11:08:17 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C82DC1.2698AE5C"
Subject: Re: [dtn-interest] problem of using discovery of ad-hoc mode
X-BeenThere: dtn-interest@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Delay Tolerant Networking Interest List <dtn-interest@mailman.dtnrg.org>
List-Id: Delay Tolerant Networking Interest List <dtn-interest.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-interest>
List-Post: <mailto:dtn-interest@mailman.dtnrg.org>
List-Help: <mailto:dtn-interest-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Nov 2007 11:07:41 -0000

Hi Zhan,
 
My own experience with IP discovery is that it is ok when the associated network interface is always up, but can have issues when the interface goes down and IP discovery doesn't recover.  I suspect that the use of ad-hoc wireless connections causes this problem for you.  If you use external ethernet attached wifi devices rather than internal ones, this probably won't happen, but I've not tried that so I'm not sure.  With an internal adapter, you could try restarting the dtnd after the ad-hoc connection is made or use bonjour instead.
 
For bonjour on Linux (I assume that's what you are using), I've used avahi instead of the apple code and that works fine, although a tweak is needed in the avahi.conf file to disable the additional service cookie, i.e. set add-service-cookie=no
 
As far as I can tell, the main difference (apart from the fact that bonjour is resilient to intermittent network connectivity) is that (as I understand it) bonjour works only on the local subnet, but IP discovery can be used for unicast discovery through routers.
 
Hope this helps.  You should probably post this kind of question to dtn-users rather than dtn-interest though.
 
Cheers,
 
Darren

-----Original Message-----
From: dtn-interest-bounces@mailman.dtnrg.org [mailto:dtn-interest-bounces@mailman.dtnrg.org]On Behalf Of Zhan Jie
Sent: 23 November 2007 06:02
To: dtn-interest@mailman.dtnrg.org
Subject: Re: [dtn-interest] problem of using discovery of ad-hoc mode


Hi, 

i had set up 2 nodes as ad-hoc network as according to the previous email. 

Situation 1 

Node 1(IP:192.168.10.1) --------- Node 2( Ip: 192.168.10.2) 

i am able to ping each other in the network. 

The configuration file for each node is as follows: 

Node 1 
route set type dtlsr 
route local_eid "dtn://one.dtn" 
interface add tcp0 tcp 
interface add udp0 udp 
discovery add ipdisc0 ip port=2000 addr=192.168.10.1 
discovery announce tcp0 ipdisc0 tcp interval=5 interval=5 

Node 2 
route set type dtlsr 
route local_eid "dtn://two.dtn" 
interface add tcp0 tcp 
interface add udp0 udp 
discovery add ipdisc0 ip port=2000 addr=192.168.10.2 
discovery announce tcp0 ipdisc0 tcp interval=5 interval=5 

There will not be error message. However, the DTN node still not able to detect each other. 

Situation 2 

when i connect both laptop to a router as follows: 

Node 1(Ip:192.168.5.100) ---LAN Connection-- [ROUTER] --LAN Connection-- Node 2 (Ip: 192.168.5.101) 

The configuration file is as follows: 

Node 1 
route set type dtlsr 
route local_eid "dtn://one.dtn" 
interface add tcp0 tcp 
interface add udp0 udp 
discovery add ipdisc0 ip port=2000 
discovery announce tcp0 ipdisc0 tcp interval=5 interval=5 

Node 2 
route set type dtlsr 
route local_eid "dtn://two.dtn" 
interface add tcp0 tcp 
interface add udp0 udp 
discovery add ipdisc0 ip port=2000 
discovery announce tcp0 ipdisc0 tcp interval=5 interval=5 

In Situation 2, the node 1 DTN is able to locate Node 2 DTN. Thus i can able to send file or message to Node 2. However i am not able to do that in Situation 1 as Node 1 cannot locate Node 2. is that any mistake in the configuration file?

another question is that what is the difference between discovery_bonjour and ipdisc0? 
And discovery only used for neighbor protocol?