Wireshark-users: Re: [Wireshark-users] strange ping behavior
From: "Manu" <traqueur@xxxxxxxxxxxxxxxx>
Date: Fri, 9 Apr 2010 08:34:49 +0200
Yes it's exactly that.3 pings give 6 packets and it's the same for every communication. How could it be mirrored ? By NIC ? ----- Original Message ----- From: "M K" <gedropi@xxxxxxxxx>
To: "Community support list for Wireshark" <wireshark-users@xxxxxxxxxxxxx> Sent: Friday, April 09, 2010 1:36 AM Subject: Re: [Wireshark-users] strange ping behavior
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@xxxxxxxxxxxxxxxx> 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@xxxxxxxxx>To: "Community support list for Wireshark" <wireshark-users@xxxxxxxxxxxxx>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@xxxxxxxxxxxxxxxx> wrote:No. Time Source Destination ProtocolInfo 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 ProtocolNo. Time Source Destination ProtocolInfo 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 serverWhen I ping another box in my office with ping -n 1 192.168.10.13 insteadof 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 ProtocolNo. Time Source Destination ProtocolInfo 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 ProtocolNo. Time Source Destination ProtocolInfo 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@xxxxxxxxxxxxx>Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?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@xxxxxxxxxxxxx>Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?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@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
- Follow-Ups:
- Re: [Wireshark-users] strange ping behavior
- From: Ian Schorr
- Re: [Wireshark-users] strange ping behavior
- References:
- [Wireshark-users] strange ping behavior
- From: Manu
- Re: [Wireshark-users] strange ping behavior
- From: M K
- Re: [Wireshark-users] strange ping behavior
- From: Manu
- Re: [Wireshark-users] strange ping behavior
- From: M K
- [Wireshark-users] strange ping behavior
- Prev by Date: [Wireshark-users] Wireshark utility problem with openflow-netfpga switch
- Next by Date: Re: [Wireshark-users] To many STP protocol
- Previous by thread: Re: [Wireshark-users] strange ping behavior
- Next by thread: Re: [Wireshark-users] strange ping behavior
- Index(es):