Re: [Wireshark-users] Bad Checksum Packet

2008-02-11 Thread Guy Harris
Andreas Fink wrote: > in todays wired networks its rather rare to see invalid checksums > because it would mean that a packet get transmitted and received but > incorrectly received due to a bad wire o the like. The same applies for 802.11 wireless networks, at least - you might be more likel

Re: [Wireshark-users] Bad Checksum Packet

2008-02-10 Thread Andreas Fink
On 11.02.2008, at 06:35, Becky Vict wrote: Hi, The protocol that I'm interested in is TCP (ftp transfer). I've done as per recommended but the following is what I get. Transmission Control Protocol, Src Port: 5001 (5001), Dst Port: ftp- data (20), Seq: 1, Ack: 15169, Len: 0 Flags: 0x001

Re: [Wireshark-users] Bad Checksum Packet

2008-02-10 Thread Becky Vict
Hi, The protocol that I'm interested in is TCP (ftp transfer). I've done as per recommended but the following is what I get. Transmission Control Protocol, Src Port: 5001 (5001), Dst Port: ftp-data (20), Seq: 1, Ack: 15169, Len: 0 Flags: 0x0010 (ACK) 0... = Congestion Window Reduced (CWR):

Re: [Wireshark-users] Bad Checksum Packet

2008-02-10 Thread Stephen Fisher
On Sun, Feb 10, 2008 at 06:35:08AM -0800, Becky Vict wrote: > I would like to know if a packet is discarded due to bad checksum, > will it show in the capture? How to distinguish this quickly? What > display filter should I use for this? If the frame is discarded by the network card for a bad

[Wireshark-users] Bad Checksum Packet

2008-02-10 Thread Becky Vict
Hi everyone, I would like to know if a packet is discarded due to bad checksum, will it show in the capture? How to distinguish this quickly? What display filter should I use for this? Thanks. - Never miss a thing. Make Yahoo your homepage.__