Imran:
Hello! Some answers:
> This is Imran from Spsoft, we had just tested the VPN capabilities
> again, Now what we are considering is that we are going to implement
> NAT module which will allow user communicate between PC1 of LAN 1 with
> PC2 of LAN 2 through VPN end point of both LAN's
>
> LAN 1
> --------------------------- VPN Tunnel----------------------------
> | PC1 ------ VPN Endpoint |<------->| VPN End Point ------PC2 |
> |-------------------------- | |___________________________|
>
> We considered that all the PC's in both LAN including VPN End point are
> running Kaboodle
> do you want any please contact as soon as possible.
Please refer to the spec in regards to the VPN End Point
requirements regarding which machines are running Kaboodle to
be able to use the tunnel. I can summarize here as well: suppose
PC1 and PC2 are in LAN1 and PC3 and PC4 are in LAN2:
1. Whichever of the two PC's are VPN endpoints (PC1 and PC3,
or PC2 and PC4, etc) *must* be running Kaboodle, clearly.
2. The PC which is initiating the connection that is using
the VPN tunnel also *must* be running Kaboodle. So if I'm
connecting VNC across the connection, from PC1 to PC4, the
VNC session on PC1 is initiated using Kaboodle on PC1.
3. Here's the tricky part: the PC which is receiving the tunneled
connection *may not* be running Kaboodle. For example, PC2
is a VPN endpoint connected with PC3, also a VPN endpoint.
PC4 is a VNC Server and is *not* running Kaboodle. If I'm
running Kaboodle on PC1, I need to be able to initiate a VNC
connection to PC4 that uses the existing tunnel between PC2
and PC3. In this case the process is as follows:
3.a: PC1 uses Kaboodle signaling to tell PC2 that a VNC
connection is requested to PC4.
3.b: PC2 acknowledges PC1, and binds a new TCP port (eg,
port XYZ) to listen for PC1's data.
3.c: PC2 tells PC3 that VNC data is coming destined for
PC4.
3.d: PC3 acknowledges PC2, and confirms it's ready for VNC
data on virtual-channel N of the VPN connection.
3.e: Upon getting a ready signal from PC3, PC2 tells PC1
it's ready, and to connect to its port XYZ.
3.f: PC1 initiates the VNC viewer to connect to PC2's TCP
port XYZ.
3.g: PC2 collects that data and puts it into virtual-channel N
of the VPN connection.
3.h: PC3 takes the data out of that virtual-channel, and
pushes it on to PC4's VNC server. Note that PC4 is *not*
running Kaboodle.
3.i: PC4 responds to this TCP data normally: by replying to
the PC3 TCP port which sent it.
3.j: PC3 collects this response packet, and puts it back into
the VPN virtual-channel back to PC2.
3.k: PC2 takes the data out of the virtual-channel and sends
the packet to the waiting VNC viewer on PC1. That completes
the connection.
Please let me know if this helps clarify. Thanks!
-Scott
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
