VK:
Heya. Some replies (Igor, please see the question to you
below):
> > 0. As soon as the user on PC1 clicks "Connect" in the VNC Window,
> > a Zebedee server needs to be started on PC3. Arguably, this server
> > should be started as soon as a VPN is started: why else initiate
> > a VPN unless you want to do something with it, right? Anyhow...
> > PC2 uses the Kaboodle control channel to tell PC3 to activate a
> > Zebedee server that's ready to do whatever it, as the Zebedee client,
> > tells it to do. The easiest thing to do on PC3 is just this:
> >
> The Zebedee server should run as soon as the VPN is started.
> The problem here is that the zebedee server needs the targethost
> machine otherwise it redirects all incoming data to ports on the local
> machine. We need to enable the "Allow loopback connection" for the VNC
> server if the target machine is same as the zebedee server machine.
You're right about the targethost. For now, to get things
working, I believe you can use "0.0.0.0/0" as the targethost: that
should allow Zebedee on PC3 to connect to anything anywhere. Long
term, the target hose should look something like "a.b.c.0/24" which
is the Class-C address range of PC3, where a.b.c.d is the IP address
of PC3. But please test it with 0.0.0.0/0.
Igor: from the LAN detection stuff, is there a function that
VK can use which returns all of the "active class-C ranges" known to
the Kaboodle Master node? It's the same range that Kaboodle is active
ping'ing when the user hits "Refresh". This result of this function
should take into account multiple interfaces as well, so it might
return "a.c.d.e/24", "f.g.h.i/24" and "j.k.l.m/24" where the first
two are on one interface, and the third is on another interface.
If VK had a function like this, we could put those IP ranges
into the targethost specification for Zebedee.
VK: you may be right about the loopback -- we should see what
happens when its running.
> On Pc3 we will create a shared key and pass it to the PC2 through VPN tunnel.
>
> But I could not create the shared key with the command sharedkeygencommand.
No biggie: you can use Kaboodle to generate a random 32-digit
hexadecimal value.
> We need to change the zebedee server listening port.
>
> Where will the user specify the port for zebedee server in the
> application? If you could tell the exact location I will add it and pass
> that information through the VPN tunnel.
The approximate location will be some fill-field in the VPN
Service icon somewhere, probably at the bottom of the page where the
user hits the "Connect" button.
Lastly...I'm not sure about the "checkaddress" feature right
now. It worries me because it prevents multiple simultaneous VPNs:
if I'm VPN'd with partner-A, I'd have to restart the Zebedee server
to start a session with partner-B. If partner-A was connecting to a
VNC session, is Zebedee smart enough to restart itself without
disrupting the VNC session? I doubt it. If we could get the "sharedkey"
part working well enough, I suppose I could live without checkaddress.
-Scott
-------------------------------------------------------
This SF.NET email is sponsored by: AMD - Your access to the experts
on Hammer Technology! Open Source & Linux Developers, register now
for the AMD Developer Symposium. Code: EX8664
http://www.developwithamd.com/developerlab
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
