Shoutbox

LOL. You think that's what causing the problem? Intel's crappy drivers?

quote:

---

Originally posted by Zeh
I don't think it's the drivers cookie

---

search the web for code for sniffers. In almost every piece of code you'll find they talk about it and say that some drivers are the cause for raw sockets not being able to be opened (on wireless). After changing drivers they work...

quote:

---

Originally posted by Zeh
but for the case it is could you tell me what are the best drivers for the "INTEL Pro/Wireless 2200BG network connection" hardware version 0.1.3. My current driver version is 9.0.1.9.

---

I can't unless I search for them myself; there are hundreds if not thousands of drivers out there... sorry...

Ok. Actually my new theory is that the intel drivers suck! lol. It seems its people with intel wireless hardware and drivers that have this problem. I hope intel released drivers that correct this issue. If not I can't use scripts with Xniff.

EDIT: Ok I've downloaded the latest driver from intel's site for my adapter, v. 9.0.4.17, going to download nudgeback again and see if it does work now. You should try to download the latest driver from itel's site for your adapter too alex and then try to see if the xniff starts working on you connection.

EDIT(2): Well the nudge back doesn't work but i don't think it's the Xniff fault, it crashes the WLM when I import or activate it and when active the "/" command it is supposed to add doesn't appear in the list so i'm gessing this is the scripts fault. Can anyone tell me another script that uses Xniff.ocx that I could try to see if my wireless is working well now with the sniffer?

Pai,

How do I access your activex onData event in c++?

I've done a wrapper class but can't use the event.

Thanks