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

“Can’t dissect FP frame because no per-frame info was attached! over TCP

0

Hi ,i am unable to dissect fp frame packet over tcp anw we got the error ""Can't dissect FP frame because no per-frame info was attached!" plz responce

This question is marked "community wiki".

asked 24 May '13, 02:43

Ranjeet%20Nag's gravatar image

Ranjeet Nag
11●3●3●6
accept rate: 0%

edited 24 May '13, 02:49

2 Answers:

1

I thought FP was transgered over UDP only, but in general se athe similar questions http://ask.wireshark.org/tags/umts-fp/

answered 24 May '13, 03:53

Anders's gravatar image

Anders ♦
4.6k●9●52
accept rate: 17%

1

See: http://wiki.wireshark.org/FP

More specifically: The FP dissector is mostly functional, but can currently only be invoked while reading Catapult DCT2000 or Tektronix K12 format traces (these contain the additional information needed in order to properly decode the frames). It would be possible, but challenging, to decode the RRC messages describing the configuration of the lower layers, and use this information to infer how each FP frame should be decoded.

answered 24 May '13, 04:03

Pascal%20Quantin's gravatar image

Pascal Quantin
5.5k●10●60
accept rate: 30%

It actually works partly if NBAP and RRC signaling is present.

(24 May '13, 04:31) Anders ♦

Then we should update the Wiki page ;)

(24 May '13, 05:09) Pascal Quantin

How can we determine if RRC signalling is present? Is it as straightforward as seeing packets labelled as RRC? Or does it require some decoding?

(30 Aug '13, 08:51) davide0089