Igor:
Just checking...are you using version 3.0.4 of WinPCAP?
-Scott
On Fri, 22 Nov 2002, Igor Kotelevsky wrote:
> Hello everyone.
> I found the example of using WpCap at the
> http://www.cet.nau.edu/~mc8/Socket/Tutorials/section1.html
> That example also returns network address *all zeros* for my Win2000 prof.
> Please let me know if somebody saw, that the function *pcap_lookupnet*
> of the WpCap successfully returns valid network address for Win2000 prof.
> - Igor
>
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Friday, November 22, 2002 8:19 AM
> Subject: Re: Sniffer thread bug
>
>
> > Igor:
> > Attached are the logs from my WinNT machine and my
> > Win98 machine. The NT machine looks fine. The Win98 log don't
> > even have a sniffer log -- the thread dies so early that the
> > log isn't even generated. Yikes.
> >
> > Good luck chasing this one down. It's important to
> > get this working.
> >
> > -Scott
> >
> > On Thu, 21 Nov 2002, Igor Kotelevsky wrote:
> >
> > > Hello Scott.
> > > About your WinNT machine.
> > > I see from log that sniffer found 3 adapters (network cards).
> > > Then it failed to get network address for 2 of them.
> > > But it successfully found the network address for 1 of them.
> > >
> > > About your Win98 machine.
> > > It's very strange that log file didn't created.
> > > It looks like that thread failed before creation of that file.
> > > >From analysis of the source code,
> > > I can guess that it failed to found (GetProcAddress)
> > > of some function from the WpCap component.
> > > In my Win98 machine it failed in other point, the log created.
> > > I added some extra data into that log.
> > > Please
> > > update latest CVS snapshot,
> > > try to obtain and
> > > send me that log again.
> > >
> > > - Igor
> > >
> > > ----- Original Message -----
> > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > Cc: <[EMAIL PROTECTED]>
> > > Sent: Thursday, November 21, 2002 10:23 AM
> > > Subject: Re: Master Node bugs
> > >
> > >
> > > > Igor:
> > > > Attached, please find the sniffer log file from my WinNT
> > > > machine. This log file isn't even created on my other Win98 PC
> > > > (though winpcap is installed on both). I've attached all of the
> > > > logs for the Win98 machine -- you'll notice it only finds 2
> > > > PC's on my network of 6 or 7 devices. Ouch.
> > > >
> > > > Please look into the WinPCAP implementation of Kaboodle.
> > > > It's important that this be bug-free, even on Win98. Last I
> > > > heard from OAS, it was all working.
> > > >
> > > > -Scott
> > > >
> > > >
> > > > On Wed, 20 Nov 2002, Igor Kotelevsky wrote:
> > > >
> > > > > Hello Scott.
> > > > > Please see my inline comments.
> > > > > - Igor
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > Sent: Wednesday, November 20, 2002 9:00 AM
> > > > > Subject: Re: Master Node bugs
> > > > > > Igor:
> > > > > > Heya. The Master Node stuff is looking better. I
> > > > > > noticed two related bugs tonight:
> > > > > >
> > > > > > 1. All of my Kaboodle PC's are still ping'ing the active list.
> > > > > > Only the Master Node device should ping. Everyone needs to
> > > > > > sniff, though.
> > > > > In my tests the *sniffer thread* doesn't work.
> > > > > So, may be, I don't see some pings that you see.
> > > > > I wrote you about these bugs of my tests earlier.
> > > > > I attached my *Sniffer.txt* log from Win2000 box.
> > > > > There are lines #9 and #14-15,
> > > > > which show that sniffer thread failed to define a network
> > > > > address and stopped. Win98 box shows the same bug.
> > > > > That bug appears always:
> > > > > if Kaboodle is Master Node and if Kaboodle is not Master Node.
> > > > > Do you see any error in your log file?
> > > > > Please send me *Sniffer.txt* log from your PC.
> > > > > I tested some samples from WpCap site and they worked correctly,
> > > > > so I think that my WpCap component installed correctly.
> > > > > I afraid that *sniffer thread*
> > > > > *didn't correctly* implement functionality of the WpCap.
> > > > >
> > > > > > 2. It doesn't look like NID sync'ing is activated when Kaboodle
> > > > > > sniffs a new network arrival. That is, my Master Node GUI
> > > > > > updates to display the new arrival, but the non-Master GUI's
> > > > > > don't update until I click "refresh". It needs to work like
> > > > > > this: if the Master Node sniffs a new arrival it should run
> > > > > > OS detection on it, then tell all of the non-Master nodes
> > > > > > about the new device. If one of the non-Master nodes sniffs a
> > > > > > new device, it should tell the Master about it.
> > > > > First.
> > > > > As I wrote above, my Kaboodle doesn't sniffs.
> > > > > Except *Sniffer.txt* log file, I implemented following test:
> > > > > - I started Kaboodle on the PC1 device.
> > > > > The PC2 device didn't work in that time.
> > > > > - After Kaboodle on the PC1 finished LAN detection and
> > > > > installed itself as Master Node,
> > > > > then I started PC2 device.
> > > > > Kaboodle didn't show the PC2 device.
> > > > > - Then I pinged the PC1 from the PC2 - Kaboodle didn't show the PC2
> > > device.
> > > > > - Then I successfully started VNC session from the PC2 (viewer)
> > > > > to the PC1 (server).
> > > > > (There was VNC session without Kaboodle.)
> > > > > Kaboodle didn't show the PC2 device also.
> > > > > But your sounds:
> > > > > > It doesn't look like NID sync'ing is activated when Kaboodle
> > > > > > sniffs a new network arrival.
> > > > > seem very strange to me.
> > > > > Please send me log files for both Kaboodle's.
> > > > >
> > > > > Second.
> > > > > You wrote:
> > > > > > If one of the non-Master nodes sniffs a
> > > > > > new device, it should tell the Master about it.
> > > > > I looked into the source code of the *sniffer thread*.
> > > > > The current implementation is next:
> > > > > If one of the nodes (Master or non-Master) sniffs
> > > > > a new device, it performs own LAN scan.
> > > > > Results of that scan will NID sync'ing.
> > > > > Now *sniffer thread* don't works correctly on my PC,
> > > > > so I cannot begin implementation of that new thing.
> > > > >
> > > > > > Two non-related bugs now:
> > > > > >
> > > > > > 3. I detected a rogue wireless LAN member today, probably my
> > > > > > neighbor. They disconnected before Kaboodle was done with
> > > > > > OS detection, though, and Kaboodle hung up waiting for the
> > > > > > TCP sockets to time-out. Is there any way to make it fail
> > > > > > more gently when a TCP connection is failing? On my WinNT
> > > > > > box, Kaboodle was non-responsive for more than 2 minutes.
> > > > > There is very slippery thing: if we decrease a time-out of the TCP
> > > sockets,
> > > > > then we decrease a reliability of them also.
> > > > > If I'll reproduce that bug, then I'll try to do something.
> > > > > Now I don't know what occurrence of the TCP socket is
> > > > > the reason of that bug.
> > > > >
> > > > > > 4. I've attached the GIF's of two GUI bugs. One is an overwrite
> > > > > > of the "cancel" button during a file-transfer. The other is
> > > > > > the PropPanel for a Printer -- it looks like it's been
> > > > > > confused with the Network Icon PropPanel.
> > > > > I saw and fixed these bugs. All my changes are in the CVS server.
> > > > >
> > > > >
> > > > > > thanks,
> > > > > > Scott
> > > > > >
> > > > > >
> > > > > > On Tue, 19 Nov 2002, Igor Kotelevsky wrote:
> > > > > >
> > > > > > > Hello Scott.
> > > > > > > The thing that you wrote looks as
> > > > > > > *more automatically setting of the Master Node*.
> > > > > > > I implemented following.
> > > > > > > 1. If Kaboodle starts, then it never set itself as Master Node.
> > > > > > > (Earlier it applied the previous setting.)
> > > > > > > 2. After LAN detecting and finishing timer (7 seconds),
> > > > > > > it performs checking.
> > > > > > > 2.1 If there absent other running an instance in the LAN,
> > > > > > > which is Master Node,
> > > > > > > then Kaboodle sets itself as Master Node.
> > > > > > > (#2 was implemented earlier.)
> > > > > > > 3. If other instance shutdowns, then Kaboodle performs checking.
> > > > > > > Then #2.1 follows.
> > > > > > > If there are more then one running instances without Master Node
> > > status,
> > > > > > > then Kaboodle have to decide which instance will set itself as
> > > Master
> > > > > Node:
> > > > > > > it will be the instance, which MAC address string is minimum.
> > > > > > > Therefore only one Kaboodle will set itself as Master Node.
> > > > > > >
> > > > > > > Because of #1, the message
> > > > > > > *This PC isn't a "Master Node" Continue a registration ?*
> > > > > > > of *GetEngaged.exe* isn't correct always.
> > > > > > >
> > > > > > > You asked:
> > > > > > > > Also, in the Device Icon, where it says "This PC is
> > > > > > > > currently the Master Node" the checkbox is still active. It
> should
> > > > > > > > be greyed out if the PC is the Master.
> > > > > > > That thing implemented.
> > > > > > >
> > > > > > > All my changes are in the CVS server.
> > > > > > > - Igor
> > > > > > >
> > > > > > >
> > > > > > > ----- Original Message -----
> > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > Sent: Monday, November 18, 2002 8:40 PM
> > > > > > > Subject: Re: Master Node bugs
> > > > > > >
> > > > > > >
> > > > > > > > Igor:
> > > > > > > > Thanks for this update. It's close, but still a little
> > > > > > > > buggy: I start Kaboodle on PC1 (WinNT) with no other Kaboodles
> > > > > > > > on the LAN, and let it finish OS discovery. Then I shut it
> down.
> > > > > > > > Next, start Kaboodle on PC2 (Win98) with no other Kaboodles on
> > > > > > > > the LAN. Let it finish OS discovery. Then turn Kaboodle on PC1
> > > > > > > > back on.
> > > > > > > > In the Network Icon of PC2, it says that PC1 is the
> > > > > > > > Master. In the Network Icon of PC1, it says that PC2 is the
> > > > > > > > Master. In the device icons of both on both PC's, it says that
> > > > > > > > both are the Master node. When I look at the network traffic,
> > > > > > > > both PC's are active ping'ing the active device list.
> > > > > > > >
> > > > > > > > Of course, the desired functionalit is that PC2 should
> > > > > > > > be the Master -- when it joined the LAN, there wasn't an
> existing
> > > > > > > > Master. When PC1 came back online, it should defer to PC2, the
> > > > > > > > current Master.
> > > > > > > >
> > > > > > > > Also, in the Device Icon, where it says "This PC is
> > > > > > > > currently the Master Node" the checkbox is still active. It
> should
> > > > > > > > be greyed out if the PC is the Master.
> > > > > > > >
> > > > > > > > thanks,
> > > > > > > > Scott
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, 18 Nov 2002, Igor Kotelevsky wrote:
> > > > > > > >
> > > > > > > > > Hello Scott.
> > > > > > > > > Your thing implemented:
> > > > > > > > > If an user sets Master Node status for some device,
> > > > > > > > > then Kaboodle iterates all LAN devices.
> > > > > > > > > If it found other device, which also has Master Node status,
> > > > > > > > > then it removes Master Node status for that device.
> > > > > > > > > - Igor
> > > > > > > > >
> > > > > > > > > ----- Original Message -----
> > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > > > Sent: Saturday, November 16, 2002 8:31 AM
> > > > > > > > > Subject: Re: Master Node bugs
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Igor:
> > > > > > > > > > I think I see part of the problem now:
> > > > > > > > > >
> > > > > > > > > > > I don't understand where is the bug.
> > > > > > > > > > > Kaboodle sets the PC2 Master Node, as your asked.
> > > > > > > > > > > After that there are 2 Master Nodes - both PC1 and PC2.
> > > > > > > > > >
> > > > > > > > > > Here's the thing: I want there to be a maximum of
> > > > > > > > > > *one* Master Node *per network*. If a user makes a
> Kaboodle
> > > > > > > > > > instance a Master, the current Kaboodle Master needs to
> > > > > > > > > > give up its Master status.
> > > > > > > > > >
> > > > > > > > > > Looking at the sniffer stuff now.
> > > > > > > > > >
> > > > > > > > > > -Scott
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Fri, 15 Nov 2002, Igor Kotelevsky wrote:
> > > > > > > > > >
> > > > > > > > > > > Hello Scott.
> > > > > > > > > > > Please see my inline comments.
> > > > > > > > > > > - Igor
> > > > > > > > > > >
> > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > > > > > Sent: Friday, November 15, 2002 12:41 AM
> > > > > > > > > > > Subject: Re: Master Node bugs
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > Igor:
> > > > > > > > > > > > I tested this code today as follows: I started
> Kaboodle
> > > > > > > > > > > > (with a new registry) on my WinNT PC (PC1). It
> completed
> > > the
> > > > > > > > > > > > network discovery and OS discovery correctly. Then I
> > > started
> > > > > > > > > > > > Kaboodle (with a new registry) on my Win98 PC (PC2).
> In
> > > the
> > > > > > > > > > > > Network Icon and both device icons, it correctly
> showed
> > > the
> > > > > > > > > > > > Master Node as being PC1.
> > > > > > > > > > > >
> > > > > > > > > > > > Then on PC1 I changed the Master Node from PC1 to PC2
> > > > > > > > > > > > via the Network Icon dropdown and clicked OK. When I
> > > reopened
> > > > > > > > > > > > the Network Icon, it correctly showed PC2 as the new
> > > Master
> > > > > > > > > > > > Node. However, in the Network Icon on PC2, it still
> says
> > > PC1
> > > > > is
> > > > > > > > > > > > the Master. Also, the device icons for both PC1 and
> PC2
> > > both
> > > > > > > > > > > > say that their device is the Master node.
> > > > > > > > > > > I don't understand where is the bug.
> > > > > > > > > > > Kaboodle sets the PC2 Master Node, as your asked.
> > > > > > > > > > > After that there are 2 Master Nodes - both PC1 and PC2.
> > > > > > > > > > > If you open Network Icon, then combobox activates one of
> > > them.
> > > > > > > > > > > Of course, I think that it isn't clear for a user: they
> > > cannot
> > > > > > > > > understand
> > > > > > > > > > > which PC is Master Node, or which PC isn't Master Node.
> > > > > > > > > > > I proposed different variants of GUI:
> > > > > > > > > > > - special icon before text in the combobox,
> > > > > > > > > > > - special text after PC-name in the combobox,
> > > > > > > > > > > - special text under combobox.
> > > > > > > > > > > You prefer the current variant of GUI and that variant
> > > > > implemented.
> > > > > > > > > > > Please let me know what kind of combobox does you like:
> > > > > > > > > > > what must show combobox if there are 2 Kaboodles, both
> of
> > > which
> > > > > is
> > > > > > > > > > > Master Node.
> > > > > > > > > > >
> > > > > > > > > > > > I've attached the logs from PC1 (WinNT) and PC2
> (Win98).
> > > > > > > > > > > > From the amount of network traffic I see on the LAN
> > > between
> > > > > > > > > > > > PC1 and PC2 involving TCP port 4083, I'm thinking that
> the
> > > NID
> > > > > > > > > > > > is not correctly being sync'd between the two Kaboodle
> > > > > instances.
> > > > > > > > > > > I don't found someone not correctness in these logs.
> > > > > > > > > > >
> > > > > > > > > > > > Lastly, we should remove the ping'ing from the sniffer
> > > > > > > > > > > > thread. It really doesn't belong there at all.
> Sniffing is
> > > > > > > > > > > > passive and generates no network traffic; it doesn't
> make
> > > > > sense
> > > > > > > > > > > > to put anything that generates traffic into that
> thread.
> > > > > Ping'ing
> > > > > > > > > > > > the LAN really should be part of the
> CSearchNetworkManager
> > > > > thread
> > > > > > > > > > > > only.
> > > > > > > > > > > I saw into the sniffer thread more carefully and found
> > > > > following.
> > > > > > > > > > > The sniffer thread doesn't work - it fails in
> > > initialization.
> > > > > > > > > > > I am not familiar with wpcap.dll (that thread use that
> > > > > component),
> > > > > > > > > > > but it looks like the thread cannot correctly
> > > > > > > > > > > define mask or IP address of the network interface.
> > > > > > > > > > > I tested that in Win2000 and Win98.
> > > > > > > > > > > For both OS's it failed, since in different points.
> > > > > > > > > > > I added next log file *Sniffer.txt* into the source code
> > > > > > > > > > > (for debug build only).
> > > > > > > > > > > Please send me that log from your PC.
> > > > > > > > > > > - Igor
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > thanks,
> > > > > > > > > > > > Scott
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, 14 Nov 2002, Igor Kotelevsky wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > Kaboodle has 2 threads, which ping LAN -
> > > > > > > > > > > > > *CSearchNetworkManager* and *CSnifferThread*.
> > > > > > > > > > > > > As I see from the *Ping.txt* log file,
> > > > > > > > > > > > > they have following approximate estimate of pinging:
> > > > > > > > > > > > > CSearchNetworkManager - 30%, CSnifferThread - 70%.
> > > > > > > > > > > > > Now CSearchNetworkManager ping only if Kaboodle has
> > > Master
> > > > > Node
> > > > > > > > > status.
> > > > > > > > > > > > > In my yesterday CVS snapshot CSnifferThread also
> > > > > > > > > > > > > pinged only if Kaboodle has Master Node status.
> > > > > > > > > > > > > After you found Win98 bug, I return back -
> > > CSnifferThread
> > > > > pings
> > > > > > > > > always.
> > > > > > > > > > > > > Please test both variants on your Win98 laptop -
> > > > > > > > > > > > > with and without ping from CSnifferThread.
> > > > > > > > > > > > > The source code has very simple possibility for
> > > implementing
> > > > > > > these
> > > > > > > > > > > things.
> > > > > > > > > > > > > Please look into the file COMMON\Ping.cpp.
> > > > > > > > > > > > > There is the line #23.
> > > > > > > > > > > > > Now there is following text
> > > > > > > > > > > > > file://#define _PING_FOR_MASTER_NODE_ONLY
> > > > > > > > > > > > > and CSnifferThread pings always.
> > > > > > > > > > > > > If you remove out commentary (first and second
> symbols)
> > > from
> > > > > > > that
> > > > > > > > > text,
> > > > > > > > > > > > > then CSnifferThread will ping for Master Node status
> > > only.
> > > > > > > > > > > > >
> > > > > > > > > > > > > - Igor
> > > > > > > > > > > > >
> > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > Cc: <[EMAIL PROTECTED]>
> > > > > > > > > > > > > Sent: Thursday, November 14, 2002 10:25 AM
> > > > > > > > > > > > > Subject: Re: Master Node bugs
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > Heya. Tried this variant: I can't tell if the
> sniffing
> > > > > > > > > > > > > > is working, because Kaboodle is now not pinging
> the
> > > whole
> > > > > LAN
> > > > > > > > > > > > > > at startup. Whoops.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > In general, every Kaboodle should always sniff if
> > > > > > > > > > > > > > WinPCAP is installed. It shouldn't have anything
> to do
> > > > > with
> > > > > > > > > > > > > > Master Node status.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > thanks,
> > > > > > > > > > > > > > Scott
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Wed, 13 Nov 2002, Igor Kotelevsky wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > About your thing
> > > > > > > > > > > > > > > > 1. All Kaboodle nodes ping the list of active
> > > devices.
> > > > > > > Only
> > > > > > > > > > > > > > > > the Master Node should do this. Everyone
> else
> > > > > should
> > > > > > > just
> > > > > > > > > > > > > > > > sniff.
> > > > > > > > > > > > > > > There was following thing.
> > > > > > > > > > > > > > > The sniffer thread pings every time -
> > > > > > > > > > > > > > > no matter is Kaboodle Master Node or no.
> > > > > > > > > > > > > > > I added a little modification -
> > > > > > > > > > > > > > > that thread pings if Kaboodle is Master Node
> only.
> > > > > > > > > > > > > > > But that change may have potential bug:
> > > > > > > > > > > > > > > - Sniffer thread created directly after start,
> > > > > > > > > > > > > > > - If Kaboodle starts at first time (empty
> registry),
> > > > > > > > > > > > > > > then it isn't a Master Node.
> > > > > > > > > > > > > > > It can become as the Master Node via some time
> only.
> > > > > > > > > > > > > > > Therefore some time sniffer thread didn't works
> > > > > correctly.
> > > > > > > > > > > > > > > In my tests that modification didn't have "LAN
> > > scans"
> > > > > bug.
> > > > > > > > > > > > > > > But I didn't sure it's valid for all cases.
> > > > > > > > > > > > > > > Please repeat a variant:
> > > > > > > > > > > > > > > - start one Kaboodle in your LAN. Kaboodle
> registry
> > > key
> > > > > is
> > > > > > > > > empty.
> > > > > > > > > > > > > > > Please let me know accuracy of "LAN scans".
> > > > > > > > > > > > > > > If that result will not correctly, then I'll
> remove
> > > that
> > > > > > > > > > > modification.
> > > > > > > > > > > > > > > Also I inform you that I added new log file
> > > *Ping.txt*
> > > > > > > (debug
> > > > > > > > > build
> > > > > > > > > > > > > only).
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > About your thing
> > > > > > > > > > > > > > > > 2. When I start Kaboodle on a Win98 laptop
> with
> > > just a
> > > > > > > modem
> > > > > > > > > > > > > > > > and no network connection, it fails to set
> > > itself
> > > > > as
> > > > > > > the
> > > > > > > > > > > > > > > > Master.
> > > > > > > > > > > > > > > I need some additional data.
> > > > > > > > > > > > > > > I'll write additional log-file about
> functionality
> > > of
> > > > > > > "Master
> > > > > > > > > Node".
> > > > > > > > > > > > > > > Then I'll ask you send that file to me.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > To: "Igor Kotelevsky"
> <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > Cc: <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > Sent: Tuesday, November 12, 2002 7:51 PM
> > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Re: VPN bug
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > > > Thanks for the update. Am testing it out now.
> > > > > Regarding
> > > > > > > > > > > > > > > > #1 thru #5, how long would you estimate it
> would
> > > take
> > > > > you
> > > > > > > to
> > > > > > > > > > > > > > > > clean up the code and document the
> functionality?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Before that work, though, I'm hoping we can
> fix
> > > the
> > > > > > > > > > > > > > > > Master Node functionality. Two known bugs:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > 1. All Kaboodle nodes ping the list of active
> > > devices.
> > > > > > > Only
> > > > > > > > > > > > > > > > the Master Node should do this. Everyone
> else
> > > > > should
> > > > > > > just
> > > > > > > > > > > > > > > > sniff. If I change the Master Node, the new
> > > Master
> > > > > > > should
> > > > > > > > > > > > > > > > start pinging.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > 2. When I start Kaboodle on a Win98 laptop
> with
> > > just a
> > > > > > > modem
> > > > > > > > > > > > > > > > and no network connection, it fails to set
> > > itself
> > > > > as
> > > > > > > the
> > > > > > > > > > > > > > > > Master. At least, when I install the
> > > > > RegistrationFile,
> > > > > > > > > > > > > > > > GetEngaged.exe warns me that "This PC is
> not
> > > the
> > > > > > > Master".
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > thanks,
> > > > > > > > > > > > > > > > Scott
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Tue, 12 Nov 2002, Igor Kotelevsky wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > > > > Your thing implemented:
> > > > > > > > > > > > > > > > > Kaboodle saves the IP address after
> successful
> > > > > remote
> > > > > > > > > connection
> > > > > > > > > > > > > > > > > in the registry. When it next try to connect
> > > with
> > > > > that
> > > > > > > > > partner,
> > > > > > > > > > > > > > > > > it try that IP address *first*, on port
> 4182,
> > > > > > > > > > > > > > > > > bypassing a Gnutella completely.
> > > > > > > > > > > > > > > > > If it fails to connect, then it returns back
> to
> > > the
> > > > > > > Gnutella
> > > > > > > > > > > search.
> > > > > > > > > > > > > > > > > All my changes are in the CVS server.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Also I want to notice following my
> estimation:
> > > > > > > > > > > > > > > > > 1. Current design of source code not very
> well
> > > to
> > > > > answer
> > > > > > > the
> > > > > > > > > > > purpose
> > > > > > > > > > > > > > > > > of the current functionality of the
> application.
> > > > > > > > > > > > > > > > > There are very many big functions, which has
> > > fuzzy
> > > > > > > > > > > functionality.
> > > > > > > > > > > > > > > > > 2. Source code has very little
> documentation.
> > > > > > > > > > > > > > > > > 3. There is a big part of code, which was
> > > written in
> > > > > > > style C
> > > > > > > > > > > > > language,
> > > > > > > > > > > > > > > > > but not in style C++ language.
> > > > > > > > > > > > > > > > > 4. Indications of many variables look as in
> > > > > "hungarian
> > > > > > > > > > > notation",
> > > > > > > > > > > > > > > > > but these real types not conform to that
> > > notation.
> > > > > > > > > > > > > > > > > 5. Indications of some variables written in
> MFC
> > > > > style,
> > > > > > > > > > > > > > > > > others variables don't has that style,
> > > > > > > > > > > > > > > > > even when both of them refer to one class.
> > > > > > > > > > > > > > > > > Things #1 - #5 greatly obstruct further
> > > > > accompaniment
> > > > > > > and
> > > > > > > > > > > > > development
> > > > > > > > > > > > > > > > > of the application.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > To: "Igor Kotelevsky"
> > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > Cc: <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > Sent: Monday, November 11, 2002 10:35 PM
> > > > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Re: VPN bug
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > > > > > Sorry, didn't see this email until after I
> > > sent my
> > > > > > > > > > > > > > > > > > email describing the LAN traffic. Am
> looking
> > > > > forward
> > > > > > > to
> > > > > > > > > you
> > > > > > > > > > > > > > > > > > getting to work on this tomorrrow.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Mon, 11 Nov 2002, Igor Kotelevsky
> wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > First.
> > > > > > > > > > > > > > > > > > > The bug you wrote fixed:
> > > > > > > > > > > > > > > > > > > > > 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.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Second.
> > > > > > > > > > > > > > > > > > > Now Kaboodle saves the IP address of the
> > > latest
> > > > > > > > > successful
> > > > > > > > > > > > > remote
> > > > > > > > > > > > > > > > > connection
> > > > > > > > > > > > > > > > > > > in the registry.
> > > > > > > > > > > > > > > > > > > Please see the registry key
> > > > > > > > > > > > > > > > > > >
> *SOFTWARE\Kaboodle\LatestRemoteConnections*.
> > > > > > > > > > > > > > > > > > > It didn't tries that IP addresses
> *first*,
> > > on
> > > > > port
> > > > > > > 4182,
> > > > > > > > > > > > > > > > > > > bypassing Gnutella completely.
> > > > > > > > > > > > > > > > > > > I'll implement that later on (I hope
> this
> > > will
> > > > > > > > > tomorrow).
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > To: "Igor Kotelevsky"
> > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > Cc:
> <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > Sent: Monday, November 11, 2002 10:11 AM
> > > > > > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Re: VPN
> bug
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > > > > > > > Heya. Hope you had a good weekend.
> Quick
> > > > > > > questions:
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > 1. Any progress on the update to
> Kaboodle
> > > to
> > > > > use
> > > > > > > > > Partner
> > > > > > > > > > > IP
> > > > > > > > > > > > > > > > > > > > addresses as described below?
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > 2. Any progress on the Master Node
> ping
> > > > > problem?
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > thanks,
> > > > > > > > > > > > > > > > > > > > Scott
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > On Wed, 6 Nov 2002, Scott C. Best
> wrote:
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > 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
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > -------------------------------------------------------
> > > > > > > > > > > > > > > > > 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
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
> -------------------------------------------------------
> 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
>
-------------------------------------------------------
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
