Have you a machine with this problem at hand? I'd be very interested in seeing some debug output from such a machine, since we are not able to reproduce the problem in our lab, although many users report it. I suspect that it's due to an underdimensioned buffer in the function that gathers the device names, but I have no proofs at the moment.
Loris > Going back to version 2.2 of WinPcap may fix your problem. If you do a > "snort -W" and get a listing of only "1", then installing WinPcap 2.2 > will most likely fix the problem. If you do see multiple adapters using > "snort -W", then you can use the -i switch to choose the adapter you > would like to sniff on. > > There is a new compile of Snort on our website that fixes the problem > with the latest Snort and WinPcap. > > Michael Steele | Support Technician > mailto:[EMAIL PROTECTED] > Silicon Defense: IDS solutions - http://www.silicondefense.com > Snort: Open Source Network IDS - http://www.snort.org > > > > -----Original Message----- > From: Loris Degioanni [mailto:[EMAIL PROTECTED]] > Sent: May 2, 2002 2:02 AM > To: [EMAIL PROTECTED] > Subject: Re: [WinPcap-users] WinPcap problem > > > Hi All. > > > > I need help with two problems I have with WinPcap. (I am working with > the > > last WinPcap version 2.3, under win98) > > > > > > > > 1. I can't work with two net cards with the same name, a problem I > > already saw in the FAQ section. > > > > > > > > The second card is nor working - I can't access it. > > > > > > > > Do you know or have information about the problem ? > > If I remember well, the name of the network devices is obtained by > winpcap > from the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\ > registry hive. Win9x gives the same internal name (something like > ndis0001) > to identical network adapters, so winpcap is unable di distinguish them. > Some users were able to make winpcap work correctly modifying this > registry > location, changing the name of the second adapter. Obviously, we > discourage > this kind of operation because it can cause serius damage to the > protocol > stacks. ;-) > > > Is there a solution for the problem or you will have a solution for > > it ? > > > > > > > > > > > > 2. It is impossible to work with net card with the name - PCINT. > > > > > > > > Working with this card causes a total fail of Win98. (I used your > > examples) > > What kind of interface is it? > > > Loris > > > > > > > Regard's > > > > Parancher Semion > > Automatic Test Equipment Development Dep. > > RAD Data Communications Ltd. > > Phone: +972-3-6455145 > > Fax : +972-3-6488785 > > Email: semion_p <mailto:[EMAIL PROTECTED]> @rad.co.il > > > > >
