Le jeu. 20 juin 2024 à 12:16, Anders Broman a écrit :
> My first thought would be to keep it simple and use a tag per address.
> Plenty of tag namespace.
>
Could we use a single tag for 3GPP global cell identifier, and then 1 byte
for the cell identity type followed by the identity itself? This w
My first thought would be to keep it simple and use a tag per address.
Plenty of tag namespace.
Den tors 20 juni 2024 11:35Mauro Levra
skrev:
> > Instead of dedicating a bit to the enterprise flag, we could also
> > define a specific tag for the IANA-PEN, then the enterprise number
> > itself fo
> Instead of dedicating a bit to the enterprise flag, we could also
> define a specific tag for the IANA-PEN, then the enterprise number
> itself followed by its private payload. This way we keep the full
> range of value tags at the cost of 2 extra bytes per packet.
Thank you, Pascal, for the sug
Hi Mauro,
Instead of dedicating a bit to the enterprise flag, we could also define a
specific tag for the IANA-PEN, then the enterprise number itself followed by
its private payload. This way we keep the full range of value tags at the cost
of 2 extra bytes per packet.
Presumably we will need a
Not against the suggestion per se but isn't it better that you write an MR
including the new tags you need so that wireshark can read your files?
Best regards
Anders
Den tors 20 juni 2024 06:30Mauro Levra via Wireshark-dev <
wireshark-dev@wireshark.org> skrev:
> Dear all,
>
> I have been looking
Dear all,
I have been looking for a way to store 4G and 5G RAN/Core signaling traces in
pcapng. Its lack of support for 5G traces made me abandon gsmtap and focus on
the exported_pdu protocol that allows me to specify the dissector to apply and
hence can handle any protocol.
The TLV approach f
