] exported_pdu 3GPP Cell identity, question on PLMN
encoding
Hi Mauro,
NAS layer is also using little endian encoding.
Anyway I do not really car as long as we specify whether we use big endian or
little endian, both are supported by Wireshark. If you prefer little endian
that's fine.
Hi Pascal,
Some additional info. Both formats exist for the PLMN Id.
One is called "little-endian" MNC encoding in Wireshark's code.
[0] MCC digit 2, MCC digit 1
[1] MNC digit 3, MCC digit 3
[2] MNC digit 2, MNC digit 1
While the one I wrote in my original email is the "big-endian" MNC
encoding.
From: Pascal Quantin. Friday, June 28, 2024 17:21
> Actually what I wrote is the encoding I'm used to, and that
> does not match either the rules you defined.
> Did you mean:
> [0] MCC digit 2, MCC digit 1
> [1] MNC digit 3, MCC digit 3
> [2] MNC digit 2, MNC digit 1
> Instead of:
> [0] MCC digit 2
Le ven. 28 juin 2024 à 17:07, Mauro Levra
a écrit :
> Thanks, Pascal. Yes, of course. This is what I meant.
> I completely reversed the order when writing the example by hand. :)
>
Actually what I wrote is the encoding I'm used to, and that does not match
either the rules you defined.
Did you me
Thanks, Pascal. Yes, of course. This is what I meant.
I completely reversed the order when writing the example by hand. :)
From: Pascal Quantin
Sent: Friday, June 28, 2024 17:03
This does not seem correct. Using your encoding rules, you should instead hav
Hi Mauro,
Le ven. 28 juin 2024 à 16:55, Mauro Levra via Wireshark-dev <
wireshark-dev@wireshark.org> a écrit :
> Hi,
>
> I am working on adding a 3GPP Cell Identity tag to the
> exported_pdu header. A single-octet type field precedes the
> actual value and specifies if the identity is the CGI, EC
Hi,
I am working on adding a 3GPP Cell Identity tag to the
exported_pdu header. A single-octet type field precedes the
actual value and specifies if the identity is the CGI, ECGI,
or NCGI.
I have a question about the PLMN component at the beginning of
each global identity field. There are several
