Snort mailing list archives

RE: Error initializing NIC


From: Reinhard Doberstein <r.doberstein () typoart de>
Date: Wed, 24 Apr 2002 15:20:57 +0200

Hi,


-----Original Message-----
From: Rich Adamson [mailto:radamson () routers com]
Sent: Wednesday, April 24, 2002 3:18 PM

If I understand your issue correctly, try running snort from 
the Windows
command line as "snort -W". 

With "snort -W" i got:

.................................................................

F:\Programme\Sourcefire\Snort>snort -W

-*> Snort! <*-
Version 1.8-WIN32 (Build 103)
By Martin Roesch (roesch () sourcefire com, www.snort.org)
1.7-WIN32 Port By Michael Davis (mike () datanerds net,
www.datanerds.net/~mike)
1.8-WIN32 Port By Chris Reid (chris.reid () codecraftconsultants com)
          (based on code from 1.7 port)

Interface       Device          Description
-------------------------------------------
1

.................................................................

so i got nothing by Device or Description. And that happend on all machines.
I think this is the problem.


Select the appropriate NIC card interface
that you'd like to use, and enter that number in the IDS 
Center's general
setup screen where it says "Network Interface #".

On IDScenter (1.09 Beta 1.3) i go a "Generate a script first" msg if i click
on "Test configuration". On another machine i go an error on "Test
configuration", after installing some rules. Sorry, haven't the message
here.


Also, I'm not sure of the status of this problem, but IDS 
Center has had
a problem for about six months relative to "where" it is 
installed on a
Windows machine. The author did not correctly handle 
"\Program Files" in
any part of the software (the space between Program and Files 
blows IDS
Center out of the water). If you install both snort and IDS Center in
any directory that does not include a space in the name, the issue
disappears. I've been running snort and IDScenter (v1.09 beta 
1.1) on a

No spaces in the path. But all OSs are in german. Could this be a problem?

And WinDump on one of the machine works withould error. So i think this
isn't a problem from the WinPcap installation. 

Anything that i can test?


By
Reinhard


Btw. Better answer in the list, i am not the only with this problem.

--
Reinhard Doberstein
mailto:r.doberstein () gmx de http://www.doberstein.com

_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users


Current thread: