Igor:
Ah! It was a registry setting, of course. Version 0.72
must have set "GnutellaServer" with the Installer. Good find!
Your changes sound like good ones, though you *may* want to
have the IP address (66.123.20.59) be a registry setting as
well. So, "GnutellaServer" and "GnutellaServerDefaultIP"
perhaps. That will make things easier to change if I ever have
to change ISP's here.
Regarding "bug #5", I am not sure why this doesn't
work. PC1_IP and PC2_IP in the Partnership files should just
be treated as "suggestions" to the Partner Discovery process,
not treated as "the right answer". If the process fails to
find a partner in this manner, it should fall back to the
Gnutella search.
Longer term, I will be adding other pieces to this
process. For instance, after a Partnership is established, the
IP addresses of that connection should be saved for use next
time, as "suggestions". Or, if I ever get the dynamic-DNS
client part into the code, we can add that to the process
(I'm not asking you to make these changes now, I'm just
speaking about the future). So, right now, the process has to
be able to handle:
1. Start Discovery process using A, B, C where A,B,C are all
IP address "suggestions". Some of them may even be running
Kaboodle, but none have the right PartnershipFile.
2. If #1 fails to find the PartnershipFile, fall back to a
Gnutella search using the list of servers in the
"GnutellaServer" registry entry.
3. If #3 fails to find the PartnershipFile, report failure.
Hope this makes sense!
cheers,
Scott
On Thu, 18 Apr 2002, Igor Kotelevsky wrote:
> Hello Scott.
> Today I continued working on Kaboodle remote connection bug.
> I have found the following.
> Please see the file VPNModule\VPNManager.cpp, the function BOOL
> CVPNManager::StartConnection( CGUID& KaboodleID ).
> In this function Kaboodle tries to read string value "GnutellaServer" from
> Kaboodle registry key.
> But this value is absent. Both Kaboodle and GetEngaged do not create the
> above value.
> Therefore result of this reading is always an empty string.
> Then Kaboodle tries to get IP address of this string by calling function
> GetIPByName().
> The string is empty so Kaboodle gets its own IP address.
> This IP address is used as parameter when connecting to Gnutella.
> Earlier you wrote:
> > 3. Looking in the Gnutella.log file, it appears to be connecting
> > not to gnutella.getengaged.net, but to itself. That can't
> > be right. :) It *should* show in this file that it's connected
> > to the remote server, shouldn't it?
> Now we understand why this occurs.
>
> I have expected that in the registry value "GnutellaServer" there must be
> the string "Gnutella.GetEngaged.Net".
> (Earlier you wrote:
> > So I'm sure, which .cpp file should contains the phrase
> > "Gnutella.GetEngaged.Net"? I cannot seem to find it. )
>
> Therefore I have changed this part of source code as follows.
> If Kaboodle failed to read value "GnutellaServer", then Kaboodle creates one
> and using the default
> "Gnutella.GetEngaged.Net".
> If Kaboodle failed to get IP address of this string by calling function
> GetIPByName(), then Kaboodle uses
> the default IP "66.123.20.59".
> My changes of source code already inhere in CVS server.
>
> Yesterday I wrote:
> > I have executed the following steps.
> > 1) Register two Kaboodles.
> > I have PC1 IP address - PC1_IP, and PC2 IP address - PC2_IP.
> > 2) Download Registration and PartnerShip files.
> > Register the above files via GetEngaged.exe.
> > 3) Try remote connection.
> > Remote connection works cool.
> > 4) Then I swap the two IP addresses.
> > Now I have PC1 IP address - PC2_IP, and PC2 IP address - PC1_IP.
> > 5) Try remote connection. It fails.
>
> Here bug #5 is repeated.
> Do you think the case described in #4 is typical in real life? I do not.
> Please let me know what you think on #4.
>
> Please send you mail to me [EMAIL PROTECTED] and replicate it to
> Alexander [EMAIL PROTECTED]
>
> - Regards, Igor
>
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, April 16, 2002 9:30 PM
> Subject: Re: "Text of your message" is my understanding...
>
>
> > Igor:
> > I couldn't find it either. That's what worries me.
> > Kaboodle is not doing the 4-step process described below. It
> > is only doing the first 2 steps, and then it stops. I need
> > it to do all 4.
> >
> > The work priority should be to fix this, then to
> > implement the changes to the VNC tunneling from last week.
> > Please let me know how long you think those two projects will
> > take. I had been thinking that you would be able to work on
> > these two, and then implement the push-based file transfer.
> > But we seem to be stuck on Partner Discovery.
> > Anyhow, please let me know when you can.
> >
> > thanks,
> > Scott
> >
> >
> > On Tue, 16 Apr 2002, Igor Kotelevsky wrote:
> >
> > > Hello Scott.
> > > I don't know which .cpp file contains the phrase
> "Gnutella.GetEngaged.Net".
> > > I know that file UI\RemoteNetworkPage.cpp contains the phrase
> > > "http://www.getengaged.net"; .
> > > - Regards, Igor
> > >
> > > ----- Original Message -----
> > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > Sent: Tuesday, April 16, 2002 12:02 PM
> > > Subject: Re: "Text of your message" is my understanding...
> > >
> > >
> > > > Igor:
> > > > Hello! I've just downloaded the latest snapshot in the
> > > > CVS. So I'm sure, which .cpp file shoul contains the phrase
> > > > "Gnutella.GetEngaged.Net"? I cannot seem to find it. Or perhaps
> > > > you've not finished #3 below?
> > > > Thanks!
> > > >
> > > > -Scott
> > > >
> > > > On Mon, 15 Apr 2002, Igor Kotelevsky wrote:
> > > >
> > > > > Hello Scott.
> > > > >
> > > > > I confirm that "text of your message" is my understanding of the
> > > > > intended operation of VPN partner discovery.
> > > > >
> > > > > > Try this: turn Kaboodle off on PC2, and try to connect
> > > > > > from PC1. The second time you try, it will report "Initiating
> > > > > > Remote Network Search". Actually, it will first report the
> > > > > > "Direct Connection..." splash screen, which sometimes appears
> > > > > > at position 0,0 in the window, not centered. Anyhow...
> > > > >
> > > > > I can not reproduce bug
> > > > > > ..."Direct Connection..." splash screen, which sometimes appears
> > > > > > at position 0,0 in the window, not centered...
> > > > > But I has written certain additional code on this cause.
> > > > > Please inform me if this bug is repeated.
> > > > >
> > > > > Earlier I has found and has corrected following bug of "Searching
> for
> > > > > Partnership file..." splash screen.
> > > > > If user clicks or parental PropertyTab "Remote Networks" or the main
> > > > > Kaboodle window,
> > > > > that above splash screen will become in Z-order below and will be
> > > hidden.
> > > > >
> > > > > My changes of source code already inhere in CVS server.
> > > > >
> > > > > - Regards, Igor
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > > > > Sent: Friday, April 12, 2002 8:36 PM
> > > > > Subject: Re: [Kaboodle-devel] Re: 8-April status (2 of 2)
> > > > >
> > > > >
> > > > > > Igor:
> > > > > >
> > > > > > Hello! Two important comments:
> > > > > >
> > > > > > > > 1. First, when I use Connect the first time, I see "Searching
> > > > > > > > for Partnership File....". It takes ~3 seconds to popup
> > > > > > > > after I hit the Connect button, but it works. The second
> > > > > > > > time, though, it reads "Initiating Remote Network
> Search...".
> > > > > > > > This suggests there's two different things going on?
> > > > > > >
> > > > > > > This is old part of source.
> > > > > > > It seems to me that this depends on what machine first initiates
> > > > > > > connection.
> > > > > >
> > > > > > Actually, this is an important point: I'm only testing
> > > > > > with one side of the connection trying to initiate a connection.
> > > > > > I'm working on PC1, I leave PC2 alone with Kaboodle running. I
> > > > > > never touch PC2 after I install the appropriate Partnership file.
> > > > > >
> > > > > > Try this: turn Kaboodle off on PC2, and try to connect
> > > > > > from PC1. The second time you try, it will report "Initiating
> > > > > > Remote Network Search". Actually, it will first report the
> > > > > > "Direct Connection..." splash screen, which sometimes appears
> > > > > > at position 0,0 in the window, not centered. Anyhow...
> > > > > >
> > > > > >
> > > > > > > > 3. Looking in the Gnutella.log file, it appears to be
> connecting
> > > > > > > > not to gnutella.getengaged.net, but to itself. That can't
> > > > > > > > be right. :) It *should* show in this file that it's
> connected
> > > > > > > > to the remote server, shouldn't it?
> > > > > > <snip>
> > > > > > > Kaboodle on PC1 have valid IP address.
> > > > > > > Kaboodle on PC2 have chanded IP address.
> > > > > > > Users on both Kaboodles push "Connect" button.
> > > > > >
> > > > > >
> > > > > > Ah! Okay, here's why we're speaking past each other: the
> > > > > > VPN needs to work if only *one* Kaboodle user pushes the Connect
> > > > > > button.
> > > > > > Here's the process I need to work. In this example, both
> > > > > > PC1 and PC2 have a Partnership file for the other guy installed,
> > > > > > but in both cases the IP address has changed:
> > > > > >
> > > > > > 0. User on PC1 starts Kaboodle. Its Gnucleus client needs a
> > > > > > startup server: it connects to Gnutella.GetEngaged.Net and
> > > > > > reports an error if it cannot. User on PC2 does the same
> > > > > > thing. I'm absolutely certain this is how it used to work.
> > > > > > The startup server may have been called "gnutella.echogent.com"
> > > > > > back then (I'm checking my old source code snapshots now).
> > > > > > 1. User on PC1 pushes "Connect". Kaboodle on PC1 should first
> > > > > > try a direct connection to PC2 via the IP-address-2 it reads
> > > > > > from the Partnership file.
> > > > > > 2. Since PC2's IP address has changed, #1 will not work. It should
> > > > > > timeout in 5 to 10 seconds.
> > > > > > 3. Kaboodle on PC1 then queries Gnutella.GetEngaged.Net looking
> > > > > > for PC2's Partnership file. Since PC2's Gnucleus client has
> > > > > > connected to this server as well, the search *should* be
> > > > > > successful.
> > > > > > 4. If the search is successful, Kaboodle on PC1 now has the
> > > > > > current, active IP address of Kaboodle on PC2. It can now
> > > > > > connect.
> > > > > >
> > > > > > Please confirm that this is you understanding of the
> > > > > > intended operation of VPN partner discovery.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > -Scott
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
