[omniORB] omniORB on Laptops?

[Theo Aukerman]

Another DHCP problem related specifically to laptops is the possibility that
you are running while not connected to the network, and therefore do not
have an IP address at all.

If your application only runs locally, you might try using the
OMNIORB_USEHOSTNAME environment variable to attempt to force a binding to
the local loopback IP address (127.0.0.1).  Doing this would make
communication to the ORB from any non-local ORB impossible, but at least you
could run while not connected to the network.

I have no idea how you might handle the case where you are
disconnecting/reconnecting to a network (possibly getting a new IP address),
and not have to stop/restart the ORB and/or application.

Theo


-----Original Message-----
From: Sai-Lai Lo [mailto:S.Lo@uk.research.att.com]
Sent: Friday, October 01, 1999 10:40 AM
To: ryan.tecco
Cc: omniorb-list@uk.research.att.com
Subject: Re: [omniORB] omniORB on Laptops?


I suspect the BOA fails because it can't work out its own name and IP
address. Try to do something like this:

$ eg2_impl -BOAiiop_name_port 192.168.1.2:12345

Or 

$ export OMNIORB_USEHOSTNAME=192.168.1.2
$ eg2_impl -BOAiiop_port 12345

The -BOAiiop_name_port is a new option in 2.8.0. I suggest you past the
hostname to omniNames via OMNIORB_USEHOSTNAME.

The problem here is that with DHCP, you may not know what IP address your
machine has been assigned so manually setting the host name is not ideal.

If you want to investigate how to modify the code to work around your
problem, have a look at
<top>/src/lib/omniORB2/orbcore/tcpSocketMTfactory.cc,
the ctor of tcpSocketIncomingRope.

Sai-Lai


>>>>> ryan tecco writes:

> I am having trouble working with getting the BOA to initialize on the
> various laptops that our group works with. None of these laptops have
> hostnames registered with DNS and all of them use DHCP for IP
> configuration. Running 'omniNames -start 12345' results in a 'BOA_init
> failed, cannot use port 12345'. Port 12345 has nothing running on it,
> other ports result in the same error.

> What is going on?

> Please respond to rtecco@umich.edu, or the list. 



-- 
Sai-Lai Lo                                   S.Lo@uk.research.att.com
AT&T Laboratories Cambridge           WWW:   http://www.uk.research.att.com 
24a Trumpington Street                Tel:   +44 1223 343000
Cambridge CB2 1QA                     Fax:   +44 1223 313542
ENGLAND