[omniORB] omniorb configuration multiple network cards

[Wernke Zur Borg (external)]

The normal endPoint option is sufficient if you expect clients to
connect only on one interface. The ORB will then listen only on this
interface and encode the related endpoint into all IORs. The
endPointPublish option can be used to publish a certain endpoint but to
listen on all interfaces.
 
This business only gets tricky if you have clients on both interfaces,
which have no connectivity to the "other" interface. I could solve this
with an interceptor, which can tweak outgoing IORs depending on which
client they are dedicated for. But this solution is not portable.
 
Regards, Wernke
 


________________________________

	From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Luke
Deller
	Sent: 15 January 2010 09:52
	To: 'jenskristianvilladsen at gmail.com';
'omniorb-list at omniorb-support.com'
	Subject: Re: [omniORB] omniorb configuration multiple network
cards
	
	

	Hi Michiel,
	
	I have seen a problem just like this too. By default omniorb
will bind to all interfaces, which is what we want. The problem is the
IP address which is placed into object references: by default omniorb
will pick the IP address of the first interface it finds, which in my
case was the wrong one. Object references sent to the client did not
work for the client because it could not access the IP address contained
within the object reference.
	
	To resolve the issue, I used the endPointPublish configuration
option to control which IP address was placed into object references
(see the documentation for how to use this option).
	
	Regards,
	Luke.
	

	
________________________________

	From: omniorb-list-bounces at omniorb-support.com 
	To: omniorb-list at omniorb-support.com 
	Sent: Fri Jan 15 18:23:45 2010
	Subject: Re: [omniORB] omniorb configuration multiple network
cards 
	

	

	I have had the same problem when adding extra network card. It
seems that it binds to either one of them or some global network. Try
disable one of the network card and try it once more. I am aware that it
is not a solution, just a fix
	
	On 14-01-2010 10:50, Michiel Soede wrote: 

		Hi,
		 
		I'm using a corba servers using omniorb 4.1.2 on a
debian (amd64) linux system.
		A Windows PC (also using omniorb 4.1.2) client is
communicating with it.
		 
		Recently I added a second ethernet card, and the client
cannot find the server anymore.
		 
		what could be wrong?
		 
		best regards,
		Michiel
		 
		 
		
		
________________________________

		Hotmail: Trusted email with powerful SPAM protection.
Sign up now. <http://clk.atdmt.com/GBL/go/196390707/direct/01/>  
		
		_______________________________________________
		omniORB-list mailing list
		omniORB-list at omniorb-support.com
	
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
		  


	
************************************************************************
**********************
	Important Note
	This email (including any attachments) contains information
which is confidential and may be subject to legal privilege.  If you are
not the intended recipient you must not use, distribute or copy this
email.  If you have received this email in error please notify the
	sender immediately and delete this email. Any views expressed in
this email are not necessarily the views of IRESS Market Technology
Limited.
	
	It is the duty of the recipient to virus scan and otherwise test
the information provided before loading onto any computer system.
	IRESS Market Technology Limited does not warrant that the
information is free of a virus or any other defect or error.
	
************************************************************************
**********************

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