forum.vdsworld.com

[Hippo]

I dont know wether this is a bug as such or wether its a limitation of the DLL. I have a few internet buddies who have tried out my bandwidth monitor for me, its nice to have beta testers

One of my beta testers reports that it does not detect traffic on his wifi adapter. If he connects his wired LAN up then it works. I have a wifi card on my laptop and it reads that perfectly.

I personally dont think this is a bug, more a limitation of the method used to read the values, although I dont quite understand why it can read my wifi card and not his

Any ideas Dr. Dread?

[Dr. Dread]

Naaa, actually not! I mentioned in another thread that the DLL uses Windows' Management Information
Base API to plug into Win network stats.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mib/mib/mib_structures.asp

The DLL only reports traffic on the ethernet interface.

So somehow traffic on your tester's computer is not reported by MIB as ethernet traffic. Frankly it escapes me why....

Greetz
Dr. Dread

[Hippo]

Thanks Dread, you mentioned where you got the stats from before as you say, but I couldnt find the thread

As you say the Windows MIB should be getting information for the adapter, and since its a Windows function it should work everytime.

I asked the guy with the problem to tell me about his hardware. He uses a Dlink wifi card with a Dlink AP/Router. He allows Windows to configure his wireless networking.

As far as I can see it must be an error within the Windows MIB, not picking up the ethernet traffic for the wifi card.

I might produce a small test script for him to run, to see what, if any, of the function for dreadnet.dll and hence Windows MIB work for him.

Out of interest what functions of the Windows MIB do you use to return the values of Inbytes,Outbytes,Infmat,Outfmat.

Thanks for your support Dread

[Dr. Dread]

It's the MIB_IFROW structure.

Greetz
Dread