Doug,
Although the WinPcap 3.1 driver is labelled beta, I have never encountered a
single crash with them. There's even a beta4 you can get from
http://winpcap.polito.it/install/default.htm in the case you want to try it.
I'm thinking this might be the cause, although I have no hard evidence I can
rely upon.
On what network are you capturing (LAN, Wireless, or PPP link)?
And, are you capturing in promiscuous mode or not? This only matters for
wireless links.
Best regards,
Olivier
----- Original Message -----
From: Douglas Burdett
Oliver,
I tried unchecking all the Name Resolution selections and it didn't seem
to help. I am running WinPcap 3.0. which seems to be the latest
released version. Do I need to be running a beta version?
Just to reiterate: I am able to capture packets just fine as long as I
don't check "Update list of packets in real time".
Thanks for your help
Doug
-----Original Message-----
From: Olivier Biot
Doug,
This is strange. It works on my computer (0.10.8 with WinPcap 3.1 beta3)
on
my wireless link (ATMEL chip, no promiscuous mode).
Try starting a capture while unticking the "Enable network name
resolution"
option in the capture options dialog.
Best regards,
Olivier
----- Original Message -----
From: Douglas Burdett
Oliver,
I tried toggling the "Enable concurrent DNS name resolution" and got
the
same result whether it was enabled if disabled.
Doug
-----Original Message-----
From: Olivier Biot
This is probably related to the address-to-name resolutions, which may
take
time to complete (e.g., temporarily slow name server). On Ethereal
0.10.8,
go to Edit > Preferences, and select "Name Resolution" from the left
pane.
There are 2 options:
1. Enable concurrent DNS was disabled. Enable it and perform another
test.
2. If this fails, I guess Enable network name resolution is enabled.
Disable
it and perform another test.
Should you still have problems, then reply to this post.
Best regards,
Olivier
----- Original Message -----
From: Douglas Burdett
I am a new user of Ethereal on Windows XP SP2 but I am having no luck
using
the "Update list of packets in real time" option on the Capture. When
I
select that option, the Ethereal hangs and must be closed from the
Task
Manager. After the Ethereal is cancelled then I see the capture begin
to
function.
As I understand it, whenever the "Update list of packets in real time"
option is selected, the capture is executed as a separate task which
writes
into the capture file, while the original Ethereal task reads data
from
that
file. It seems to me that the Capture task is somehow prevented from
running until the original Ethereal is cancelled.
Obviously that defeats the purpose of the "Update list of packets in
real
time" option. Can anyone suggest a possible cause for this and more
importantly, a solution?
Thanks
Doug Burdett
