- OpenBSC - lists.osmocom.org

Wiki Error?
by Stuart Baggs 16 Nov '10

16 Nov '10

Hi, I am reading the OpenBSC_GPRS wiki page and trying to get GPRS up and running. On the wiki it says: ! ! Osmocom SGSN configuration ! ! line vty no login ! sgsn gtp local-ip 192.168.1.128 ggsn 0 remote-ip 192.168.1.129 ggsn 0 gtp-version 1 ! ns timer tns-block 3 timer tns-block-retries 3 timer tns-reset 3 timer tns-reset-retries 3 timer tns-test 30 timer tns-alive 3 timer tns-alive-retries 10 encapsulation udp local-ip 192.168.0.128 encapsulation udp local-port 23000 encapsulation framerelay-gre enabled 0 ! bssgp ! Shouldn't encapsulation udp local-ip and gtp local-ip be the same if everything is on the same subnet? Also I have all 3 processes running openggsn, osmo-sgsn and bsc_hack but GPRS does not attach on any of my handsets. What could be the problem?

3 2

Introducing osmo-bsc to master
by Holger Hans Peter Freyther 16 Nov '10

16 Nov '10

Hi all, after months of work on the BSC API and on/off on the osmo-bsc it seems to be close to a working state. It has a lot of code from bsc_msc_ip of the on-waves/bsc-master branch but in a better structure thanks to the BSC API. Right now it is on the zecke/osmo-bsc branch and has about 58 commits to build the BSC. It can be found in the src/bsc directory and has the main files: osmo_bsc_main.c - The main method osmo_bsc_sccp.c - To handle the SCCP connections, connection release, connection timeouts, IT timer.. osmo_bsc_msc.c - To handle the connection(s) to the MSC, authentication, ping/pong to test the link and connection failure via a signal osmo_bsc_bssap.c - This is parsing the GSM0808 messages and maps that to the BSC API functions osmo_bsc_api.c - Callbacks for the BSC API, creating GSM0808 messages and sending them to the MSC osmo_bsc_sound.c - Handle the CRCX_ACK and send a MDCX... osmo_bsc_filter.c - To inspect incoming and outgoing packets and provide extra functionality. osmo_bsc_vty.c - VTY options for the MSC connection(s). This is a msc subgroup of the VTY. I will have to heavily test the new code for leaks, crashes, failure and such and will do this with call testing overnight, but I think it should not be less stable than bsc_msc_ip. There are two things that should be done next. Work on paging and decouple the BSC part of scheduling the messages, not scheduling too many to not crash the nanoBTS and the MSC part that triggers the callback. Be able to 'switch' from Osmo-BSC functionality and bsc_hack functionality on the fly. This could be very interesting for fuzzing that only after a certain message someone wants to start fuzzing with an external app. Use the MSC functionality from a new application and have a true MSC...

2 2

nanoBTS Calibration
by Stuart Baggs 16 Nov '10

16 Nov '10

Hi guys, how do we calibrate the internal ocilator of the nanoBTS? I have a 139 unit which has synced up fine and has a olid green light but the network no longer appears on the handsets selection menu (the handset is dual band and the BTS is on an AFRCN within the handsets range). It was working before but the unit has been powered down for several months and I remember someone from ip.access advising that the internal oscillator needs to be re-calibrated to fix this issue.

2 1

Relation between IMSI and TMSI
by zero cool 15 Nov '10

15 Nov '10

Dear community members, as we all know that TMSI is alotted by bsc, can anybody explain how this happens and what kind of algorithm they (professional network) use. Can I extract IMSI from TMSI?? Please answer !!!! On Mon, Nov 15, 2010 at 2:05 AM, <openbsc-request(a)lists.gnumonks.org> wrote: > Send OpenBSC mailing list submissions to > openbsc(a)lists.gnumonks.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gnumonks.org/mailman/listinfo/openbsc > or, via email, send a message with subject or body 'help' to > openbsc-request(a)lists.gnumonks.org > > You can reach the person managing the list at > openbsc-owner(a)lists.gnumonks.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenBSC digest..." > > > Today's Topics: > > 1. libosmocore compile error (Stuart Baggs) > 2. Re: libosmocore compile error (Sylvain Munaut) > 3. Re: libosmocore compile error (Stuart Baggs) > 4. Re: libosmocore compile error (Holger Hans Peter Freyther) > 5. Re: libosmocore compile error (Stuart Baggs) > 6. Re: libosmocore compile error (Holger Hans Peter Freyther) > 7. Re: libosmocore compile error (Holger Hans Peter Freyther) > 8. bsc_hack dies (Stuart Baggs) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 14 Nov 2010 17:48:09 +0000 > From: Stuart Baggs <stuart(a)bluewave.im> > Subject: libosmocore compile error > To: OpenBSC list <openbsc(a)lists.gnumonks.org> > Message-ID: <507B2AE3-06E7-4486-9AE0-F0965C15FF10(a)bluewave.im> > Content-Type: text/plain; charset=us-ascii > > Hi, I am trying to get a working GPRS branch up and running. I have done a > fresh git clone of both libosmocore and openbsc master branches. Both > compile without issue. When I try and run bsc_hack from /opt/openbsc/ I get > this error: > > ./bsc_hack: error while loading shared libraries: libosmovty.so.0: cannot > open shared object file: No such file or directory > > Any ideas what has gone wrong with this install? Obviously openbsc cannot > find libosmocore libraries, but I have compiled them cas per usual. Any > ideas? > > Thanks > > > ------------------------------ > > Message: 2 > Date: Sun, 14 Nov 2010 19:00:50 +0100 > From: Sylvain Munaut <246tnt(a)gmail.com> > Subject: Re: libosmocore compile error > To: Stuart Baggs <stuart(a)bluewave.im> > Cc: OpenBSC list <openbsc(a)lists.gnumonks.org> > Message-ID: > <AANLkTi=_yru5SiOApB6dQ7XAk_FgMzUymTW-CN+XLU=x(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi, > > > > ./bsc_hack: error while loading shared libraries: libosmovty.so.0: cannot > open shared object file: No such file or directory > > > > Any ideas what has gone wrong with this install? Obviously openbsc cannot > find libosmocore libraries, but I have compiled them cas per usual. Any > ideas? > > Well yeah ... > > When you install libraried in non-standard location you must tell the > ld loader where to look > > Either using LD_LIBRARY_PATH en variable or /etc/ld.so.conf > > Cheers, > > Sylvain > > > > ------------------------------ > > Message: 3 > Date: Sun, 14 Nov 2010 18:49:12 +0000 > From: Stuart Baggs <stuart(a)bluewave.im> > Subject: Re: libosmocore compile error > To: Sylvain Munaut <246tnt(a)gmail.com> > Cc: OpenBSC list <openbsc(a)lists.gnumonks.org> > Message-ID: <2A79A19C-6D6F-4E19-B9ED-9894421F8F10(a)bluewave.im> > Content-Type: text/plain; charset=us-ascii > > Thanks, I though it was in the standard location. I have another issue now. > I have installed libosmocore 0.1.27 and the latest clone of openbsc master > branch but when compiling open_bsc I am getting: > > No package 'libosmo-sccp' found > > I though this was part of libosmocore? I have managed to get a git clone of > libosmo-sccp but a ./configure comes up with: > > configure: error: cannot find install-sh, install.sh, or shtool in "." > "./.." "./../.." > > I'm keen to get the GPRS branch up and running so I can start testing. > > On 14 Nov 2010, at 18:00, Sylvain Munaut wrote: > > > Hi, > > > > > >> ./bsc_hack: error while loading shared libraries: libosmovty.so.0: > cannot open shared object file: No such file or directory > >> > >> Any ideas what has gone wrong with this install? Obviously openbsc > cannot find libosmocore libraries, but I have compiled them cas per usual. > Any ideas? > > > > Well yeah ... > > > > When you install libraried in non-standard location you must tell the > > ld loader where to look > > > > Either using LD_LIBRARY_PATH en variable or /etc/ld.so.conf > > > > Cheers, > > > > Sylvain > > > > > ------------------------------ > > Message: 4 > Date: Sun, 14 Nov 2010 19:51:37 +0100 > From: Holger Hans Peter Freyther <holger(a)freyther.de> > Subject: Re: libosmocore compile error > To: openbsc(a)lists.gnumonks.org > Message-ID: <4CE02FB9.2060909(a)freyther.de> > Content-Type: text/plain; charset=ISO-8859-1 > > On 11/14/2010 07:49 PM, Stuart Baggs wrote: > > > configure: error: cannot find install-sh, install.sh, or shtool in "." > "./.." "./../.." > > autoreconf --install --force.. > > > > > > > I'm keen to get the GPRS branch up and running so I can start testing. > > You don't need to pass the enable option for the BSC... normal OpenBSC does > not require SCCP. > > > > ------------------------------ > > Message: 5 > Date: Sun, 14 Nov 2010 18:59:29 +0000 > From: Stuart Baggs <stuart(a)bluewave.im> > Subject: Re: libosmocore compile error > To: Holger Hans Peter Freyther <holger(a)freyther.de> > Cc: openbsc(a)lists.gnumonks.org > Message-ID: <5ABF6A6C-7A7B-40C9-B079-2CB06D0C9520(a)bluewave.im> > Content-Type: text/plain; charset=us-ascii > > Thanks for your help. This is getting really frustrating now. I have tried > to recompile openbsc with: > > autoreconf --install --force > ./configure > > but the process stops on ./configure with: > > checking for LIBOSMOSCCP... configure: error: Package requirements > (libosmo-sccp >= 0.0.3) were not met: > > No package 'libosmo-sccp' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables LIBOSMOSCCP_CFLAGS > and LIBOSMOSCCP_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > > I'm probably being really stupid, but it's been a long day. Any pointers? > > Thanks guys. > > s > > On 14 Nov 2010, at 18:51, Holger Hans Peter Freyther wrote: > > > On 11/14/2010 07:49 PM, Stuart Baggs wrote: > > > >> configure: error: cannot find install-sh, install.sh, or shtool in "." > "./.." "./../.." > > > > autoreconf --install --force.. > > > > > > > >> > >> I'm keen to get the GPRS branch up and running so I can start testing. > > > > You don't need to pass the enable option for the BSC... normal OpenBSC > does > > not require SCCP. > > > > > > > ------------------------------ > > Message: 6 > Date: Sun, 14 Nov 2010 20:04:10 +0100 > From: Holger Hans Peter Freyther <holger(a)freyther.de> > Subject: Re: libosmocore compile error > To: openbsc(a)lists.gnumonks.org > Message-ID: <4CE032AA.2060601(a)freyther.de> > Content-Type: text/plain; charset=ISO-8859-1 > > On 11/14/2010 07:59 PM, Stuart Baggs wrote: > > Thanks for your help. This is getting really frustrating now. I have > tried to recompile openbsc with: > > > > autoreconf --install --force > > ./configure > > > > but the process stops on ./configure with: > > > > checking for LIBOSMOSCCP... configure: error: Package requirements > (libosmo-sccp >= 0.0.3) were not met: > > > > No package 'libosmo-sccp' found > > > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > > installed software in a non-standard prefix. > > > > Alternatively, you may set the environment variables LIBOSMOSCCP_CFLAGS > > and LIBOSMOSCCP_LIBS to avoid the need to call pkg-config. > > See the pkg-config man page for more details. > > > > I'm probably being really stupid, but it's been a long day. Any pointers? > > .... > > > 1.) the autoreconf --install --force was below your quote of attempting to > build libosmo-sccp. So it was related to libosmo-sccp. :) > > 2.) You have not invoked './configure', you have either invoked > './configure > --enable-nat' or './configure --enable-osmo-bsc' (or both). For a normal > build > libosmosccp is not required. > > To illustrate I have put the relevant part from configure.in here. So only > if > you have used any of the two options you will need libosmo-sccp. If you > don't > have libosmosccp... then don't specify the two options. > > I hope this helps > > > > > AC_ARG_ENABLE([nat], [AS_HELP_STRING([--enable-nat], [Build the BSC NAT. > Requires SCCP])], > [ > PKG_CHECK_MODULES(LIBOSMOSCCP, libosmo-sccp >= 0.0.2) > osmo_ac_build_nat="yes" > ], > [ > osmo_ac_build_nat="no" > ]) > AM_CONDITIONAL(BUILD_NAT, test "x$osmo_ac_build_nat" = "xyes") > > AC_ARG_ENABLE([osmo-bsc], [AS_HELP_STRING([--enable-osmo-bsc], [Build the > Osmo > BSC])], > [ > PKG_CHECK_MODULES(LIBOSMOSCCP, libosmo-sccp >= 0.0.2) > osmo_ac_build_bsc="yes" > ], > [ > osmo_ac_build_bsc="no" > ]) > > > > > ------------------------------ > > Message: 7 > Date: Sun, 14 Nov 2010 21:24:09 +0100 > From: Holger Hans Peter Freyther <holger(a)freyther.de> > Subject: Re: libosmocore compile error > To: openbsc(a)lists.gnumonks.org > Message-ID: <4CE04569.8070701(a)freyther.de> > Content-Type: text/plain; charset=ISO-8859-1 > > On 11/14/2010 09:13 PM, Stuart Baggs wrote: > > All compiled and installed. I'm running OpenBSC 0.3.99.20onwaves. Is this > compatible with GPRS? I have compiled OpenGGSN and recompiled openbsc but I > dont seem to be getting an osmo-sgsn binary created. > > osmo-sgsn is only in master. You will need to get osmo-sgsn from the master > branch, bsc_msc_ip is only in the branch and will stay there. > > > > ------------------------------ > > Message: 8 > Date: Sun, 14 Nov 2010 20:35:33 +0000 > From: Stuart Baggs <stuart(a)bluewave.im> > Subject: bsc_hack dies > To: OpenBSC list <openbsc(a)lists.gnumonks.org> > Message-ID: <CF05E7EF-E369-4694-905E-D1DF7D0E203C(a)bluewave.im> > Content-Type: text/plain; charset=us-ascii > > After 30 seconds my bsc_hack is dieing. Here is the error: > > root@gateway:~/openbsc/openbsc# /usr/local/sbin/bsc_hack -c > /home/stuart/openbsc.cfg -P > DB: Database initialized. > DB: Database prepared. > <000d> input/ipaccess.c:634 accept()ed new OML link from 192.168.1.51 > <0005> bsc_init.c:745 bootstrapping OML for BTS 0 > SET ATTR NACK CAUSE=Message cannot be performed > <000d> input/ipaccess.c:696 accept()ed new RSL link from 192.168.1.51 > <0004> bsc_init.c:941 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 870 > using MCC=234 MNC=18 LAC=1 CID=0 BSIC=63 TSC=7 > <0000> chan_alloc.c:441 (bts=0,trx=0,ts=0,ss=0) Recycling Channel. > <0004> abis_rsl.c:588 (bts=0,trx=0,ts=0,ss=1) is back in operation. > *** stack smashing detected ***: /usr/local/sbin/bsc_hack terminated > ======= Backtrace: ========= > /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0x2eaed8] > /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0x2eae90] > /usr/local/sbin/bsc_hack[0x8060f43] > /usr/local/sbin/bsc_hack[0x805cca0] > /usr/local/sbin/bsc_hack[0x80663d9] > /usr/local/sbin/bsc_hack[0x80752a2] > /usr/local/lib/libosmocore.so.0(bsc_select_main+0x14b)[0x88e51b] > /usr/local/sbin/bsc_hack[0x804c0a6] > /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x220b56] > /usr/local/sbin/bsc_hack[0x804bbb1] > ======= Memory map: ======== > 00110000-00111000 r-xp 00000000 00:00 0 [vdso] > 0020a000-00348000 r-xp 00000000 fc:00 171 /lib/tls/i686/cmov/ > libc-2.10.1.so > 00348000-00349000 ---p 0013e000 fc:00 171 /lib/tls/i686/cmov/ > libc-2.10.1.so > 00349000-0034b000 r--p 0013e000 fc:00 171 /lib/tls/i686/cmov/ > libc-2.10.1.so > 0034b000-0034c000 rw-p 00140000 fc:00 171 /lib/tls/i686/cmov/ > libc-2.10.1.so > 0034c000-0034f000 rw-p 00000000 00:00 0 > 003c0000-003dc000 r-xp 00000000 fc:00 300 /lib/libgcc_s.so.1 > 003dc000-003dd000 r--p 0001b000 fc:00 300 /lib/libgcc_s.so.1 > 003dd000-003de000 rw-p 0001c000 fc:00 300 /lib/libgcc_s.so.1 > 00443000-0045e000 r-xp 00000000 fc:00 143 /lib/ld-2.10.1.so > 0045e000-0045f000 r--p 0001a000 fc:00 143 /lib/ld-2.10.1.so > 0045f000-00460000 rw-p 0001b000 fc:00 143 /lib/ld-2.10.1.so > 004ba000-004c5000 r-xp 00000000 fc:00 151866 /usr/lib/libdbi.so.0.0.5 > 004c5000-004c6000 rw-p 0000a000 fc:00 151866 /usr/lib/libdbi.so.0.0.5 > 00569000-0056b000 r-xp 00000000 fc:00 177 /lib/tls/i686/cmov/ > libdl-2.10.1.so > 0056b000-0056c000 r--p 00001000 fc:00 177 /lib/tls/i686/cmov/ > libdl-2.10.1.so > 0056c000-0056d000 rw-p 00002000 fc:00 177 /lib/tls/i686/cmov/ > libdl-2.10.1.so > 005cf000-005f3000 r-xp 00000000 fc:00 179 /lib/tls/i686/cmov/ > libm-2.10.1.so > 005f3000-005f4000 r--p 00023000 fc:00 179 /lib/tls/i686/cmov/ > libm-2.10.1.so > 005f4000-005f5000 rw-p 00024000 fc:00 179 /lib/tls/i686/cmov/ > libm-2.10.1.so > 006c8000-006dd000 r-xp 00000000 fc:00 235 /lib/tls/i686/cmov/ > libpthread-2.10.1.so > 006dd000-006de000 r--p 00014000 fc:00 235 /lib/tls/i686/cmov/ > libpthread-2.10.1.so > 006de000-006df000 rw-p 00015000 fc:00 235 /lib/tls/i686/cmov/ > libpthread-2.10.1.so > 006df000-006e1000 rw-p 00000000 00:00 0 > 00764000-007ea000 r-xp 00000000 fc:00 135483 > /usr/lib/libsqlite3.so.0.8.6 > 007ea000-007eb000 r--p 00086000 fc:00 135483 > /usr/lib/libsqlite3.so.0.8.6 > 007eb000-007ec000 rw-p 00087000 fc:00 135483 > /usr/lib/libsqlite3.so.0.8.6 > 00889000-008a2000 r-xp 00000000 fc:00 1806 > /usr/local/lib/libosmocore.so.0.0.0 > 008a2000-008a3000 r--p 00018000 fc:00 1806 > /usr/local/lib/libosmocore.so.0.0.0 > 008a3000-008a4000 rw-p 00019000 fc:00 1806 > /usr/local/lib/libosmocore.so.0.0.0 > 008a4000-008a5000 rw-p 00000000 00:00 0 > 00abe000-00ac7000 r-xp 00000000 fc:00 175 /lib/tls/i686/cmov/ > libcrypt-2.10.1.so > 00ac7000-00ac8000 r--p 00008000 fc:00 175 /lib/tls/i686/cmov/ > libcrypt-2.10.1.so > 00ac8000-00ac9000 rw-p 00009000 fc:00 175 /lib/tls/i686/cmov/ > libcrypt-2.10.1.so > 00ac9000-00af0000 rw-p 00000000 00:00 0 > 00bca000-00bcf000 r-xp 00000000 fc:00 151877 > /usr/lib/dbd/libdbdsqlite3.so > 00bcf000-00bd0000 r--p 00004000 fc:00 151877 > /usr/lib/dbd/libdbdsqlite3.so > 00bd0000-00bd1000 rw-p 00005000 fc:00 151877 > /usr/lib/dbd/libdbdsqlite3.so > 08048000-08091000 r-xp 00000000 fc:00 154760 /usr/local/sbin/bsc_hack > 08091000-08092000 r--p 00048000 fc:00 154760 /usr/local/sbin/bsc_hack > 08092000-08097000 rw-p 00049000 fc:00 154760 /usr/local/sbin/bsc_hack > 08097000-0809b000 rw-p 00000000 00:00 0 > 0919b000-09228000 rw-p 00000000 00:00 0 [heap] > b6ffe000-b6fff000 ---p 00000000 00:00 0 > b6fff000-b7802000 rw-p 00000000 00:00 0 > b7806000-b7808000 rw-p 00000000 00:00 0 > bfa5e000-bfa73000 rw-p 00000000 00:00 0 [stack] > signal 6 received > talloc report on 'vty' (total 37965 bytes in 3350 blocks) > save_cwd contains 29 bytes in 1 blocks (ref > 0) 0x91bb478 > vty_command contains 21352 bytes in 1719 blocks (ref > 0) 0x91bb440 > vty_vector contains 16584 bytes in 1629 blocks (ref > 0) 0x91bb408 > full talloc report on 'openbsc' (total 137666 bytes in 63 blocks) > struct e1inp_line contains 45208 bytes in 1 blocks (ref > 0) 0x9207170 > struct ia_e1_handle contains 60 bytes in 1 blocks (ref > 0) 0x91f1500 > telnet_connection contains 1 bytes in 1 blocks (ref > 0) 0x91a18a0 > struct gsm_network contains 89224 bytes in 6 blocks (ref > 0) 0x91a16e0 > struct gsm_bts contains 88804 bytes in 2 blocks > (ref 0) 0x91f1620 > struct gsm_bts_trx contains 86188 bytes in 1 > blocks (ref 0) 0x91f2090 > BlueWave contains 9 bytes in 1 blocks > (ref 0) 0x919f018 > BlueWave contains 9 bytes in 1 blocks > (ref 0) 0x91a3490 > 127.0.0.1 contains 10 bytes in 1 blocks > (ref 0) 0x91a2038 > counter contains 580 bytes in 30 blocks (ref > 0) 0x919b568 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a3448 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a3400 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a33b8 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a3370 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a3328 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a32e0 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a3298 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a3250 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a3208 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a31c0 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a3178 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919d958 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919d910 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919d8c8 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919d880 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919d838 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919ea18 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919e9d0 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919e988 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919e940 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919e8f8 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919efd0 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919ef88 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919ef40 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919eef8 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919f0d0 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x919f088 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a2078 > struct counter contains 20 bytes in 1 blocks > (ref 0) 0x91a25b0 > trau_upq_entry contains 0 bytes in 1 blocks (ref > 0) 0x919b530 > trau_map_entry contains 0 bytes in 1 blocks (ref > 0) 0x919b4f8 > transaction contains 0 bytes in 1 blocks (ref > 0) 0x919b4c0 > subch_txq_entry contains 0 bytes in 1 blocks (ref > 0) 0x919b488 > signal_handler contains 140 bytes in 8 blocks (ref > 0) 0x919b450 > struct signal_handler contains 20 bytes in 1 blocks > (ref 0) 0x91f13e8 > struct signal_handler contains 20 bytes in 1 blocks > (ref 0) 0x91eb2b8 > struct signal_handler contains 20 bytes in 1 blocks > (ref 0) 0x919b6c0 > struct signal_handler contains 20 bytes in 1 blocks > (ref 0) 0x919b678 > struct signal_handler contains 20 bytes in 1 blocks > (ref 0) 0x919b630 > struct signal_handler contains 20 bytes in 1 blocks > (ref 0) 0x919b5e8 > struct signal_handler contains 20 bytes in 1 blocks > (ref 0) 0x919b5a0 > paging_request contains 0 bytes in 1 blocks (ref > 0) 0x919b418 > gsm_call contains 0 bytes in 1 blocks (ref > 0) 0x919b3e0 > subscr_request contains 0 bytes in 1 blocks (ref > 0) 0x919b3a8 > subscriber contains 392 bytes in 2 blocks (ref > 0) 0x919b370 > struct gsm_subscriber contains 392 bytes in 1 blocks > (ref 0) 0x9212ce0 > sms contains 0 bytes in 1 blocks (ref > 0) 0x919b338 > loc_updating_oper contains 0 bytes in 1 blocks (ref > 0) 0x919b300 > bs11_file_list_entry contains 0 bytes in 1 blocks (ref > 0) 0x919b2c8 > msgb contains 2060 bytes in 3 blocks (ref > 0) 0x919b290 > GSM 04.08 contains 1092 bytes in 1 blocks > (ref 0) 0x9213360 > Abis/IP contains 968 bytes in 1 blocks > (ref 0) 0x91f0f20 > Aborted > > > Any ideas? > > > ------------------------------ > > _______________________________________________ > OpenBSC mailing list > OpenBSC(a)lists.gnumonks.org > https://lists.gnumonks.org/mailman/listinfo/openbsc > > > End of OpenBSC Digest, Vol 23, Issue 7 > ************************************** > -- Thanks.....

3 2

bsc_hack dies
by Stuart Baggs 14 Nov '10

14 Nov '10

After 30 seconds my bsc_hack is dieing. Here is the error: root@gateway:~/openbsc/openbsc# /usr/local/sbin/bsc_hack -c /home/stuart/openbsc.cfg -P DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:634 accept()ed new OML link from 192.168.1.51 <0005> bsc_init.c:745 bootstrapping OML for BTS 0 SET ATTR NACK CAUSE=Message cannot be performed <000d> input/ipaccess.c:696 accept()ed new RSL link from 192.168.1.51 <0004> bsc_init.c:941 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 870 using MCC=234 MNC=18 LAC=1 CID=0 BSIC=63 TSC=7 <0000> chan_alloc.c:441 (bts=0,trx=0,ts=0,ss=0) Recycling Channel. <0004> abis_rsl.c:588 (bts=0,trx=0,ts=0,ss=1) is back in operation. *** stack smashing detected ***: /usr/local/sbin/bsc_hack terminated ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0x2eaed8] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0x2eae90] /usr/local/sbin/bsc_hack[0x8060f43] /usr/local/sbin/bsc_hack[0x805cca0] /usr/local/sbin/bsc_hack[0x80663d9] /usr/local/sbin/bsc_hack[0x80752a2] /usr/local/lib/libosmocore.so.0(bsc_select_main+0x14b)[0x88e51b] /usr/local/sbin/bsc_hack[0x804c0a6] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x220b56] /usr/local/sbin/bsc_hack[0x804bbb1] ======= Memory map: ======== 00110000-00111000 r-xp 00000000 00:00 0 [vdso] 0020a000-00348000 r-xp 00000000 fc:00 171 /lib/tls/i686/cmov/libc-2.10.1.so 00348000-00349000 ---p 0013e000 fc:00 171 /lib/tls/i686/cmov/libc-2.10.1.so 00349000-0034b000 r--p 0013e000 fc:00 171 /lib/tls/i686/cmov/libc-2.10.1.so 0034b000-0034c000 rw-p 00140000 fc:00 171 /lib/tls/i686/cmov/libc-2.10.1.so 0034c000-0034f000 rw-p 00000000 00:00 0 003c0000-003dc000 r-xp 00000000 fc:00 300 /lib/libgcc_s.so.1 003dc000-003dd000 r--p 0001b000 fc:00 300 /lib/libgcc_s.so.1 003dd000-003de000 rw-p 0001c000 fc:00 300 /lib/libgcc_s.so.1 00443000-0045e000 r-xp 00000000 fc:00 143 /lib/ld-2.10.1.so 0045e000-0045f000 r--p 0001a000 fc:00 143 /lib/ld-2.10.1.so 0045f000-00460000 rw-p 0001b000 fc:00 143 /lib/ld-2.10.1.so 004ba000-004c5000 r-xp 00000000 fc:00 151866 /usr/lib/libdbi.so.0.0.5 004c5000-004c6000 rw-p 0000a000 fc:00 151866 /usr/lib/libdbi.so.0.0.5 00569000-0056b000 r-xp 00000000 fc:00 177 /lib/tls/i686/cmov/libdl-2.10.1.so 0056b000-0056c000 r--p 00001000 fc:00 177 /lib/tls/i686/cmov/libdl-2.10.1.so 0056c000-0056d000 rw-p 00002000 fc:00 177 /lib/tls/i686/cmov/libdl-2.10.1.so 005cf000-005f3000 r-xp 00000000 fc:00 179 /lib/tls/i686/cmov/libm-2.10.1.so 005f3000-005f4000 r--p 00023000 fc:00 179 /lib/tls/i686/cmov/libm-2.10.1.so 005f4000-005f5000 rw-p 00024000 fc:00 179 /lib/tls/i686/cmov/libm-2.10.1.so 006c8000-006dd000 r-xp 00000000 fc:00 235 /lib/tls/i686/cmov/libpthread-2.10.1.so 006dd000-006de000 r--p 00014000 fc:00 235 /lib/tls/i686/cmov/libpthread-2.10.1.so 006de000-006df000 rw-p 00015000 fc:00 235 /lib/tls/i686/cmov/libpthread-2.10.1.so 006df000-006e1000 rw-p 00000000 00:00 0 00764000-007ea000 r-xp 00000000 fc:00 135483 /usr/lib/libsqlite3.so.0.8.6 007ea000-007eb000 r--p 00086000 fc:00 135483 /usr/lib/libsqlite3.so.0.8.6 007eb000-007ec000 rw-p 00087000 fc:00 135483 /usr/lib/libsqlite3.so.0.8.6 00889000-008a2000 r-xp 00000000 fc:00 1806 /usr/local/lib/libosmocore.so.0.0.0 008a2000-008a3000 r--p 00018000 fc:00 1806 /usr/local/lib/libosmocore.so.0.0.0 008a3000-008a4000 rw-p 00019000 fc:00 1806 /usr/local/lib/libosmocore.so.0.0.0 008a4000-008a5000 rw-p 00000000 00:00 0 00abe000-00ac7000 r-xp 00000000 fc:00 175 /lib/tls/i686/cmov/libcrypt-2.10.1.so 00ac7000-00ac8000 r--p 00008000 fc:00 175 /lib/tls/i686/cmov/libcrypt-2.10.1.so 00ac8000-00ac9000 rw-p 00009000 fc:00 175 /lib/tls/i686/cmov/libcrypt-2.10.1.so 00ac9000-00af0000 rw-p 00000000 00:00 0 00bca000-00bcf000 r-xp 00000000 fc:00 151877 /usr/lib/dbd/libdbdsqlite3.so 00bcf000-00bd0000 r--p 00004000 fc:00 151877 /usr/lib/dbd/libdbdsqlite3.so 00bd0000-00bd1000 rw-p 00005000 fc:00 151877 /usr/lib/dbd/libdbdsqlite3.so 08048000-08091000 r-xp 00000000 fc:00 154760 /usr/local/sbin/bsc_hack 08091000-08092000 r--p 00048000 fc:00 154760 /usr/local/sbin/bsc_hack 08092000-08097000 rw-p 00049000 fc:00 154760 /usr/local/sbin/bsc_hack 08097000-0809b000 rw-p 00000000 00:00 0 0919b000-09228000 rw-p 00000000 00:00 0 [heap] b6ffe000-b6fff000 ---p 00000000 00:00 0 b6fff000-b7802000 rw-p 00000000 00:00 0 b7806000-b7808000 rw-p 00000000 00:00 0 bfa5e000-bfa73000 rw-p 00000000 00:00 0 [stack] signal 6 received talloc report on 'vty' (total 37965 bytes in 3350 blocks) save_cwd contains 29 bytes in 1 blocks (ref 0) 0x91bb478 vty_command contains 21352 bytes in 1719 blocks (ref 0) 0x91bb440 vty_vector contains 16584 bytes in 1629 blocks (ref 0) 0x91bb408 full talloc report on 'openbsc' (total 137666 bytes in 63 blocks) struct e1inp_line contains 45208 bytes in 1 blocks (ref 0) 0x9207170 struct ia_e1_handle contains 60 bytes in 1 blocks (ref 0) 0x91f1500 telnet_connection contains 1 bytes in 1 blocks (ref 0) 0x91a18a0 struct gsm_network contains 89224 bytes in 6 blocks (ref 0) 0x91a16e0 struct gsm_bts contains 88804 bytes in 2 blocks (ref 0) 0x91f1620 struct gsm_bts_trx contains 86188 bytes in 1 blocks (ref 0) 0x91f2090 BlueWave contains 9 bytes in 1 blocks (ref 0) 0x919f018 BlueWave contains 9 bytes in 1 blocks (ref 0) 0x91a3490 127.0.0.1 contains 10 bytes in 1 blocks (ref 0) 0x91a2038 counter contains 580 bytes in 30 blocks (ref 0) 0x919b568 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a3448 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a3400 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a33b8 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a3370 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a3328 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a32e0 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a3298 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a3250 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a3208 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a31c0 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a3178 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919d958 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919d910 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919d8c8 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919d880 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919d838 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919ea18 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919e9d0 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919e988 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919e940 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919e8f8 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919efd0 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919ef88 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919ef40 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919eef8 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919f0d0 struct counter contains 20 bytes in 1 blocks (ref 0) 0x919f088 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a2078 struct counter contains 20 bytes in 1 blocks (ref 0) 0x91a25b0 trau_upq_entry contains 0 bytes in 1 blocks (ref 0) 0x919b530 trau_map_entry contains 0 bytes in 1 blocks (ref 0) 0x919b4f8 transaction contains 0 bytes in 1 blocks (ref 0) 0x919b4c0 subch_txq_entry contains 0 bytes in 1 blocks (ref 0) 0x919b488 signal_handler contains 140 bytes in 8 blocks (ref 0) 0x919b450 struct signal_handler contains 20 bytes in 1 blocks (ref 0) 0x91f13e8 struct signal_handler contains 20 bytes in 1 blocks (ref 0) 0x91eb2b8 struct signal_handler contains 20 bytes in 1 blocks (ref 0) 0x919b6c0 struct signal_handler contains 20 bytes in 1 blocks (ref 0) 0x919b678 struct signal_handler contains 20 bytes in 1 blocks (ref 0) 0x919b630 struct signal_handler contains 20 bytes in 1 blocks (ref 0) 0x919b5e8 struct signal_handler contains 20 bytes in 1 blocks (ref 0) 0x919b5a0 paging_request contains 0 bytes in 1 blocks (ref 0) 0x919b418 gsm_call contains 0 bytes in 1 blocks (ref 0) 0x919b3e0 subscr_request contains 0 bytes in 1 blocks (ref 0) 0x919b3a8 subscriber contains 392 bytes in 2 blocks (ref 0) 0x919b370 struct gsm_subscriber contains 392 bytes in 1 blocks (ref 0) 0x9212ce0 sms contains 0 bytes in 1 blocks (ref 0) 0x919b338 loc_updating_oper contains 0 bytes in 1 blocks (ref 0) 0x919b300 bs11_file_list_entry contains 0 bytes in 1 blocks (ref 0) 0x919b2c8 msgb contains 2060 bytes in 3 blocks (ref 0) 0x919b290 GSM 04.08 contains 1092 bytes in 1 blocks (ref 0) 0x9213360 Abis/IP contains 968 bytes in 1 blocks (ref 0) 0x91f0f20 Aborted Any ideas?

2 1

Re: libosmocore compile error
by Holger Hans Peter Freyther 14 Nov '10

14 Nov '10

On 11/14/2010 09:13 PM, Stuart Baggs wrote: > All compiled and installed. I'm running OpenBSC 0.3.99.20onwaves. Is this compatible with GPRS? I have compiled OpenGGSN and recompiled openbsc but I dont seem to be getting an osmo-sgsn binary created. osmo-sgsn is only in master. You will need to get osmo-sgsn from the master branch, bsc_msc_ip is only in the branch and will stay there.

2 1

libosmocore compile error
by Stuart Baggs 14 Nov '10

14 Nov '10

Hi, I am trying to get a working GPRS branch up and running. I have done a fresh git clone of both libosmocore and openbsc master branches. Both compile without issue. When I try and run bsc_hack from /opt/openbsc/ I get this error: ./bsc_hack: error while loading shared libraries: libosmovty.so.0: cannot open shared object file: No such file or directory Any ideas what has gone wrong with this install? Obviously openbsc cannot find libosmocore libraries, but I have compiled them cas per usual. Any ideas? Thanks

3 5

A5/4 spec
by Harald Welte 10 Nov '10

10 Nov '10

Hi all, recently I've been mentioning A5/4 in a couple of meetings. I've found the (already approved) change requests that introduce A5/4 by coincidence today: http://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_45/docs/SP-090635.zip http://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_46/docs/SP-090821.zip So basically A5/4 (and GEA4) use a 128bit Kc, and this mandates the use of an USIM in USIM application mode. Old GSM SIM cards are not sufficient. So A5/4 will be the first algorithm that uses a different Kc and will thus not suffer from semi-active downgrading attacks (like you can do with old phones and A5/2 to break A5/1 or A5/3, or you can do today with A5/3 if you later use the same RAND on an A5/1 encrypted session). 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)

1 0

Where do I get the compatible BTS
by Milind Bhirud 06 Nov '10

06 Nov '10

Hello, I'm exicted to see the OpenBSC contribution and wanted to try out and test the OpenBSC. I tried hard to get the nano-bts so that I can deploy OpenBSC but could not find any place / dealer / online auction to get one (new / used). I will appreciate if someone can help me pointing to the right people / firms from where I can buy the nano BTS. Thanks, Milind

1 0

Help with sccp library
by mosbah abdelkader 06 Nov '10

06 Nov '10

Dear openbsc developers, I have some questions regarding the sccp library code: 1- Where is implemented the write_data fct callback for sending sccp message. have I to reimplement it with mtp3 layer to send sccp data or it is implemented. 2- What are missing features of the library. Please help. Thank you.

2 1