Ethereal-users: RE: [Ethereal-users] Why is ethereal on widows only capturing "1" (one)packet?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Andy Davis" <adavis@xxxxxxxxxxxx>
Date: Thu, 4 Aug 2005 14:46:58 -0400

Uh, this is embarrassing. If anyone has ever heard of Alienware and their widows theme packages, you may be aware that is doesn’t work well with GTK at all. The packets were there in the list of ethereal all along but were not visible because the text and background were both white while using the alienware theme’s color scheme. Pretty hard to read!!!

 

Mystery solved.

 


From: ethereal-users-bounces@xxxxxxxxxxxx [mailto:ethereal-users-bounces@xxxxxxxxxxxx] On Behalf Of Andy Davis
Sent: Thursday, August 04, 2005 2:31 PM
To: ethereal-users@xxxxxxxxxxxx
Subject: [Ethereal-users] Why is ethereal on widows only capturing "1" (one)packet?

 

I’m capturing with ethereal on Debian without any problem. Unfortunately, at the other end, I only have a windows box.

 

Here are the particulars:

 

Version 0.10.11 (C) 1998-2005 Gerald Combs <gerald@xxxxxxxxxxxx>

Compiled with GTK+ 2.4.14, with GLib 2.4.7, with WinPcap (WinPcap_3_1_beta4-1),

with libz 1.2.2, with libpcre 4.4, with Net-SNMP 5.1.2, with ADNS.

Running with WinPcap version 3.1 beta4 (packet.dll version 3, 1, 0, 24), based on libpcap version 0.8.3 on Windows XP Service Pack 2, build 2600.

 

While I’m still looking for this answer, I figured I’d drop a message here too.

 

Why is ethereal on widows only capturing “1” (one) packet?

 

 

The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.