Re: {bb} Networking -- not sure what to call it

[Frank Fegert <fra.nospam.nk@gmx.de>]

Almost ;-) It boils down to something like this:

On the master BB4-Server:

ssh -fnNR 1984:`hostname`:1984 client1
ssh -fnNR 1984:`hostname`:1984 client2
ssh -fnNR 1983:`hostname`:1984 relay1

This tunnels the communication between the master server and its
clients from 1984 (client side) to 1984 (server side). Plus the
communication between the relay/slave server and the master server
is tunneled from 1983 (relay side) to 1984 (server side).

Because of the redirection of the relayed traffic "slave BB4 to
master BB4" to port 1983 on the slave tunnel-end the slave BB4
can still listen to port 1984 for its own clients:

ssh -fnNR 1984:`hostname`:1984 client1
ssh -fnNR 1984:`hostname`:1984 client2

Plus you don't have to tweak the master BB4 end, because its end
of the tunnel is at 1984. This saves a lot of headache, with having
the master BB4 cope with two ports.

If anyone is interested i could post some patch files with the
necessary modifications to the BB4 sources.

HTH & Regards,

	Frank


Misty Stanley-Jones wrote:
> OK, based on the snip below, I need to change not the normal BB port, but the 
> BBRELAY port?  Then I will need to change the remote port for the SSH tunnel 
> as well?
>
> On Saturday 29 May 2004 03:26 am, Frank Fegert wrote:
>
>
> > Admittedly there is some fiddling, if you have one "master"
> > BBDISPLAY and some "slave" BBDISPLAYs relaying to the master
> > plus clients at the master AND the slave(s). This is since
> > you can't have the ssh-tunnel and the bb-process both listen
> > to the same port at the slave BBDISPLAY. So i did a quick &
> > dirty hack to the bb sources to have bb send the relying
> > information to another port, at which the ssh-tunnel-end is
> > listening.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.