ndislwf monitoring filter preventing network connectivity
in [Device Drivers]
|
Prev: Need help with Network Packet filtering (IDS)
Next: Communicating with CD DVD devices - port driver ? class driver ?
From: g b on 6 Jan 2010 18:23 Hi, I've modified the ndislwf to be a monitoring filter that binds below at the native 802.11 layer (below native wifi) at the "custom" level in Windows Vista. The sample works great, but the problem is whenever I install the driver it prevents network connectivity. I'm NOT putting it into monitor mode or some such where it can't sustain active connections, nor have I changed anything in ndislwf that, as far as I know, would cause this (it's still a "pass through" filter). When I do an "ipconfig /all" in a command window after it has been installed, the 802.11 device does not appear. Also, using Window's "connect to wireless network" feature, I can see the other wireless networks with the driver installed, but attempting to connect to them fails. The cause of this has been eluding me and any suggestions would be greatly appreciated!
From: Thomas F. Divine on 6 Jan 2010 19:17 Probably a problem with your "custom" level. A monitoring LWF can work under Native Wi-Fi without breaking connectivity if the operation mode is left unchanged. Good luck, Thomas F. Divine http://www.pcausa.com "g b" <gb952325(a)gmail.com> wrote in message news:c2c74ba7-fb61-4f28-a9eb-8199527a06cc(a)g31g2000vbr.googlegroups.com... > Hi, > > I've modified the ndislwf to be a monitoring filter that binds below > at the native 802.11 layer (below native wifi) at the "custom" level > in Windows Vista. The sample works great, but the problem is whenever > I install the driver it prevents network connectivity. I'm NOT > putting it into monitor mode or some such where it can't sustain > active connections, nor have I changed anything in ndislwf that, as > far as I know, would cause this (it's still a "pass through" filter). > When I do an "ipconfig /all" in a command window after it has been > installed, the 802.11 device does not appear. Also, using Window's > "connect to wireless network" feature, I can see the other wireless > networks with the driver installed, but attempting to connect to them > fails. > > The cause of this has been eluding me and any suggestions would be > greatly appreciated!
From: Pradeep on 1 Feb 2010 23:14
You have to modify the FilterAttach function in ndislwf sample, to accept 802.11 connections. Sample is written to accept only 802.3 adapter connections. --- frmsrcurl: http://msgroups.net/microsoft.public.development.device.drivers/ndislwf-monitoring-filter-preventing-network-connect |