OpenBSC

openbsc@lists.osmocom.org

10 participants
4188 discussions

patch serie: download URL
by 246tnt＠gmail.com 28 Sep '09

28 Sep '09

Damn, gmail sucks for posting patches, sorry about that ... Here's an url to download them: http://www.246tnt.com/files/openbsc/20090924/ Sylvain

2 2

[patch 1/4] gsm_04_11: Free transaction on RX_RP_ACK for SMS
by Sylvain Munaut 28 Sep '09

28 Sep '09

commit 90e04861aa587d192025dd42aff5501e3742672a Author: Sylvain Munaut <tnt(a)246tNt.com> Date: Thu Sep 24 01:32:41 2009 +0200 [gsm_04_11] Free transaction on RX_RP_ACK for SMS When only one SMS is sent, the freeing of the lchan will automatically free all transactions on the lchan. However, if there are several SMS sent at once, the call to gsm411_send_sms_lchan will create a new transaction with the same caracteristics as the previous one. If the old one is not free'd, the next call to trans_find_by_id (triggered by the next incoming RP-ACK) will not return the good transaction and things go haywire. Signed-off-by: Sylvain Munaut <tnt(a)246tNt.com> openbsc/src/gsm_04_11.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)

2 2

junghanns.net singleE1 MiniPCI support
by Clemens Hopfer 28 Sep '09

28 Sep '09

Hi, has anyone tried running OpenBSC with the junghanns.net singleE1 MiniPCI card? It has got the CologneChip HFC-E1 controller and seems to be supported by mISDN. Target system would be an alix3d3. cu, Clemens

3 3

SMS delivery (Mobile Terminated): First ok, second fails
by 246tnt＠gmail.com 26 Sep '09

26 Sep '09

Hi, I've noticed a problem when delivering several SMS to a mobile back-to-back. The first one is ok, the second one is received by the MS but OpenBSC fails with "RX RP-ACK but no sms in transaction?!?" when receiving the "RX SMS RP-ACK (MO)" (full log below) From the symptoms and looking at the code, I would say that the transaction of the first SMS delivery was not freed, therefore, when we receive the RP-ACK of the second SMS, we do a trans_find_by_id in gsm0411_rcv_sms, and we actually find the transaction of the _first_ deliver (which has its .sms field cleared since it was released already). I think you wouldn't notice if you waited between SMS because SMC Timer TC1* would expire, calling trans_free(). The problem is that I don't really know _where_ trans_free should be called. There are commented out call to it at several places ... I would think the RP-ACK(MO) reception looks like a good place. But OTOH, this whole process can queue data, giving away a reference to lchan (without get) and trans_free does a put on lchan (so I guess that could invalidate the lchan ref that was queued ? didn't check that in details) Sylvain --- SNIP --- <0100> gsm_04_11.c:920 send_sms_lchan() <0002> transaction.c:69 subscr=0x1fe52d0, subscr->net=0x1f8fc30 <0002> gsm_subscriber_base.c:131 subscr 46332 usage increases usage to: 4 <0002> gsm_04_11.c:937 lchan (bts=0,trx=0,ts=0,ch=0) increases usage to: 1 <0100> gsm_04_11.c:972 TX: SMS DELIVER <0100> gsm_04_11.c:188 TX: CP-DATA trans=4 <0100> gsm_04_11.c:149 GSM4.11 TX 49 01 1e 01 2a 07 91 44 77 58 10 06 50 00 12 00 05 b9 72 65 f7 00 00 90 80 72 12 03 41 00 02 44 3a <0001> abis_rsl.c:1215 channel=(bts=0,trx=0,ts=0) chan_nr=0x20 sapi=3 DATA INDICATION <0100> gsm_04_11.c:817 trans_id=c RX SMS CP-ACK <0001> abis_rsl.c:1215 channel=(bts=0,trx=0,ts=0) chan_nr=0x20 sapi=3 DATA INDICATION <0100> gsm_04_11.c:817 trans_id=c RX SMS CP-DATA <0100> gsm_04_11.c:191 TX: CP-ACK trans=4 <0100> gsm_04_11.c:149 GSM4.11 TX 49 04 <0100> gsm_04_11.c:750 RX SMS RP-ACK (MO) <0002> gsm_subscriber_base.c:139 subscr 27567 usage decreased usage to: 0 <0002> gsm_subscriber_base.c:139 subscr 46332 usage decreased usage to: 3 DB: Found Subscriber: ID 2, IMSI 206205003327508, NAME '', TMSI 1666608304, EXTEN '27567', LAC 1, AUTH 1 DBI: -7: The requested variable type does not match what libdbi thinks it should be <0002> gsm_subscriber_base.c:131 subscr 46332 usage increases usage to: 4 <0100> gsm_04_11.c:920 send_sms_lchan() <0002> transaction.c:69 subscr=0x1fe52d0, subscr->net=0x1f8fc30 <0002> gsm_subscriber_base.c:131 subscr 46332 usage increases usage to: 5 <0002> gsm_04_11.c:937 lchan (bts=0,trx=0,ts=0,ch=0) increases usage to: 2 <0100> gsm_04_11.c:972 TX: SMS DELIVER <0100> gsm_04_11.c:188 TX: CP-DATA trans=4 <0100> gsm_04_11.c:149 GSM4.11 TX 49 01 1f 01 2a 07 91 44 77 58 10 06 50 00 13 00 05 b9 72 65 f7 00 00 90 80 72 12 03 41 00 03 47 39 19 <0001> abis_rsl.c:1215 channel=(bts=0,trx=0,ts=0) chan_nr=0x20 sapi=3 DATA INDICATION <0100> gsm_04_11.c:817 trans_id=c RX SMS CP-ACK <0001> abis_rsl.c:1215 channel=(bts=0,trx=0,ts=0) chan_nr=0x20 sapi=3 DATA INDICATION <0100> gsm_04_11.c:817 trans_id=c RX SMS CP-DATA <0100> gsm_04_11.c:191 TX: CP-ACK trans=4 <0100> gsm_04_11.c:149 GSM4.11 TX 49 04 <0100> gsm_04_11.c:750 RX SMS RP-ACK (MO) <0100> gsm_04_11.c:640 RX RP-ACK but no sms in transaction?!? <0100> gsm_04_11.c:561 TX: SMS RP ERROR, cause 111 (Protocol Error) <0100> gsm_04_11.c:188 TX: CP-DATA trans=4 <0100> gsm_04_11.c:149 GSM4.11 TX 49 01 04 05 2a 01 6f <0001> abis_rsl.c:1215 channel=(bts=0,trx=0,ts=0) chan_nr=0x20 sapi=3 DATA INDICATION <0100> gsm_04_11.c:817 trans_id=c RX SMS CP-ACK <0100> gsm_04_11.c:159 SMC Timer TC1* is expired, calling trans_free() <0002> transaction.c:101 lchan (bts=0,trx=0,ts=0,ch=0) decreases usage to: 1 <0002> gsm_subscriber_base.c:139 subscr 46332 usage decreased usage to: 4 --- /SNIP ---

3 3

Re: Quick & Dirty test of the ciphering functions
by Dieter Spaar 24 Sep '09

24 Sep '09

Hello Sylvain, On Thu, 24 Sep 2009 02:13:45 +0200, "Sylvain Munaut" <246tnt(a)gmail.com> wrote: > > This evening I spent a few hours hacking a small test to activate > ciphering and I tought people might be interested with tinkering with > it. If you want to try for yourself, start off from the encryption > branch of Harald, then apply the 4 patches I just posted to this list > then apply the quick hack attached to this message. Great that you provide the patches, I did a proof a concept implementation a while ago (http://lists.gnumonks.org/pipermail/openbsc/2009-July/000584.html). However I never found the time to actually complete it, so now I don't have to care any more :-) Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

List is quiet...
by Harald Welte 24 Sep '09

24 Sep '09

Hi! I'm surprised that this list is so quiet... no mails for more than a week already. Is anybody still playing with, developing or using OpenBSC? I would really appreciate more community participation, such as * more documentation in the wiki * talk about what you're doing with OpenBSC (esp. the universities!) * discussion / sharing of your experience * bug reports (should probably go in trac) * patches! Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

6 9

[patch 4/4] abis_rsl: Fix rsl_encryption_cmd L3 length computation
by Sylvain Munaut 24 Sep '09

24 Sep '09

commit c582a730570f96ea294d53f5261b6f4df35f256c Author: Sylvain Munaut <tnt(a)246tNt.com> Date: Thu Sep 24 01:54:40 2009 +0200 [abis_rsl] Fix rsl_encryption_cmd L3 length computation msg->l3h doesn't have any coherent value at that point, can't use that. Signed-off-by: Sylvain Munaut <tnt(a)246tNt.com> openbsc/src/abis_rsl.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

1 0

[patch 3/4] gsm_04_08: Fix gsm48_send_rr_ciph_mode algorithm ID
by Sylvain Munaut 24 Sep '09

24 Sep '09

commit 7aa86ed1e8669bcd06970ba23a1ff5abd5da81e6 Author: Sylvain Munaut <tnt(a)246tNt.com> Date: Thu Sep 24 01:44:24 2009 +0200 [gsm_04_08] Fix gsm48_send_rr_ciph_mode algorithm ID The algorithm ID used in the GSM 04.08 RR message is (x-1) for A5/x. In RSL it's (x+1) for A5/x so there is a difference of 2. Signed-off-by: Sylvain Munaut <tnt(a)246tNt.com> openbsc/src/gsm_04_08.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

1 0

[patch 2/4] gsm_04_08: Fix gsm48_tx_mm_auth_req implementation
by Sylvain Munaut 24 Sep '09

24 Sep '09

commit ed85ac5d09fa892996a06170422430274e050124 Author: Sylvain Munaut <tnt(a)246tNt.com> Date: Thu Sep 24 01:40:55 2009 +0200 [gsm_04_08] Fix gsm48_tx_mm_auth_req implementation It was mainly missing the key_seq field, causing the command to just be rejected by the ME. Signed-off-by: Sylvain Munaut <tnt(a)246tNt.com> openbsc/include/openbsc/gsm_04_08.h | 7 +++++++ openbsc/src/gsm_04_08.c | 8 +++++--- 2 files changed, 12 insertions(+), 3 deletions(-)

1 0

OpenBSC related job offer in Dresden / Germany
by Harald Welte 22 Sep '09

22 Sep '09

Hi all! I have recently been informed there is a job opening related to OpenBSC in Dresden / Germany. So if you're interested in working full time on issues such as * integrating OpenBSC into actual applications / products * testing OpenBSC with various handsets in various scenarios * sending bug reports and interacting with actual developers The job is not really about development of the OpenBSC stack itself, but related to system integration. So don't worry if you are neither a full-blown programmer, nor know the GSM protocol specs up to the last bit .. Please drop me a note, in case you're interested. Regards, -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC