wgao at broadcom.com
Wed Jun 25 21:02:09 GMT 2008
Thank you all for the great answering and feedback.
In my case, reloading the "npf" driver by doing "net stop/start npf" can
solve the issue. The newly added adapter will be "recognized" by
From: winpcap-users-bounces at winpcap.org
[mailto:winpcap-users-bounces at winpcap.org] On Behalf Of Fish
Sent: Wednesday, June 25, 2008 12:42 PM
To: winpcap-users at winpcap.org
Subject: RE: [Winpcap-users] PacketOpenAdapter
-----BEGIN PGP SIGNED MESSAGE-----
Gianluca Varenni wrote:
> It's wrong. The WinPcap driver detects the adapters when it
> gets loaded into memory, not during installation (that merely
> registers the NPF driver as part of the services in the system).
Wow. I didn't know that. Thanks!
> A workaround to it is to force an unload of the driver. This can
> be done with the SCM APIs (asking the NPF service to stop), or with
> the command line "net stop npf". You do not need to restart the
> driver manually, as it gets done automatically by the WinPcap API.
Ah. Okay. That makes sense now. Thanks! (again!) :)
(Gee, you learn something new every day on this list!) ;-)
> There is just a caveat to it. You cannot unload the driver if you
> have any open capture instances (i.e. any open pcap_t handles).
Knew that. :)
> Have a nice day
You too Gianluca. (and thanks again for the correction!)
"Fish" (David B. Trout) - fish(at)infidels.org
Fight Spam! Join CAUCE! <http://www.cauce.org/>
(Any HTML email received will be deleted unread)
PGP key fingerprints:
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1
-----END PGP SIGNATURE-----
Winpcap-users mailing list
Winpcap-users at winpcap.org
More information about the Winpcap-users