VK:
I've attached the packet log from startup to this email.
You can see that Kaboodle gets past the Gnutella handshake, but
gets "stuck" doing broadcasts to the .255 address (I think it's
the "looking for other Kaboodle instances" part). You can also
see it never gets far enough to ping the whole LAN. The "Detecting
Network..." never goes away.
This from release build of 17 Aug 02 on WinXP. I haven't
tried with today's code yet.
-Scott
On Mon, 19 Aug 2002, mailbox wrote:
> Hello Scott,
> Sorry I could not replicate the bug you mentioned on windowXP at my end.
>
> Regards,
> Varsha
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "mailbox" <[EMAIL PROTECTED]>
> Cc: "Igor Kotelevsky" <[EMAIL PROTECTED]>; "Kaboodle-devel"
> <[EMAIL PROTECTED]>
> Sent: Sunday, August 18, 2002 1:08 AM
> Subject: Re: [Kaboodle-devel] "VNC halo" bug
>
>
> > VK:
> > Thanks for removing the duplication. However, the release
> > build is now unstable (testing here on WinXP). After "Classifying
> > Devices..." and VNC discovery it locks up. Can't select, can't
> > scroll, can't quit. Gotta use the task manager to kill it. This
> > got added yesterday, I saw it then too. The 14-Aug-02 code is
> > stable.
> >
> > -Scott
> >
> >
> > On Sat, 17 Aug 2002, mailbox wrote:
> >
> > > Hello Igor,
> > > I have removed the duplication. Igor Please test the correctness of the
> > > code.
> > >
> > > Regards,
> > > Varsha
> > > ----- Original Message -----
> > > From: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > To: "Scott C. Best" <[EMAIL PROTECTED]>; "mailbox" <[EMAIL PROTECTED]>
> > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> > > Sent: Friday, August 16, 2002 4:55 PM
> > > Subject: [Kaboodle-devel] "VNC halo" bug
> > >
> > >
> > > > Hello Scott.
> > > > I found that "VNC halo" bug is my bug.
> > > > That bug fixed.
> > > >
> > > > I visited
> > > > http://www.geocrawler.com/lists/3/SourceForge/16728/0/9330591/
> > > > and found following:
> > > > > Regarding the VNC status display synchronization:
> > > > > I have added the synchronization, which will display the VNC halo
> icon.
> > > > > For this to work I have added the flag to kaboodlebase.h as the data
> for
> > > > VNC
> > > > > comes from the registry.
> > > > I understand that Varsha also fixed that bug.
> > > >
> > > > But here is next problem.
> > > > Kaboodle already had data, which described independent VNC service.
> > > > That data was
> > > > CNIDDevice::m_Attributes.m_uiIndependentVncPort.
> > > > It is the port number of independent VNC Server:
> > > > _UNDEF_VNC - we don't know about VNC Server,
> > > > _NO_VNC_RUN - VNC Server don't run,
> > > > otherwise - port number of independent VNC Server.
> > > > Now Kaboodle has new binary flag PC_RUNNING_VNC,
> > > > which also describes above data.
> > > >
> > > > Therefore redundancy of data appears.
> > > > That redundancy is a potential source of mistakes.
> > > > I prefer to avoid that redundancy.
> > > > I can remove the flag PC_RUNNING_VNC and avoid that redundancy.
> > > > Please let me know if I have to make that.
> > > >
> > > > - Igor
> > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This sf.net email is sponsored by: OSDN - Tired of that same old
> > > > cell phone? Get a new here for FREE!
> > > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > > > _______________________________________________
> > > > Kaboodle-devel mailing list
> > > > [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> > > >
> > >
> > >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by: OSDN - Tired of that same old
> > cell phone? Get a new here for FREE!
> > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > _______________________________________________
> > Kaboodle-devel mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> >
>
>
C:\>WinDump -n -s 1024 src 192.168.1.100
WinDump: listening on \Device\NPF_{324E2B25-4FC1-4D56-B1FA-58B34159A0B3}
12:04:35.554522 IP 192.168.1.100.138 > 192.168.1.255.138: udp 174
12:04:35.554796 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:36.298930 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:37.048908 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:39.798860 IP 192.168.1.100.138 > 192.168.1.255.138: udp 174
12:04:39.798976 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:40.548818 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:41.298787 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:44.062946 IP 192.168.1.100.138 > 192.168.1.255.138: udp 174
12:04:44.063063 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:44.798684 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:45.548675 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:04:48.298628 IP 192.168.1.100.138 > 192.168.1.255.138: udp 183
12:04:48.698960 IP 192.168.1.100.1034 > 63.240.76.19.53: 35+ A? Gnutella.GetEng
aged.Net. (41)
12:04:49.099137 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:04:49.689236 IP 192.168.1.100.1034 > 204.127.198.19.53: 35+ A? Gnutella.GetE
ngaged.Net. (41)
12:04:49.907954 IP 192.168.1.100.138 > 192.168.1.255.138: udp 187
12:04:50.096717 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:04:50.689287 IP 192.168.1.100.1034 > 24.147.1.57.53: 35+ A? Gnutella.GetEnga
ged.Net. (41)
12:04:50.907953 IP 192.168.1.100.138 > 192.168.1.255.138: udp 187
12:04:51.092061 IP 192.168.1.100.1124 > 66.123.20.59.4183: S 3542387805:35423878
05(0) win 16384 <mss 1460,nop,nop,sackOK> (DF)
12:04:51.097323 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:04:51.202748 IP 192.168.1.100.1124 > 66.123.20.59.4183: . ack 3842406781 win
17232 (DF)
12:04:51.203166 IP 192.168.1.100.1124 > 66.123.20.59.4183: P 0:22(22) ack 1 win
17232 (DF)
12:04:51.517219 IP 192.168.1.100.1124 > 66.123.20.59.4183: . ack 14 win 17219 (DF)
12:04:51.907915 IP 192.168.1.100.138 > 192.168.1.255.138: udp 187
12:04:52.907931 IP 192.168.1.100.138 > 192.168.1.255.138: udp 187
12:04:53.908079 IP 192.168.1.100.137 > 192.168.1.255.137: udp 68
12:04:54.657797 IP 192.168.1.100.137 > 192.168.1.255.137: udp 68
12:04:55.407764 IP 192.168.1.100.137 > 192.168.1.255.137: udp 68
12:04:56.157754 IP 192.168.1.100.137 > 192.168.1.255.137: udp 68
12:04:56.907898 IP 192.168.1.100.137 > 192.168.1.255.137: udp 68
12:04:57.657708 IP 192.168.1.100.137 > 192.168.1.255.137: udp 68
12:04:58.407691 IP 192.168.1.100.137 > 192.168.1.255.137: udp 68
12:04:59.157675 IP 192.168.1.100.137 > 192.168.1.255.137: udp 68
12:04:59.908668 IP 192.168.1.100.138 > 192.168.1.255.138: udp 205
12:04:59.910590 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:05:00.657630 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:05:01.112627 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:05:01.407599 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:05:02.159461 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:05:02.907564 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:05:03.657557 IP 192.168.1.100.137 > 192.168.1.255.137: udp 50
12:05:11.127909 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:05:21.127673 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:05:31.142973 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:05:41.142805 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:05:51.158045 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:05:59.906765 IP 192.168.1.100.138 > 192.168.1.255.138: udp 205
12:06:01.157830 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:06:11.173137 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:06:21.172847 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:06:31.172540 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:06:41.172279 IP 192.168.1.100.1123 > 255.255.255.255.4082: udp 324
12:06:48.035746 IP 192.168.1.100.1124 > 66.123.20.59.4183: F 22:22(0) ack 14 win 17219
(DF)
12:06:48.166784 IP 192.168.1.100.1124 > 66.123.20.59.4183: . ack 15 win 17219
(DF)12:06:59.906275 IP 192.168.1.100.138 > 192.168.1.255.138: udp 205
