baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

Re: imm ass packages
by g.roelant＠telenet.be 15 Dec '12

15 Dec '12

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(a)yandex.ru> Aan: "g roelant" <g.roelant(a)telenet.be>, "osmocomBB" <baseband-devel(a)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_r… Try to write in the wireshark forum. 14.12.2012, 14:22, "g.roelant(a)telenet.be" <g.roelant(a)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

2 1

stupid question
by g.roelant＠telenet.be 14 Dec '12

14 Dec '12

Are the bursts captured with ccch_scan in burst_ind branch the same as the bursts captured with usrp2? do they result in the same file? i guess not... kind regards

2 1

imm ass packages
by g.roelant＠telenet.be 14 Dec '12

14 Dec '12

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

1 0

bursts dat files
by g.roelant＠telenet.be 11 Dec '12

11 Dec '12

Hi, I'm using the sylvain/burst_ind branch and ccch_scan. this produces bursts files. with which application can i view them? what is the format of these dat files? i cannot open them with wireshark... any hints? kind regards

4 5

another newbie question
by g.roelant＠telenet.be 10 Dec '12

10 Dec '12

I want to try to alter the mobile app (in gsm48_rr.c) to listen to all tmsi's. i changed the code and altered all if statements where in the else part was the log 'Not for us' i'm hoping the phone will start following the conversation with the immediate assignment packages... this way i can start logging the beginning of the encryption.... am i doing stupid things? or is there already an app that does this? thanks

4 4

AW: Re: AW: Re: beginners question
by Denis Simonet 09 Dec '12

09 Dec '12

For example. (reply-to doesn't seem to be set correctly in the list, btw?) Von Samsung Mobile gesendetg.roelant(a)telenet.be hat geschrieben:and than write the file with wireshark? i'm already using the mobile app with succes. Van: "Denis Simonet" <denis.simonet(a)bluewin.ch> Aan: "g roelant" <g.roelant(a)telenet.be> Verzonden: Zaterdag 8 december 2012 18:26:19 Onderwerp: AW: Re: beginners question You probably want to use the -i switch with a layer23 app and capture gsmtap with Wireshark. Best regards Denis Von Samsung Mobile gesendet g.roelant(a)telenet.be hat geschrieben: I want to write the raw data to a file. is that possible with a command? tune the gsm to a channel (for inst. 67) and capture all raw data into a file. ----- Oorspronkelijk e-mail ----- Van: "Alexander Huemer" <alexander.huemer(a)xx.vu> Aan: baseband-devel(a)lists.osmocom.org Verzonden: Vrijdag 7 december 2012 22:54:46 Onderwerp: Re: beginners question Hi g, On Fri, Dec 07, 2012 at 10:09:06PM +0100, g.roelant(a)telenet.be wrote: > How can i write the burst frames? Your question is very unspecific and therefore unlikely to be answered. You may want to rethink what exactly you want to know. Then, rephrase your question. Kind regards, -Alexander Huemer

2 1

beginners question
by g.roelant＠telenet.be 09 Dec '12

09 Dec '12

Hi, How can i write the burst frames? thanks

2 2

[PATCH] Add a5/3 support.
by ☎ 09 Dec '12

09 Dec '12

Hello. Attached patch will bring a5/3 support to osmo_a5. The implementatin is done based on spec, results are compared to reference implementation from standard and test vectors. Unfortunately there are several deficiencies: - it doesn't work with real phonein test network yet - no tests included - code is probably suboptimal here and there Anyway I would love to read your comments. It would be especially great if someone will manage to test it against real phones in actual network. -- best regards, Max, http://fairwaves.ru

5 11

Possible bug in "gsm48_decode_lai" code
by Bhaskar11 07 Dec '12

07 Dec '12

While running Cell-Log application, I found that the main branch of OsmocomBB gives wrong value of MCC/MNC in hex (but correct one in decimal), but the Sylvain testing branch gives correct value. In practice this means compiling Cell-Log in testing branch gives the name of the country, but the compiling it in main branch does not recognise the country. Other side-effects are unknown to me at present. Tracing through the source leads to the "gsm48_decode_lai" as the culprit. The code seems correct in the testing branch, but has not been updated in the main. Moreover, the code is shifted out from gsm48.c to sysinfo.c in the testing branch. Testing branch decodes MCC/MNC to hex: *mcc = ((lai->digits[0] & 0x0f) << 8) | (lai->digits[0] & 0xf0) | (lai->digits[1] & 0x0f); But main branch decodes MCC/MNC to decimal: *mcc = (lai->digits[0] & 0x0f) * 100 + (lai->digits[0] >> 4) * 10 + (lai->digits[1] & 0x0f); The comment in main branch states that "/* Attention: this function retunrs true integers, not hex! */". There is no such comment in the testing branch. So is this a problem because Cell_Log wrongly uses gsm48_decode_lai? Or does gsm48_decode_lai need to be updated in the main branch? B.

4 4

[PATCH 3/3] Add A5/3 support.
by Max Suraev 07 Dec '12

07 Dec '12

--- src/gsm/a5.c | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/src/gsm/a5.c b/src/gsm/a5.c index 93b22c7..5815aa7 100644 --- a/src/gsm/a5.c +++ b/src/gsm/a5.c @@ -39,6 +39,7 @@ #include <string.h> #include <osmocom/core/bits.h> #include <osmocom/gsm/a5.h> +#include <osmocom/gsm/kasumi.h> /*! \brief Main method to generate a A5/x cipher stream * \param[in] n Which A5/x method to use @@ -71,6 +72,10 @@ osmo_a5(int n, const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) osmo_a5_2(key, fn, dl, ul); break; + case 3: + osmo_a5_3(key, fn, dl, ul); + break; + default: /* a5/[4..7] not supported here/yet */ return -ENOTSUP; @@ -368,4 +373,42 @@ osmo_a5_2(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) } } +/* ------------------------------------------------------------------------ */ +/* A5/3 */ +/* ------------------------------------------------------------------------ */ + +/*! \brief Generate a GSM A5/3 cipher stream + * \param[in] key 8 byte array for the key (as received from the SIM) + * \param[in] fn Frame number + * \param[out] dl Pointer to array of ubits to return Downlink cipher stream + * \param[out] ul Pointer to array of ubits to return Uplink cipher stream + * + * Either (or both) of dl/ul should be NULL if not needed. + * + * Implementation based on specifications from 3GPP TS 55.216, 3GPP TR 55.919 and ETSI TS 135 202 + * with slight simplifications (CE hardcoded to 0). + */ +void +osmo_a5_3(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) +{ + /* internal function require 128 bit key so we expand by concatenating supplied 64 bit key */ + uint8_t i, ck[16], gamma[32], _key[8]; + memcpy(_key, key, 8); + osmo_revbytes_buf(_key, 8); /* reverse key byte order to match the way it's stored in SIM */ + memcpy(ck, _key, 8); + memcpy(ck + 8, _key, 8); + + uint32_t fn_count = osmo_a5_fn_count(fn); /* Frame count load */ + if (dl) { + kgcore(0xF, 0, fn_count, 0, ck, gamma, 114); + osmo_pbit2ubit(dl, gamma, 114); + } + if (ul) { + kgcore(0xF, 0, fn_count, 0, ck, gamma, 228); + uint8_t uplink[15]; + for(i = 0; i < 15; i++) uplink[i] = (gamma[i + 14] << 2) + (gamma[i + 15] >> 6); + osmo_pbit2ubit(ul, uplink, 114); + } +} + /*! @} */ -- 1.7.10.4 --------------000004050908040808070403--

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel