Re: One NIC on public side

["Gianluca Varenni" <gianluca.varenni () cacetech com>]

On NIC1 you can totally disable the TCP/IP stack. Go to the properties of 
that network connection, in the list of services/protocols bound to that 
NIC, uncheck TCP/IP.

This will still allow you to capture, but there won't be any protocol bound 
to that NIC apart from the WinPcap driver.

Have a nice day
GV

--------------------------------------------------
From: <mike () grounded net>
Sent: Wednesday, May 12, 2010 9:18 PM
To: "wireshark-users" <wireshark-users () wireshark org>
Subject: [Wireshark-users] One NIC on public side

> The server I'm using wireshark on has two NICs.
> I put NIC0 on the LAN side which is how I remotely manage the server.
> I put NIC1 on a hub just before the firewall so that I can see all public 
> traffic before it hits the firewall.
>
> On NIC1, I do not have any IP assigned which is on my lan but have 
> 169.254.1.2 on it.
> From what I understand, the NIC goes into promiscuous mode when wireshark 
> and other network monitoring software fires up to use that NIC.
>
> What I wondered about was, just now safe is it to have that NIC on the 
> public side?
>
> Thanks.
>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>
> mailto:wireshark-users-request () wireshark org?subject=unsubscribe 

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe