Mike Richmond
2007-07-19 14:41:27 UTC
We've recently moved a product from omniORB 3.0.4 to omniORB 4.1.0
and are observing a change in behaviour.
With 3.0.4 we initialised the orb with "-ORBpoa_iiop_name_port
localhost:1234". Using a port scanning utility we can see port 1234
is open on addresses 0.0.0.0, 127.0.0.1 and the machine's IP address
(say 172.1.2.3).
With 4.1.0 we initialise the orb with "endPoint
giop:tcp:localhost:1234". We now see that port 1234 is open on
addresses 0.0.0.0 and 127.0.0.1, but not on 172.1.2.3. Is this
expected behaviour? Do we need a second endPoint to specify
172.1.2.3? Or should we be using "giop:tcp::1234", which seems to
give the 3.0.4 behaviour?
FWIW we have compiled omniORB 4.1.0 with IPv6 disabled.
Mike Richmond
Global Graphics Software Ltd
and are observing a change in behaviour.
With 3.0.4 we initialised the orb with "-ORBpoa_iiop_name_port
localhost:1234". Using a port scanning utility we can see port 1234
is open on addresses 0.0.0.0, 127.0.0.1 and the machine's IP address
(say 172.1.2.3).
With 4.1.0 we initialise the orb with "endPoint
giop:tcp:localhost:1234". We now see that port 1234 is open on
addresses 0.0.0.0 and 127.0.0.1, but not on 172.1.2.3. Is this
expected behaviour? Do we need a second endPoint to specify
172.1.2.3? Or should we be using "giop:tcp::1234", which seems to
give the 3.0.4 behaviour?
FWIW we have compiled omniORB 4.1.0 with IPv6 disabled.
Mike Richmond
Global Graphics Software Ltd