Your description of the symptom is exactly correct. With one corruption the bad data was 1368 bytes long, with another 1448 bytes.
The sender is an access point. I've noticed the problem with three different access points. The receiver is an Acer with ath5k driver. My home access point is configured with RTS threshold 2346, fragmentation 2346, beacon interval 100ms, DTIM interval 1, short preamble, CTS mode auto, WEP encryption. I should be able to collect packet traces with wireshark. Can you recommend wireshark configuration options that are maximally helpful? I can transfer small files containing ASCII data until I see a mismatch. bob ==================== On Tue, May 25, 2010 at 2:45 PM, Bob Copeland <m...@bobcopeland.com> wrote: > On Tue, May 25, 2010 at 1:40 PM, Robert Brown <robert.br...@gmail.com> wrote: >> The symptom is a block of data, roughly 1400 bytes in size, that appears >> twice in a row in the destination file. The first instance of the repeated >> data >> is erroneous. It does not match the source file. The second instance of >> the repeated data block is correct. > > Ok, just to make sure I have it: one 1400ish-byte block in the file gets > replaced with the data from the subsequent block, and the data that was > supposed to be in that block was lost? > > 1400 is about the size of an MTU... ath5k is the receiver and the > sender is some AP? Do you have the frag threshold configured? > > Ok, yes, a block of 'As' wouldn't help, but perhaps alternating different > letters every 500 bytes or so. If you have enough space, a wireshark packet > capture of the transfer may give clues. > > -- > Bob Copeland %% www.bobcopeland.com _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
