[omniORB] omniNames and multiple network interfaces

[ext.erik.yderborg at se.transport.bombardier.com ()]

Hi,

I run omniNames on Solaris, with multiple network interfaces. The primary
IF picked by omniNames by default, is a private one (192.x..), not
accessable from the outside.
To work around this I have realized I need to use -ignoreport and
ORBendPoint (I use port 10111):

omniNames -start 10111 -ignoreport -ORBendPoint giop:tcp:10.9.8.7:10111

My question is: Is it possible to have omniNames work the same way as
above, without supplying the ip hard coded?
This would be useful since omniNames will be run by a script on different
machines.

I have tried '-ORBendPoint giop:tcp::10111', but then omniNames tries to
communicate with its clients on the private ip. This is strange since the
clients connect on the public ip.

Br
Erik


Please consider the environment before you print / Merci de penser ?
l'environnement avant d'imprimer / T?nk p? milj?n innan du skriver ut

_______________________________________________________________________________________________________________

This e-mail communication (and any attachment/s) may contain confidential
or privileged information and is intended only for the individual(s) or
entity named above and to others who have been specifically authorized to
receive it. If you are not the intended recipient, please do not read,
copy, use or disclose the contents of this communication to others. Please
notify the sender that you have received this e-mail in error by reply
e-mail, and delete the e-mail subsequently. Please note that in order to
protect the security of our information systems an AntiSPAM solution is in
use and will browse through incoming emails.
Thank you.
_________________________________________________________________________________________________________________


Ce message (ainsi que le(s) fichier(s)), transmis par courriel, peut
contenir des renseignements confidentiels ou prot?g?s et est destin? ?
l?usage exclusif du destinataire ci-dessus. Toute autre personne est, par
les pr?sentes, avis?e qu?il est strictement interdit de le diffuser, le
distribuer ou le reproduire. Si vous l?avez re?u par inadvertance,
veuillez nous en aviser et d?truire ce message. Veuillez prendre note
qu'une solution antipollupostage (AntiSPAM) est utilis?e afin d'assurer la
s?curit? de nos syst?mes d'information et qu'elle fur?tera les courriels
entrants.
Merci.
_________________________________________________________________________________________________________________


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20111110/ca69e7f9/attachment.htm

[Duncan Grisby]

On Thu, 2011-11-10 at 16:53 +0100,

Post by ext.erik.yderborg at se.transport.bombardier.com ()
I run omniNames on Solaris, with multiple network interfaces. The
primary IF picked by omniNames by default, is a private one (192.x..),
not accessable from the outside.

omniORB has no way to know which of your IP addresses is the one you
want to use, so it picks the first one the OS tells it. In your case,
that's the wrong one...

Post by ext.erik.yderborg at se.transport.bombardier.com ()
To work around this I have realized I need to use -ignoreport and
omniNames -start 10111 -ignoreport -ORBendPoint
giop:tcp:10.9.8.7:10111
My question is: Is it possible to have omniNames work the same way as
above, without supplying the ip hard coded?

The problem is that without telling it the IP address you want, how is
it to know which one to pick?

What you can do is to tell it to publish all its IP addresses in its
IORs, then clients will see all its addresses and can pick the one that
works. Do that with

-ORBendPointPublish "all(addr)"

Post by ext.erik.yderborg at se.transport.bombardier.com ()
I have tried '-ORBendPoint giop:tcp::10111', but then omniNames tries
to communicate with its clients on the private ip. This is strange
since the clients connect on the public ip.

Why is that strange? That is the default endpoint you'd have if you
didn't specify anything, meaning that omniORB picks an address to
publish, and it picks the wrong one for you.

omniNames doesn't connect to its clients -- the clients always connect
to it, using the address details in its object references. If a client
connects on the public IP (using an initial reference) but then receives
a NamingContext back from omniNames, that will have the private IP in
it, and the client won't be able to reach it.

Cheers,

Duncan.