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

.rf5 file opening error

0

When I try to open error a file *.rf5 it throw up error, its ATM catpure.

HLAYER      "MTP-2"     "../../protocols/base/base.upd*"    LOADED  "K12xx decoder base - english version"
LAYER       "SSCOP"     "../../protocols/bisup/sscop.upd1"  LOADED  "SSCOP ITU Q.2100, 07/1994 [06.05.02]"
LAYER       "AAL2L3"    "../../protocols/umts_common/aal2l3.upd1"   LOADED  "ITU-T Q.2630.1/2 AAL2 Signalling CS1/2"
RELATION    "BASE"      "SSCOP" UNCOND  POSITION 290 416 290 390
RELATION    "SSCOP"     "AAL2L3"    UNCOND  POSITION 290 350 290 303
DECKRNL     "MTP-2"     LSBF    UPD_DK
DECKRNL     "SSCOP"     MSBF    UPD_DK
DECKRNL     "AAL2L3"    LSBF    UPD_DK
LAYPOS      "BASE"      150 416 430 486
LAYPOS      "MTP-2"     10  10  70  50
LAYPOS      "SSCOP"     260 350 320 390
LAYPOS      "AAL2L3"    256 263 324 303

Format : error opening file.

asked 19 Jul '11, 02:51

deessing's gravatar image

deessing
1111
accept rate: 0%

edited 20 Nov '13, 13:28

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k335196


2 Answers:

0

It appears that Wireshark does not currently support the K18 file format; K12 and K15 are listed as supported, but not K18. Also see this question and answer.

answered 09 May '12, 09:43

JeffMorriss's gravatar image

JeffMorriss ♦
6.2k572
accept rate: 27%

0

Try one of the automated builds with a version number of "SVN-53452" or later; somebody finally filed a bug for a failure to read a k18 capture, and attached a capture file that showed the problem, so it was finally possible for some reverse-engineering to be done to handle that file, at least.

If that still doesn't handle it, file another bug, and attach the capture file, so that more reverse-engineering can be done.

answered 20 Nov '13, 13:27

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k335196
accept rate: 19%