All
Attached is the summary printout of a standard Windows ping exchange
between a Windows XP client and a Linux server.
The capture is recorded on the client issuing the ping.
The apparent doubling of all outgoing packets is the issue.
I suspect that the issue is related to fire walling on the client, but
would appreciate any assistance that the Ethereal team can offer.
This irritating feature is a fairly recent innovation and affects all our
standard build clients.
No. Time Source Destination Protocol
Info
1 0.000000 156.71.13.234 Broadcast ARP Who
has 156.71.12.4? Tell 156.71.13.234
2 0.000035 156.71.13.234 Broadcast ARP Who
has 156.71.12.4? Tell 156.71.13.234
3 0.000366 156.71.12.4 156.71.13.234 ARP
156.71.12.4 is at 00:b0:d0:65:e6:96
4 0.000382 156.71.13.234 156.71.12.4 ICMP Echo
(ping) request
5 0.000397 156.71.13.234 156.71.12.4 ICMP Echo
(ping) request
6 0.000588 156.71.12.4 156.71.13.234 ICMP Echo
(ping) reply
7 1.001438 156.71.13.234 156.71.12.4 ICMP Echo
(ping) request
8 1.001468 156.71.13.234 156.71.12.4 ICMP Echo
(ping) request
9 1.001825 156.71.12.4 156.71.13.234 ICMP Echo
(ping) reply
10 2.002606 156.71.13.234 156.71.12.4 ICMP Echo
(ping) request
11 2.002637 156.71.13.234 156.71.12.4 ICMP Echo
(ping) request
12 2.002820 156.71.12.4 156.71.13.234 ICMP Echo
(ping) reply
13 3.002792 156.71.13.234 156.71.12.4 ICMP Echo
(ping) request
14 3.002824 156.71.13.234 156.71.12.4 ICMP Echo
(ping) request
15 3.003091 156.71.12.4 156.71.13.234 ICMP Echo
(ping) reply
The issue occurs with all versions of Ethereal that we have tried on these
systems recently and with both the production and latest release of
WinPcap.
>From the capturing client:-
**********************************************************************************
Version 0.10.11 (C) 1998-2005 Gerald Combs <gerald@xxxxxxxxxxxx>
Compiled with GTK+ 2.4.14, with GLib 2.4.7, with WinPcap (version
unknown),
with libz 1.2.2, with libpcre 4.4, with Net-SNMP 5.1.2, with ADNS.
Running with WinPcap (3.0) on Windows XP Service Pack 1, build 2600.
**********************************************************************************
I suspect that though the client is not admitting to SP2 that large
numbers of fixes from that release are incorporated, and harbour dark
suspicions that one of these is the cause of the problem.
Harry Moyes