[omniORB] Using Bidirectional and Nat

[Duncan Grisby]

On Monday 29 March, Scott Robertson wrote:

[...]
> In the log file from the server I see:
> 
> omniORB: Accepted request from giop:tcp:192.168.0.91:52363 to switch to
> bidirectional because of this rule: "* unix,tcp,bidir"
> 
> Which looks good, but when it  tries to make the client call back it 
> looks like it's trying to open a brand new connection.
> 
> omniORB: Client attempt to connect to giop:tcp:172.16.170.128:32789
> 
> Which then throws a TRANSIENT error because the server does not know how
> to route to 172.16.170.129 (That's the address behind the firewall). 

The problem wasn't that it didn't work with the NAT, it was that
omniORBpy didn't work with bidirectional at all. I've fixed it in CVS.
You need to update both omniORB and omniORBpy.

Thanks for the bug report.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --