This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Frame xxx too long

0

Hi, I'm working on wireshark to sniff the channel on which there are associated some nodes to one coordinator (it's a wireless sensors network). The tx power is set to 0dB, somentimes it appears an error saying "the frame xxx is too long" and there is the payload (sometimes negative, sometimes positive) into round brackts. I'm tx varying the size of the payload from 5 bytes to 50 bytes, with steps of 5 bytes but I do not know which could be the problem. Is there anyone that can help me? Thanks best regards Ivana

asked 10 Feb '14, 10:45

Ivana%20Ester%20Marra's gravatar image

Ivana Ester ...
11112
accept rate: 0%

Some questions:

  • what is your OS and OS version of the Wireshark system?
  • what is your Wireshark version?
  • how do you capture the traffic (with Wireshark, or other tools)?
  • on which interface do you capture?
  • is it possible to post a sample capture file somewhere (google drive, dropbox, cloudshark.org)?
(10 Feb '14, 11:30) Kurt Knochner ♦

Hi, thanks for you reply. I'm using windows 7 and the versione of Wireshark is 1.10.5. I have a sniffer connected to the pc thanks to which is possible to sniff the channel through \.\pipe\wireshark. The problem occurs only in this case, before that I have programmed the same nodes with tx power -5dBm and everything is gone well. I attach the screenshot of the error/message as you can see. https://www.dropbox.com/s/mlk7g4tba8jo4xf/errore.jpg

Thanks Ivana

(11 Feb '14, 01:12) Ivana Ester ...

Looks like the capture file is damaged. Did you transfer the file via FTP or is that error message shown while you do a live capture?

(11 Feb '14, 01:21) Kurt Knochner ♦

No. How can it be possible? no problems just changing the power in the software. Could it be the interference on the channel? I don't think so, actually.

(11 Feb '14, 01:23) Ivana Ester ...

One Answer:

0

The software that writes to the pipe could be buggy... If possible, let that software write a capture file directly, instead of writing to a pipe.

You can also try to use dumpcap to read from the pipe and write a capture file.

Regards
Kurt

answered 11 Feb '14, 01:54

Kurt%20Knochner's gravatar image

Kurt Knochner ♦
24.8k1039237
accept rate: 15%

edited 11 Feb '14, 01:58