Hello Scott. I see that Gnutella server works correctly now. Current Kaboodle version has VPN bug: it's impossible to make remote connection via Gnutella server. But previous Kaboodle version from September 25 works correctly. I see that current Kaboodle version uses ZeBeDee component. Please inform me about your specification: how ZeBeDee component works in the process of remote connection (if ZeBeDee used in above). - Igor
----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: "Igor Kotelevsky" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, November 07, 2002 8:12 PM Subject: Re: VPN bug > Igor: > I checked, and the Gnutella server did go down. I was > working with it during my VPN tests, so it died between then > and now. I've restarted it. I'm surprised that the "Handshake > OK" message didn't report that the server was down. Shouldn't > it say something like "Server Unavailable"? > > To clarify: the Gnutella service on 66.123.20.59 > listens on port 4183. It doesn't listen to port 4182. Kaboodle, > on the other hand, doesn't listen to 4183. It listens to port > 4182, for the exchange of VPN Control Channel data. It's > unfortunate that the port numbers are consecutive, because it > causes confusion. > > Testing your recent commits now. > > thanks, > Scott > > On Thu, 7 Nov 2002, Igor Kotelevsky wrote: > > > Hello Scott. > > I see that bug also. I think that Gnutella server have a problem. > > Please see my arguments. > > I tested the previous Kaboodle version from 25 september and > > it have the bug also. > > Then I tested our little utility *TestGnuSock* and > > it show that Gnutella server doesn't works correctly now. > > In your e-mail you say about 2 numbers of Gnutella port: #4182 and #4183. > > As I know there is one #4183 in the Kaboodle source code. > > But I tested *TestGnuSock* for both numbers. > > Here is the result: > > // BEGIN OF TEST > > 0 Connect( IP address "66.123.20.59", port 4183 ), > > Date: November 07 2002 year, 14 hours 00 minutes > > 1 CGnuSock receives notification <OnConnect( ErrorCode = 10061, > > No connection could be made because > > the target machine actively refused it. )> > > > > 0 Connect( IP address "66.123.20.59", port 4182 ), > > Date: November 07 2002 year, 14 hours 10 minutes > > 1 CGnuSock receives notification <OnConnect( ErrorCode = 10060, > > A connection attempt failed because the connected party did not properly > > respond after a period of time, > > or established connection failed because connected host has failed to > > respond. )> > > // END OF TEST > > > > I implemented some little things for *TestGnuSock*. > > Now it shows a date of test. > > Also there possible to save result of test into the file. > > All my changes are in the CVS server. > > > > - Igor > > > > > > ----- Original Message ----- > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Wednesday, November 06, 2002 8:43 PM > > Subject: Re: VPN bug > > > > > > > Igor: > > > Looking at my LAN traffic after I hit the "Connect" > > > button, I'm not sure that the discovery is working. I don't > > > see any traffic exchanged between the two endpoints. What I > > > *do* see is the request to Gnutella.GetEngaged.Net, and then > > > multiple requests to the IP address in the Partnership file. > > > Then, in my VPN status window, that IP address is now shown > > > as a Gnutella server with a "Handshake OK" status. > > > > > > Here's what I think: every time I successfully make > > > a connection to a VPN partner, I should put their IP address > > > into a file, or registry entry. When I next try to connect > > > with them, I should try those IP addresses *first*, on port > > > 4182, bypassing Gnutella completely. If they fail to connect, > > > I should fall back to a Gnutella search. > > > > > > Of course, the first time I connect with a Partner, > > > I won't have such a file or registry entry. In that case, I > > > should use the IP address in the Partnership file first. If > > > that fails, then fallback to Gnutella. > > > > > > Importantly: those IP address I try should *not* end > > > up in the list of Gnutella servers. I should not see any traffic > > > to port 4183 except to machines in the list of Gnutella servers. > > > > > > hope this helps, > > > > > > Scott > > > > > > On Wed, 6 Nov 2002, Igor Kotelevsky wrote: > > > > > > > Hello Scott. > > > > I continue VPN bug debugging process. > > > > I know that Kaboodle receives remote network data, > > > > which is *exactly* correct, but GUI 'don't want' to show that data. > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
