VK:
Hello! I am sorry to hear you were sick. I hope you
are recovering well. I get most of my colds from my kids, so
I get to see what I'm going to get before I get it. :)
The IP address "172.191.8.224" belongs to AOL. It's
what my modem interface gets set to after I connect to AOL.
Perhaps the AOL service assigns a "virtual" device interface,
giving it both an IP and MAC address? Since the MAC address
doesn't start with "00", it's not listed in the IEEE OUI
list:
http://standards.ieee.org/regauth/oui/oui.txt
Perhaps that's the check we should use: if the
interface doesn't have a MAC address starting with "00", we
should presume we're not on a LAN connection.
I'll compile what you and Igor sent and pass along
results.
-Scott
On Tue, 30 Jul 2002, mailbox wrote:
> Hello Scott,
> Sorry for long silence. I was not well. I saw the debug output dump that you
> had sent. Here is my observation:
> There is some other device other than the PC that is running kaboodle.
> It has IP address 172.191.8.224,with physical address 20-53-52-43-00-00.
> The sniffer code is not detecting this device. Which type of device it is?
> The Sniffer thread is not working in the background, as there is no
> indication in the debug dump. I have added some extra check for the arp
> entries that we use in startping function after 255 pings for class C.
> Please use the latest wincvs code.
>
> Regards,
> Varsha
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "mailbox" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> Sent: Friday, July 26, 2002 12:27 PM
> Subject: [Kaboodle-devel] Re: Bug Report, 22 July
>
>
> > VK, Igor:
> >
> > I tested this again tonight. I installed VC++ on my
> > poor little Win98 laptop, applied the latest SP5 service pack.
> > I compiled the latest source, connected to AOL, and started
> > the debug. Output attached (I don't know why it's so short,
> > but it is).
> >
> > Kaboodle starts, and the "Detecting Network" message
> > box comes up. At this point, in my opinion, it should detect
> > that it's on a modem and give up. It doesn't. About half a
> > minute later, "Classifying New Devices" comes up. About 10
> > seconds later, Windows then blue screens with the message:
> >
> > "A fatal exception OE has occurred at 0028:C004A08B in VXD NDIS(01) +
> > 00002F1F. The current application will be terminated."
> >
> > The second time I tried this, the debug output looks
> > like it started the VNC auto-detection before it crashed.
> >
> > Any advice appreciated.
> >
> > -Scott
> >
> >
> > On Mon, 22 Jul 2002, Scott C. Best wrote:
> >
> > >
> > > I tested Kaboodle on a un-networked Win98 machine which
> > > uses AOL as the dialup ISP. I connected to AOL, then started
> > > Kaboodle, and it blue-screen'd the PC when it got to the
> > > "Classifying Devices" part of startup.
> > > Ouch.
> > >
> > > Is it possible to restrict network detection to use only
> > > LAN-based interfaces, as opposed to modem-interfaces? I can't
> > > imagine that we'd ever want to ping 255 devices on one of AOL's
> > > subnets...
> > >
> > > -Scott
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
