Subject RE: [firebird-support] Zebedee and RemoteAuxPort
Author Alan McDonald
> I am trying to attempt something like the following:
>
> I need to be able to connect to firebird databases on a multitude of
> remote servers using zebedee.
>
> I define the connection strings as:
>
> for remote 1 : localhost/10001:myAlias
> for remote 2 : localhost/10002:myAlias
> etc.
>
> Each server has RemoteAuxPost = 3051 in Firebird.Conf, and starts
> zebedee to listen on ports 3050 and 3051.

RemoteServicePort deals with the main communication port of FB
RemoteAuxPort only deals with the port used for event notification

You seem confused or mistaken here

>
> The client starts zebedee with:
> 10001:<ip-addr of server1>:3050
> 10002:<ip-addr of server2>:3050
> etc.

I run zebedee as a service on both client and server ends so my comments are
based on this setup - not getting the client to manually start zebedee each
time it connects.

each port you specify to zebedee will be associated with a unique port match
to a remote server
in the client.zbd file you make entries such as
tunnel 3053:<ip-addr of server1>:3050
this tells the client service to redirect comms on port 3053 to the remote
server on zebedee's port but to tell the remote zebedee service to use 3050
inside the firewall.

>
> If I specify to zebedee on the client :
> 3051:<ip-addr of server1>:3051
> Then my application starts up fine on the client when connecting to
> remote1. Without it, I get a message something like "unable to
> create secondary connection".
>
> How should I specify the 3051 port when I want to connect to more
> than 1 server? Our firewalls are VERY strict, and basically only
> open the zebedee default port 11965.
>
> regards, Colin

you need to have your client "tunnel" for each remote server.
on each server end, the zebedee service is running with
redirect 3050 # Firebird default port
or another port if you have configured them to use a different
RemoteServicePort.
On the server end, I think this entry is not needed since the client is
specifying the port to use, but in the event that the client specifies no
port, all requests will redirect to the port specified by this entry on the
server.
Hope this helps

Alan