Igor:
Hello! Some data about the bug:
> > Scott wrote:
> > I've confirmed that in the latest snapshot, Kaboodle
> > does connect to the Gnutella server at gnutella.getengaged.net
> > at startup.
> Hmm... The log file _Gnutella.log_ shows that Kaboodle connect to the
> Gnutella server at gnutella.getengaged.net at startup:
I agree, it connects at startup. Here's how I test it.
On my LAN, next to the WinNT PC running Kaboodle, I run a Linux
box. I use tcpdump to see all of the LAN traffic coming out of
that Kaboodle PC:
tcpdump -n -s 1024 -i eth0 host 192.168.123.130
Where 192.168.123.130 is the IP address of my
Kaboodle PC. At startup, here's what I see regarding Gnutella:
17:15:23.489058 192.168.123.130.2102 > 66.123.20.59.4183: S
3585032766:3585032766(0) win 8192 <mss 1460> (DF)
17:15:23.491903 66.123.20.59.4183 > 192.168.123.130.2102: S
1938556261:1938556261(0) ack 3585032767 win 16060 <mss 1460> (DF)
17:15:23.491952 192.168.123.130.2102 > 66.123.20.59.4183: . ack 1 win 8760
(DF)
17:15:23.493751 192.168.123.130.2102 > 66.123.20.59.4183: P 1:23(22) ack 1
win 8760 (DF)
17:15:23.496289 66.123.20.59.4183 > 192.168.123.130.2102: . ack 23 win
16060 (DF)
17:15:23.504098 66.123.20.59.4183 > 192.168.123.130.2102: F 1:1(0) ack 23
win 16060 (DF)
17:15:23.504148 192.168.123.130.2102 > 66.123.20.59.4183: . ack 2 win 8760
(DF)
17:15:23.513674 192.168.123.130.2102 > 66.123.20.59.4183: F 23:23(0) ack 2
win 8760 (DF)
17:15:23.515995 66.123.20.59.4183 > 192.168.123.130.2102: . ack 24 win
16060 (DF)
Above, 66.123.20.59 is gnutella.getengaged.net, and you
can see the Gnutella service there is listening and responding
from port 4183. So far so good.
> I have restored 2 temporary independent radio buttons "Use Gnutella" and
> "Direct connection"
> in "Remote Networks" PropertyTab.
> Please check radio button "Use Gnutella" and let me know if Gnutella queryes
> server when you hit "Connect" in the VPN panel. (It seems to me it doesn't
> because this old part of source code is general with "Direct connection"
> code.).
> If Gnutella queryes server, then I will test "Direct connection".
> If Gnutella not queryes server, then I will study "Gnutella connection" old
> source code more in detail.
Good idea! Here are the results. When I select "Use Gnutella",
I see this:
17:18:03.931160 192.168.123.130.2103 > 64.136.47.103.4183: S
3625148251:3625148251(0) win 8192 <mss 1460> (DF)
17:18:06.894103 192.168.123.130.2103 > 64.136.47.103.4183: S
3625148251:3625148251(0) win 8192 <mss 1460> (DF)
17:18:12.903220 192.168.123.130.2103 > 64.136.47.103.4183: S
3625148251:3625148251(0) win 8192 <mss 1460> (DF)
17:18:24.921441 192.168.123.130.2103 > 64.136.47.103.4183: S
3625148251:3625148251(0) win 8192 <mss 1460> (DF)
That's a Gnutella search to the IP address that's in
the PartnershipFile: 64.136.47.103. This was with "Use Gnutella"
selected, though! Note that it tries port 4183.
When I try to "Connect" again in the same manner,
I see nothing except the UDP heartbeat pulses:
17:19:05.635114 192.168.123.130.2099 > 255.255.255.255.4082: udp 324
17:19:15.630239 192.168.123.130.2099 > 255.255.255.255.4082: udp 324
17:19:26.052025 192.168.123.130.2099 > 255.255.255.255.4082: udp 324
Once every 10 seconds as you can see from the timestamp.
Very strange that it does something the first time after the
app is started, but differently each time after that. It may
be because Gnucleus has determined that no host is listening
at that IP address.
When I try with "Direct Connect" selected, tcpdump
shows this:
17:23:06.082527 192.168.123.130.2104 > 64.136.47.103.4182: S
3700610711:3700610711(0) win 8192 <mss 1460> (DF)
17:23:09.052413 192.168.123.130.2104 > 64.136.47.103.4182: S
3700610711:3700610711(0) win 8192 <mss 1460> (DF)
17:23:15.061545 192.168.123.130.2104 > 64.136.47.103.4182: S
3700610711:3700610711(0) win 8192 <mss 1460> (DF)
Note that Direct Connect tries to connect to port
4182 directly.
Given all this, I'd say the bug is in the Gnutella
searching somewhere. It connects to the right server at startup,
but doesn't connect there when "Connect" is used. Sometimes (I
can't find a good way to repeat it
Hope this helps!
-Scott
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
