RE: Setting up a Windowz Interface to monitor with no IP Address

["McCammon, Keith" <Keith.McCammon () eadvancemed com>]

Am I missing something!?!  Why steps two through four?  There's no reason to have TCP/IP enabled at all on that 
interface.  Winpcap is doing the work, not the (shady) Windows IP stack.

-----Original Message-----
From: CJATeck () aol com [mailto:CJATeck () aol com]
Sent: Friday, June 28, 2002 11:25 AM
To: McCammon, Keith; tslighter () itc nrcs usda gov; michaels () silicondefense com; scotw () hotmail com
Cc: snort-users () lists sourceforge net
Subject: Re: [Snort-users] Setting up a Windowz Interface to monitor with no IP Address


I do NOT use the registry hack although I am aware of it, for my "External Interface" I do the following.

1) I use a copper tap (Finisar) as the physical device to intercept traffic between my boundary router and the outside 
firewall interface, as this is a "recieve only" device, it provides protection at the OSI phyical layer.
2) On a WIN32 box I disable ALL but the TCP/IP stack. (NO file& print, NO MS client, ect)
3) I leave the interface set for "DHCP", no hard IP info (NO unicast address, NO subnet, NO DNS, ect)
4) I disable the DHCP service.

RESULT- provides a promiscuous interface that is protected from detection and intrusion at both layer 1 and layer 3 of 
the OSI model.

Hope this clarify things.

Cliff

In a message dated 6/28/2002 11:07:52 AM Eastern Daylight Time, Keith.McCammon () eadvancemed com writes: 


How about just disabling TCP/IP on that interface by un-checking the component?  Why muck around with the registry?



-----Original Message-----
From: CJATeck () aol com [mailto:CJATeck () aol com]
Sent: Friday, June 28, 2002 10:51 AM
To: tslighter () itc nrcs usda gov; michaels () silicondefense com; scotw () hotmail com
Cc: snort-users () lists sourceforge net
Subject: Re: [Snort-users] Setting up a Windowz Interface to monitor with no IP Address