[omniORB] incorrect IP address after update to SuSE 11.1

[Duncan Grisby]

On Wednesday 15 April, Nikolas Kauer wrote:

> After the sysadmin updated machines to SuSE 11.1, the
> server/client produces an IOR string with incorrect IP
> address but correct port number:
> 
> $ catior IOR:010000001300000049444c3a4f6d6e69576f726b65723a312e300000010000000000000060000000010102000a0000003132372e302e302e32008eb70e000000fede1de64900006d4c000000000000000200000000000000080000000100000000545441010000001c00000001000000010001000100000001000105090101000100000009010100
> Type ID: "IDL:OmniWorker:1.0"
> Profiles:
> 1. IIOP 1.2 127.0.0.2 46990 "....I..mL....."
>             TAG_ORB_TYPE omniORB
>             TAG_CODE_SETS char native code set: ISO-8859-1
>                           char conversion code set: UTF-8
>                           wchar native code set: UTF-16
>                           wchar conversion code set: UTF-16
> 
> On SuSE 10.x systems this problem does not occur.  We have
> been using omniORB-4.0.7, so far without any problems (Thanks,
> Duncan!).  We checked that the following holds also on the
> SuSE 11.1 systems: The correct IP address is returned by
> "nslookup <hostname>", "hostname -i" and "/sbin/ifconfig -a".
> /etc/hosts does not contain 127.0.0.2.

Please run with -ORBtraceLevel 25 and send the output.

> Section 8.6 of the omni40 docs states "If the host is empty, the
> ORB published the IP address of the first non-loopback network
> interface it can find (or the loopback if that is the only
> interface), ..."  How does this actually work?

omniORB asks the OS for all its IP addresses, and picks the first one
that is not 127.0.0.1. You strangely have an address of 127.0.0.2, so if
that is the first one in the list, omniORB will pick that.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --