Re: Multiple server connections

Why can't you have one Zebedee process running on one server machine in 
the main office, forwarding traffic to the other servers?  As long as 
they are on the same subnet, or you have your routing configured 
correctly, it should work.  It does for me.

For example.
Here is a portion of a sample server.zbd file on one of your servers in 
the main office, say this server is 10.10.1.1.  I've removed all lines 
that don't help to explain the setup.

server true                  # Yes, it's a server!
serverport 5000              # Listen on this port.
                              # Need hole in firewall.
checkidfile 'clients.id'     # Pre-shared keys in this file
redirect 22                  # SSH
target 10.10.1.1:22/tcp      # SSH on 10.10.1.1
target 10.10.1.2:22/tcp      # SSH on 10.10.1.2
target 10.10.1.3:22/tcp      # SSH on 10.10.1.3
target 10.10.1.4:22/tcp      # SSH on 10.10.1.4


Then, each client will be set up as so...

Client1:
serverport 5000              # Port that zebedee talks on.
serverhost my.office.domain  # Where is the server listening?
                              # Needs DNS or hosts file.
tunnel 5022:10.10.1.1:22     # SSH on 10.10.1.1

Client2:
serverport 5000              # Port that zebedee talks on.
serverhost my.office.domain  # Where is the server listening?
                              # Needs DNS or hosts file.
tunnel 5022:10.10.1.2:22     # SSH on 10.10.1.2

Client3:
serverport 5000              # Port that zebedee talks on.
serverhost my.office.domain  # Where is the server listening?
                              # Needs DNS or hosts file.
tunnel 5022:10.10.1.3:22     # SSH on 10.10.1.3

Client4:
serverport 5000              # Port that zebedee talks on.
serverhost my.office.domain  # Where is the server listening?
                              # Needs DNS or hosts file.
tunnel 5022:10.10.1.4:22     # SSH on 10.10.1.4

So, there you have one server in the home office, running one Zebedee 
process, forwarding SSH traffic to four different servers.  You'll need 
a key for each client on the server.  I use pre-shared keys.  They can 
be added and removed without stopping the Zebedee process.  Just edit 
the clients.id text file as needed.

I hope this helps.
Please cheerfully ignore if I've misunderstood your requirements...

Thanks,
    Tom Sneddon


Gam wrote:
 > /
 > /
 > Hi all,
 > I have started using ZBD to handle ssh tunnels between our main 
office to our different kiosks installed in different places around 
Singapore. Each kiosk has its ADSL line.
 >
 > I have found out that a client can only connect to ONE server (if 
serverhost is not specified, the first host of a tunnel is taken...)
 >
 > I would like to have one client configuration file + process running 
in the office instead of a file+process couple per kiosks (which becomes 
quite ugly when you reach a number of 10 kiosks...).
 >
 > My questions are:
 > - Do you confirm there is NO way to specify tunnels for the client to 
connect different servers (even sequentially if not parallel) with 
something like:
 > tunnel  serverhost  localport:targethost:targetport
 >
 > - If no, is there any chances that multi-server support is on its 
way? any other suggestion?
 >
 >
 > Thanks for your answers,
 > Best Regards,
 > Gam.
 >

...


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642