baseband-devel October 2021

baseband-devel@lists.osmocom.org

3 participants
4 discussions

Start a nNew thread

Engagetted !

by Sébastien Lorquet

http://www.engadget.com/2010/12/29/researchers-eavesdrop-on-encrypted-gsm-c… Congrats!

11 months, 3 weeks

GSMTAP messages not generated

by Mario Lucas

Dear All, I am running a GSM stack: osmo-stp smo-msc osmo-hlr osmo-bsc osmo-bts-trx osmo-trx-lms It seems that my transmitter is emitting radio-waves into air (osmo-bts-trx and osmo-trx-lms communicate with each other through ports 5702 / 5802 — pls see attached printscreen), however i could not make GSMTAP tracing. Osmo-bts-trx does not send GSMTAP messages to port 4729. In most recent version of osmo-bts, GSMTAP tracing is arranged through config file: bts 0 gsmtap-remote-host 127.0.0.1 gsmtap-sapi ccch I could not run the GSMTAP tracing even in previous verions of osmo-bts where you have to specify in synopsis when you call a program: /usr/bin/osmo-bts-trx -s -c /etc/osmocom/osmo-bts-trx.cfg --gsmtap-ip 127.0.0.1 I thought may be i am having some issues in stack components behind osmo-bts for example in osmo-bsc or behind and i tried to run virtual bts. When i tried to run osmo-bts-virtual GSMTAP messages were visible in wireshark (please see attached file osmo-bts-virtual), therefore bts-bsc communication is good. However I still could not figure out why my osmo-bts-trx does not send GSMTAP messages. Or would you advise what log might be helpful to see what i am doing wrong …. Thank you for your always helpful assistance -- Mario Lucas

3 years, 11 months

(bts=0,trx=0,ts=0,pchan_from_config=CCCH+SDCCH4,state=NOT_INITIALIZED) Abis RSL rx CCHAN: mismatching chan_nr=0x90

by Mario Lucas

When i try to run osmo-bts-trx i am getting following log in osmo-bsc abis_rsl.c:142 (bts=0,trx=0,ts=0,pchan_from_config=CCCH+SDCCH4,state=NOT_INITIALIZED) Abis RSL rx CCHAN: mismatching chan_nr=0x90 I tried to find out in bugs: https://osmocom.org/issues/4872 but could not understand … i am using osmo-bsc 1.7.1 and osmo-bts-trx 1.3.3 Could you pls advise me briefly whats happening and how to sort it out ? -- Mario Lucas

3 years, 11 months

libmobile.a(mncc_sock.o) undefined reference

by Mario Lucas

Dear All, I am having following error during ‘make’ osmocombb: libmobile.a(mncc_sock.o): In function `mncc_sock_accept': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:229: undefined reference to `osmo_fd_read_disable' libmobile.a(mncc_sock.o): In function `mncc_sock_close': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:95: undefined reference to `osmo_fd_read_enable' libmobile.a(mncc_sock.o): In function `mncc_sock_write': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:159: undefined reference to `osmo_fd_write_disable' /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:174: undefined reference to `osmo_fd_write_enable' libmobile.a(mncc_sock.o): In function `mncc_sock_from_cc': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:75: undefined reference to `osmo_fd_write_enable' libmobile.a(mncc_sock.o): In function `mncc_sock_write_pending': /home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile/mncc_sock.c:81: undefined reference to `osmo_fd_write_enable' collect2: error: ld returned 1 exit status Makefile:394: recipe for target 'mobile' failed make[3]: *** [mobile] Error 1 make[3]: Leaving directory '/home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src/mobile' Makefile:325: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23/src' Makefile:351: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/ubuntu/Desktop/OsmocomBB/master/src/host/layer23' Makefile:97: recipe for target 'host/layer23/layer23' failed make: *** [host/layer23/layer23] Error 2 My arm-elf-gcc is gcc version 4.5.2 (GCC) libosmocore 1.4.1 I believe it is something with libraries but could not figure out …. -- Mario Lucas

3 years, 12 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel October 2021