[Mulgara-dev] [Topaz-dev] connecting to mulgara on remote server requires allowing connections to a random high port
Amit Kapoor
amitkapoor at mindspring.com
Tue Apr 22 23:35:13 UTC 2008
Hi Ronald,
On Tue, Apr 22, 2008 at 04:27:46PM -0700, Ronald Tschalär wrote:
[snip]
> > I think there are two ways:
> >
> > 1. iptables (or a proxy) is able to sniff the randomly assigned port in the
> > return data from the RMI registry and opens that to the world. I did a
> > google search and did not find anything here. Maybe others on the list
> > know of a better solution.
> >
> > 2. Mulgara fixes the port it allocates to the server object registered with
> > the RMI registry. Looks like fairly simple to do with
> > UnicastRemoteObject, but not knowing Mulgara code I don't know if there
> > is a catch here. Ronald, Paul, Andrae?
>
>
> I took a quick lok into mulgara, and I think it would end up being a
> couple days work to make the port used for the rmi calls configurable.
> Supposedly all UnicastRemoteObjects can use the same port, and some
> say even the same port as the registry is on. The only really tricky
> thing is that I think the backup/load operations export an RMI object
> from the client to the server, so the client stuff needs a port config
> too and the firewall needs to be opened in the reverse direction (this
> client-object isn't very nat friendly, btw...)
I will open a ticket on Mulgara and based on progress on existing work
items can discuss when this can be done.
regards
More information about the Mulgara-dev
mailing list