[omniORB] omniNames (and nameclt) problem with multiple enthernet interfaces on AIX

[Tomasz Bech]

Hi all,
It could be connected with my previous mail, maybe not.
We have installation on AIX 5.2 with 3 ethernet interfaces.
Only one of ethernet interface is routing to the client machine, and it 
is not the first in the interface list.
We tried houndrets of configuration and cannot make omniNames and 
nameclt working.

The problem is here : (log from nameclt )
omniORB: Client opened connection to giop:tcp:172.16.94.1:2000
omniORB: sendChunk: to giop:tcp:172.16.94.1:2000 100 bytes
omniORB:
4749 4f50 0100 0000 0000 0058 0000 0000 GIOP.......X....
0000 0002 0100 0000 0000 000b 4e61 6d65 ............Name
5365 7276 6963 6500 0000 0006 5f69 735f Service....._is_
6100 0000 0000 0000 0000 0028 4944 4c3a a..........(IDL:
6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
672f 4e61 6d69 6e67 436f 6e74 6578 743a g/NamingContext:
312e 3000                               1.0.
omniORB: inputMessage: from giop:tcp:*172.16.94.1*:2000 25 bytes
omniORB:
4749 4f50 0100 0001 0000 000d 0000 0000 GIOP............
0000 0002 0000 0000 01                  .........
omniORB: Creating ref to remote: key<0x4e616d6553657276696365>
 target id      : IDL:omg.org/CosNaming/NamingContext:1.0
 most derived id:
omniORB: sendChunk: to giop:tcp:172.16.94.1:2000 60 bytes
omniORB:
4749 4f50 0100 0000 0000 0030 0000 0000 GIOP.......0....
0000 0004 0100 0000 0000 000b 4e61 6d65 ............Name
5365 7276 6963 6500 0000 0005 6c69 7374 Service.....list
0000 0000 0000 0000 0000 0000           ............
omniORB: inputMessage: from giop:tcp:172.16.94.1:2000 218 bytes
omniORB:
4749 4f50 0100 0001 0000 00ce 0000 0000 GIOP............
0000 0004 0000 0000 0000 0000 0000 002a ...............*
4944 4c3a 6f6d 672e 6f72 672f 436f 734e IDL:omg.org/CosN
616d 696e 672f 4269 6e64 696e 6749 7465 aming/BindingIte
7261 746f 723a 312e 3000 392e 0000 0001 rator:1.0.9.....
0000 0000 0000 0082 0001 0200 0000 000e ................
3132 392e 3138 342e 3939 2e31 3700 07d0 *129.184.99.17*...
0000 000e ff00 40ad a9e7 7800 0001 0000 ...... at ...x.....
0002 0000 0000 0003 0000 0000 0000 0008 ................
0000 0000 4154 5400 0000 0001 0000 001c ....ATT.........
0000 0000 0001 0001 0000 0001 0501 0001 ................
0001 0109 0000 0001 0001 0109 0000 0003 ................
0000 0016 0000 0000 0000 000c 3137 322e ............172.
3136 2e39 342e 3100 07d0                16.94.1...
omniORB: Creating ref to remote: root/<....x.......>
 target id      : IDL:omg.org/CosNaming/BindingIterator:1.0
 most derived id: IDL:omg.org/CosNaming/BindingIterator:1.0
omniORB: LocateRequest to remote: root/<....x.......>
throw giopStream::CommFailure from 
giopStream.cc:1061(0,NO,TRANSIENT_ConnectFailed


But if we add routing to *129.184.99.17* is goes on as:

omniORB: Client opened connection to giop:tcp:129.184.99.17:2000
omniORB: sendChunk: to giop:tcp:129.184.99.17:2000 38 bytes




Configuration:
omniNames is started on machines which have 3 ip :
129.184.99.17
172.16.94.1
127.0.0.1
*
*We need to use 172.16.94.1. However the omniNames are started (with 
endPoint giop:tcp:172.16.94.1 or just giop:ip::)
the nameclt is redirected to the 129.184.99.17 and fails.
Could you explain me what is a meaning of ip sent in this GIOP chunk:
4749 4f50 0100 0001 0000 00ce 0000 0000 GIOP............
0000 0004 0000 0000 0000 0000 0000 002a ...............*
4944 4c3a 6f6d 672e 6f72 672f 436f 734e IDL:omg.org/CosN
616d 696e 672f 4269 6e64 696e 6749 7465 aming/BindingIte
7261 746f 723a 312e 3000 392e 0000 0001 rator:1.0.9.....
0000 0000 0000 0082 0001 0200 0000 000e ................
3132 392e 3138 342e 3939 2e31 3700 07d0 *129.184.99.17*...
0000 000e ff00 40ad a9e7 7800 0001 0000 ...... at ...x....
------

What ip it is:
the omniNames or the client which where bound?
if omniNames, why the undesired ip is put instead of specified in the 
endPoint?
I'm using 4.0.2.
How to go on?
Thanks,
    Tom