THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.

Revision history  [back]

Decoding NAS-5GS with 5G-EA0

Hi All,

Some of my NAS-5GS messages such as UE response to the Security Mode Cmd that AMF sends right after successful UE authentication, followed by a few more messages before AMF sends ICSReq back to the UE are still displayed as encrypted even though I use 5G-EA0 (alone) at each end of my N2: http://drive.google.com/file/d/1SThy_zWoR8JOFdSMZGYMrBBAW02bm9YO/view?usp=sharing

Here's a pcap with that message (amended - was a wrong one before): https://drive.google.com/file/d/1FfUEgApe4WyVZMxUcyQwri-hSQF_RWg2/view?usp=sharing

Does Wireshark have any problems decoding NAS-5GS in it assuming it's in a valid 5G-EA0 format? As per 3GPP 24.501 4.4.5 this is "null ciphering algorithm".

I'm seeing it with the current stable WS version 3.4.0 (v3.4.0-0-g9733f173ea5e). Before this one I had 3.2.2, which couldn't decode even the Security Mode Cmd from the AMF immediately preceding the one in question. This 3.4.0 one does decode it but none of the next 4 messages exchanged in NGAP DL/UL NAS Transport (both 3.2.2 and 3.4.0 seem to decode all subsequent messages exhanged afterwards though, starting with ICSReq).

Many thanks in advance!

Decoding NAS-5GS with 5G-EA0

Hi All,

Some of my NAS-5GS messages such as UE response to the Security Mode Cmd that AMF sends right after successful UE authentication, followed by a few more messages before AMF sends ICSReq back to the UE are still displayed as encrypted even though I use 5G-EA0 (alone) at each end of my N2: http://drive.google.com/file/d/1SThy_zWoR8JOFdSMZGYMrBBAW02bm9YO/view?usp=sharing

Here's a pcap with that message (amended - was a wrong one before): https://drive.google.com/file/d/1FfUEgApe4WyVZMxUcyQwri-hSQF_RWg2/view?usp=sharingmessage: https://drive.google.com/file/d/1GJbpmZN0N1TpqIkEND23RuCffrGje38P/view?usp=sharing

Does Wireshark have any problems decoding NAS-5GS in it assuming it's in a valid 5G-EA0 format? As per 3GPP 24.501 4.4.5 this is "null ciphering algorithm".

I'm seeing it with the current stable WS version 3.4.0 (v3.4.0-0-g9733f173ea5e). Before this one I had 3.2.2, which couldn't decode even the Security Mode Cmd from the AMF immediately preceding the one in question. This 3.4.0 one does decode it but none of the next 4 messages exchanged in NGAP DL/UL NAS Transport (both 3.2.2 and 3.4.0 seem to decode all subsequent messages exhanged afterwards though, starting with ICSReq).

Many thanks in advance!

Decoding NAS-5GS with 5G-EA0

Hi All,

Some of my NAS-5GS messages such as UE response to the Security Mode Cmd that AMF sends right after successful UE authentication, followed by a few more messages before AMF sends ICSReq back to the UE are still displayed as encrypted even though I use 5G-EA0 (alone) at each end of my N2: http://drive.google.com/file/d/1SThy_zWoR8JOFdSMZGYMrBBAW02bm9YO/view?usp=sharing

Here's a pcap with that message: https://drive.google.com/file/d/1GJbpmZN0N1TpqIkEND23RuCffrGje38P/view?usp=sharing

Does Wireshark have any problems decoding NAS-5GS in it assuming it's in a valid 5G-EA0 format? As per 3GPP 24.501 4.4.5 this is "null ciphering algorithm".

I'm seeing it with the current stable WS version 3.4.0 (v3.4.0-0-g9733f173ea5e). Before this one I had 3.2.2, which couldn't decode even the Security Mode Cmd from the AMF immediately preceding the one in question. AMF. This 3.4.0 one does decode it but none of the next 4 messages exchanged in NGAP DL/UL NAS Transport (both 3.2.2 and 3.4.0 seem to decode all subsequent messages exhanged afterwards though, starting with ICSReq).

Many thanks in advance!

Decoding NAS-5GS with 5G-EA0

Hi All,

Some of my NAS-5GS messages such as UE response to the Security Mode Cmd that AMF sends right after successful UE authentication, followed by a few more messages before AMF sends ICSReq back to the UE are still displayed as encrypted even though I use 5G-EA0 (alone) at each end of my N2: http://drive.google.com/file/d/1SThy_zWoR8JOFdSMZGYMrBBAW02bm9YO/view?usp=sharing

Here's a pcap with that message: https://drive.google.com/file/d/1GJbpmZN0N1TpqIkEND23RuCffrGje38P/view?usp=sharing

Does Wireshark have any problems decoding NAS-5GS in it assuming it's in a valid 5G-EA0 format? As per 3GPP 24.501 4.4.5 this is "null ciphering algorithm".

I'm seeing it with the It's current stable WS version 3.4.0 (v3.4.0-0-g9733f173ea5e). Before this one I had 3.2.2, which couldn't decode even the Security Mode Cmd from the AMF. This 3.4.0 one does decode it but none of the next 4 messages exchanged in NGAP DL/UL NAS Transport (both 3.2.2 and 3.4.0 seem to decode all subsequent messages exhanged afterwards though, starting with ICSReq).

Many thanks in advance!

Decoding NAS-5GS with 5G-EA0

Hi All,

Some of my NAS-5GS messages such as UE response to the Security Mode Cmd that AMF sends right after successful UE authentication, followed by a few more messages before AMF sends ICSReq back to the UE are still displayed as encrypted even though I use 5G-EA0 (alone) at each end of my N2: http://drive.google.com/file/d/1SThy_zWoR8JOFdSMZGYMrBBAW02bm9YO/view?usp=sharing

Here's a pcap with that message: https://drive.google.com/file/d/1GJbpmZN0N1TpqIkEND23RuCffrGje38P/view?usp=sharing

Does Wireshark have any problems decoding NAS-5GS in it assuming it's in a valid 5G-EA0 format? format indeed? As per 3GPP 24.501 4.4.5 this is "null ciphering algorithm".

It's current stable WS version 3.4.0 (v3.4.0-0-g9733f173ea5e). Before this one I had 3.2.2, which couldn't decode even the Security Mode Cmd from the AMF. This 3.4.0 one does decode it but none of the next 4 messages exchanged in NGAP DL/UL NAS Transport (both 3.2.2 and 3.4.0 seem to decode all subsequent messages exhanged afterwards though, starting with ICSReq).

Many thanks in advance!

Decoding NAS-5GS with 5G-EA0

Hi All,

Some of my NAS-5GS messages such as UE response to the Security Mode Cmd that AMF sends right after successful UE authentication, followed by a few more messages before AMF sends ICSReq back to the UE are still displayed as encrypted even though I use 5G-EA0 (alone) at each end of my N2: http://drive.google.com/file/d/1SThy_zWoR8JOFdSMZGYMrBBAW02bm9YO/view?usp=sharing

http://drive.google.com/file/d/1SThy_zWoR8JOFdSMZGYMrBBAW02bm9YO/view?usp=sharing Here's a pcap with that message: https://drive.google.com/file/d/1GJbpmZN0N1TpqIkEND23RuCffrGje38P/view?usp=sharing

Does Wireshark have any problems decoding NAS-5GS in it assuming it's in a valid 5G-EA0 format indeed? As per 3GPP 24.501 4.4.5 this is "null ciphering algorithm".

It's current stable WS version 3.4.0 (v3.4.0-0-g9733f173ea5e). Before this one I had 3.2.2, which couldn't decode even the Security Mode Cmd from the AMF. This 3.4.0 one does decode it but none of the next 4 messages exchanged in NGAP DL/UL NAS Transport (both 3.2.2 and 3.4.0 seem to decode all subsequent messages exhanged afterwards though, starting with ICSReq).

Many thanks in advance!

Decoding NAS-5GS with 5G-EA0

Hi All,

Some of my NAS-5GS messages such as UE response to the Security Mode Cmd that AMF sends right after successful UE authentication, followed by a few more messages before AMF sends ICSReq back to the UE are still displayed as encrypted even though I use 5G-EA0 (alone) at each end of my N2: http://drive.google.com/file/d/1SThy_zWoR8JOFdSMZGYMrBBAW02bm9YO/view?usp=sharing image description Here's a pcap with that message: https://drive.google.com/file/d/1GJbpmZN0N1TpqIkEND23RuCffrGje38P/view?usp=sharing

Does Wireshark have any problems decoding NAS-5GS in it assuming it's in a valid 5G-EA0 format indeed? As per 3GPP 24.501 4.4.5 this is "null ciphering algorithm".

It's current stable WS version 3.4.0 (v3.4.0-0-g9733f173ea5e). Before this one I had 3.2.2, which couldn't decode even the Security Mode Cmd from the AMF. This 3.4.0 one does decode it but none of the next 4 messages exchanged in NGAP DL/UL NAS Transport (both 3.2.2 and 3.4.0 seem to decode all subsequent messages exhanged afterwards though, starting with ICSReq).

Many thanks in advance!