Very useful wireshark fix for NS / BSSGP decoding
laforge at osmocom.org
Sat Feb 13 17:16:43 UTC 2021
In case anyone has been annoyed by this before:
wireshark so far always showed _only_ the BSSGP decode in the Information column
of a Gb interface pcap file, even if that BSSGP was contained in the "erroneous
message" IE of a NS-STATUS message.
This made it particularly difficult to spot NS-STATUS, and without custom
coloring rules or search filters, a protocol trace would just look fine - except
that in reality it isn't.
I've now found out what's the proper method to resolve this and submitted
a patch to wireshark, which was merged very quickly:
After this change, the Information column in the packet list will show
NS-STATUS with the human-redaable cause value for the reject, rather than
displaying BSSGP as if nothing odd happened.
- Harald Welte <laforge at osmocom.org> http://laforge.gnumonks.org/
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
More information about the osmocom-net-gprs