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: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
