imm ass packages

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

g.roelant at telenet.be g.roelant at telenet.be
Fri Dec 14 15:12:00 UTC 2012


sorry, i made a type

in wireshark i see 31 06 3f

in documentation is see 2d 06 3f
now you tell me that only the 3f is responsible for detecting a imm ass packet.

if i wanted to detect (grep) for imm ass., shall i look for 31 06 3f or 2d 06 3f?


----- Oorspronkelijk e-mail -----
Van: "oxccoxcc oxccoxcc" <oxccoxcc at yandex.ru>
Aan: "g roelant" <g.roelant at telenet.be>, "osmocomBB" <baseband-devel at lists.osmocom.org>
Verzonden: Vrijdag 14 december 2012 16:03:34
Onderwerp: Re: imm ass packages

wireshark processing of imm ass packets seems normally. Looks like a bug with partial release complete messages. But wireshark has a signature for it: http://anonsvn.wireshark.org/wireshark/trunk/epan/dissectors/packet-gsm_a_rr.c
Try to write in the wireshark forum.

14.12.2012, 14:22, "g.roelant at telenet.be" <g.roelant at telenet.be>:
> In wireshark i see immediate assignment packages...
> they are like 31 06 0f
> but in the documentation they are like 2d 06 3f
> what am i doing wrong?
> i'm listening to a belgium operator called proximus.
> kind regards




More information about the baseband-devel mailing list