Hello Michael,
On 07/06/2011 01:54 PM, Michael Raab wrote:
> we're trying to setup a cluster rendering system that uses windows as
> client and several CentOS linux machines as rendering servers. We have
> some connection problems as client and servers don't find each other.
> This seems to be caused by the CentOS firewall settings, so I need to
> know exceptions we need to setup.
it may not be what you wanted to hear, but can't you simply turn off the
firewall on the CentOS machines? They are hopefully on an internal
network not visible to the outside world anyway?
> May someone summarize shortly how the connection between client and
> server is set up?
> Which protocols and ports are used by default?
it's not completely trivial as it attempts to find servers by name using
multicasts/broadcasts and (unless you specify otherwise) servers simply
bind to an arbitrary local port.
The name resolution defaults to port 8437, but you can change that with
the servicePort argument to the c'tor and specify a multicast group (or
broadcast address) with the serviceGroup argument (see
OSGClusterServer.{h,cpp}, specifically ClusterServer::acceptClient()).
To make a server listen on a specific port for data connections, the
serviceName argument should be "<IP>:<PORT>" and address argument left
empty.
Sorry if this explanations is somewhat unstructured, I'm just reading
the code and trying to put it into words :-/
Cheers,
Carsten
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
