Oleg:
        Hello! I'm trying to understand what the Kaboodle+VNC
limitations are right now:

> > Also, I wanted to confirm: suppose host-A and host-B are on
> > my LAN, and host-C and host-D are on a remote LAN. Hosts A, B and
> > ...
> > tunneling work you've done smart enough to allow this to work:
> >
> >   A (VNC client) => B (Kaboodle) => C (Kaboodle) => D (VNC server)
>
> I am afraid this feature was not mentioned in the initial specification
> and so it is not currently implemented.

        Right, the diagram is not exactly correct. It's actually:

   A (K+VNC client) => B (Kaboodle) <=> C (Kaboodle) => D (VNC server)
   {                               }   {                              }
    ---------- LAN 1 ---------------    ----------- LAN 2 -------------

        So, machine-A *does* run both Kaboodle and a VNC client. It's
just the server, machine-D, that doesn't. This is actually in the spec,
in section 4.1: "UPDATE: the VNC viewer is installed on the same PC
running Kaboodle, and the Kaboodle-GUI directives are interpreted to
initiate this viewer. However, the target VNC server *may* be a machine
thats a peer with a PC running Kaboodle".
        As you can see, machine-D is a peer with machine-C that's
running Kaboodle.

> which would be useful to connect several computers on a LAN each
> running VNC Server to a remote Kaboodle machine through just one
> Kaboodle gate resident on the LAN. This feature may be added as a
> future enhancement.

        So how close are we now to what I just described above?
Can Kaboodle *only* act as a gateway to a VNC server if that server
is running on the same machine as Kaboodle? If so, then it's already
re-addressing packets to have a dest-IP of 127.0.0.1 (loopback). To
be a real gateway, Kaboodle would simply need to be able to re-address
packets to anything on its own LAN as well as the loopback. Based
on the user-actions in the GUI, it would "know" what IP address to
use.
        In general, Kaboodle MUST be able to act as a gateway to
services running on non-Kaboodle machines. That's its whole reason
for being. It's sounds like we missed the target a little bit;
please let me know by how much!


-Scott


_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to