Wireshark mailing list archives
Re: strange ping behavior
From: M K <gedropi () gmail com>
Date: Thu, 8 Apr 2010 15:36:27 -0800
Sorry. I just wondered if you set the '-n' to 3, for instance, if your pings increased to 6. This could help test the issue. LIke something would be mirrored, for example. On 4/8/10, Manu <traqueur () club-internet fr> wrote:
It's "ping -n" on windows machines I send 1 ping and I've got 2 reply Strange no? ----- Original Message ----- From: "M K" <gedropi () gmail com> To: "Community support list for Wireshark" <wireshark-users () wireshark org> Sent: Thursday, April 08, 2010 5:37 PM Subject: Re: [Wireshark-users] strange ping behaviorYou can control the number of pings by using the command: ping -c, with 'c' being the count number of pings you want to do. On 4/8/10, Manu <traqueur () club-internet fr> wrote:No. Time Source Destination Protocol Info 1 0.000000 192.168.10.3 192.168.10.13 ICMP Echo (ping) request Frame 1 (74 bytes on wire, 74 bytes captured) Ethernet II, Src: a4:ba:db:0e:d2:54 (a4:ba:db:0e:d2:54), Dst: 00:90:c2:c0:f8:fa (00:90:c2:c0:f8:fa) Internet Protocol, Src: 192.168.10.3 (192.168.10.3), Dst: 192.168.10.13 (192.168.10.13) Internet Control Message Protocol No. Time Source Destination Protocol Info 2 0.000093 192.168.10.3 192.168.10.13 ICMP Echo (ping) request Hello I'm running wireshark 1.2.6 on a windows2003 server When I ping another box in my office with ping -n 1 192.168.10.13 instead of having one packet, I have everything in double as you can see below: Any idea ? Frame 2 (74 bytes on wire, 74 bytes captured) Ethernet II, Src: a4:ba:db:0e:d2:54 (a4:ba:db:0e:d2:54), Dst: 00:90:c2:c0:f8:fa (00:90:c2:c0:f8:fa) Internet Protocol, Src: 192.168.10.3 (192.168.10.3), Dst: 192.168.10.13 (192.168.10.13) Internet Control Message Protocol No. Time Source Destination Protocol Info 3 0.001232 192.168.10.13 192.168.10.3 ICMP Echo (ping) reply Frame 3 (74 bytes on wire, 74 bytes captured) Ethernet II, Src: 00:90:c2:c0:f8:fa (00:90:c2:c0:f8:fa), Dst: a4:ba:db:0e:d2:54 (a4:ba:db:0e:d2:54) Internet Protocol, Src: 192.168.10.13 (192.168.10.13), Dst: 192.168.10.3 (192.168.10.3) Internet Control Message Protocol No. Time Source Destination Protocol Info 4 0.001245 192.168.10.13 192.168.10.3 ICMP Echo (ping) reply Frame 4 (74 bytes on wire, 74 bytes captured) Ethernet II, Src: 00:90:c2:c0:f8:fa (00:90:c2:c0:f8:fa), Dst: a4:ba:db:0e:d2:54 (a4:ba:db:0e:d2:54) Internet Protocol, Src: 192.168.10.13 (192.168.10.13), Dst: 192.168.10.3 (192.168.10.3) Internet Control Message Protocol ___________________________________________________________________________ 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-- All that is necessary for evil to succeed is that good men do nothing. ~Edmund Burke ___________________________________________________________________________ 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
-- All that is necessary for evil to succeed is that good men do nothing. ~Edmund Burke ___________________________________________________________________________ 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
Current thread:
- strange ping behavior Manu (Apr 08)
- Re: strange ping behavior M K (Apr 08)
- Re: strange ping behavior Manu (Apr 08)
- Re: strange ping behavior M K (Apr 08)
- Re: strange ping behavior Manu (Apr 08)
- Re: strange ping behavior Ian Schorr (Apr 09)
- Re: strange ping behavior Manu (Apr 12)
- Re: strange ping behavior Sake Blok (Apr 12)
- Re: strange ping behavior Manu (Apr 08)
- Re: strange ping behavior M K (Apr 08)