Hello
Vincent,
Hello
Anders,
It looks like we all have a
common mother! J Interesting!
Many thanks for your
hints!
Right now have the problem, that
we receive a crash on wireshark, when we open the pcap file including one
NAS-EPS(LTE) message.
The error message tells us:
“Runtime Error! – Program: C:\Program Files\Wireshark\wireshark.exe – This
application has requested the Runtime to terminate it in an unusual way. Please
contact the application support team for more
information.”
What we have done
before?
We “captured” a NAS (LTE)
message outside of wireshark. This message was just extracted from a trace line,
we receive from LTE platform (UE). This NAS message is expected to be
correct.
Then we translated this text
line (adding a ‘000000’ in front of the NAS message) to pcap format. We
use the command:
"c:\Program
Files\Wireshark\text2pcap.exe" -l 147 NAS_message_test_6.txt
NAS_message_test_6.pcap
We use a preference setup for
the User 0 (DLT-147) and reference to protocol NAS-EPS in wireshark. (User 0
(DLT=147), NAS-EPS,0,””’,0,””
When we start wireshark, we
crash.
Do we something wrong, or could
it be an error?
Many
thanks!
Best
regards
Karl
Heinz Eckstein
Both the
NAS-EPS dissector and the LTE-RRC dissector are fairly well updated however you
need to call them by using a User DLT
From:
wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]
On Behalf Of Karl-Heinz ECKSTEIN
Sent: den 17 februari 2011
18:00
To: wireshark-dev@xxxxxxxxxxxxx
Subject:
[Wireshark-dev] Staus of ASN.1 dissectors - RRC and NAS-EPS (for
LTE)
Hello,
May I ask, which status is applicable on ASN.1, especially
dissector of RRC and NAS-EPS.
I’m asking, because I’m trying to dissector a pcap file,
which I had generated via text2pcap from a LTE NAS message.
The NAS message is not “decoded”/dissectored by wireshark in
my example. But NAS-EPS is available in Filters but not in
preferences.
I’m using latest 1.5.1 build.
Many thanks for any help about this.
Best
regards
Karl
Heinz Eckstein