OpenBSC installed but missing ipaccess and abisip-find
Hello. I just followed the step by step procedure outlined in the wiki to compile OpenBSC on Ubuntu 16.04 LTS for the ip.access nanoBTS. My problem is that the folder ipaccess which has the ipaccess.config is missing and so is the abisip-find file. Any leads on why this is happening? I had seen somewhere that the above can be found in the osmocom-ipaccess-utils from the repo but that too is unavailable. Many thanks -tyrus
Hi, ipaccess related binaries have been removed from openbsc.git in 07bcda7554a981cb23af9eb4ea9f5e23573580c6, and have been actually maintained (and deb packages generated) in osmo-bsc.git. You definetly want to build them from there. Please point us to related docs if they are outdated. -- - Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
Hi Ty, aside from Pau's comment, I'm wondering why you aren't using the binary packages we provide. I of course understand there's tons of reasons why you would want to build code from source (trust, security, ...) but then typically if you build from source, then Please also note that OpenBSC/OsmoNITB from openbsc.git is discontinued since 2017. Please use new "CNI" stack with software from osmo-bsc.git, osmo-msc.git, osmo-hlr.git, etc. -- - Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Thanks for the revert Pau. Then the Wiki is outdated https://osmocom.org/projects/openbsc/wiki/Building_OpenBSC Thank you Harald. Managed to find the .debs and installed them successfully. Problem is the abisip-find doesn't find the nanoBTS which is clearly powered on. Any insight into this. In addition, I'm getting this symbol error when I run osmo-nitb tyrus@the-jedi-council:~/openbsc/openbsc/src/osmo-nitb$ ./osmo-nitb .*/osmo-nitb: /usr/lib/i386-linux-gnu/libosmoctrl.so.0: no version information available (required by ./osmo-nitb)* *./osmo-nitb: relocation error: ./osmo-nitb: symbol ctrl_vty_init, version LIBOSMOCTRL_1.0 not defined in file libosmoctrl.so.0 with link time reference* Any idea what could be broken? I have an idea it's a linker issue but not too sure how to troubleshoot this. Also was nice attending your talk when you were last in Nairobi. Good work. Many thanks On Thu, May 9, 2019 at 10:40 PM Harald Welte <laforge@gnumonks.org> wrote:
Hi Ty,
aside from Pau's comment, I'm wondering why you aren't using the binary packages we provide. I of course understand there's tons of reasons why you would want to build code from source (trust, security, ...) but then typically if you build from source, then
Please also note that OpenBSC/OsmoNITB from openbsc.git is discontinued since 2017.
Please use new "CNI" stack with software from osmo-bsc.git, osmo-msc.git, osmo-hlr.git, etc.
-- - Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Hi. On 5/10/19 10:20 AM, ty wrote:
tyrus@the-jedi-council:~/openbsc/openbsc/src/osmo-nitb$ ./osmo-nitb .*/osmo-nitb: /usr/lib/i386-linux-gnu/libosmoctrl.so.0: no version information available (required by ./osmo-nitb)* *./osmo-nitb: relocation error: ./osmo-nitb: symbol ctrl_vty_init, version LIBOSMOCTRL_1.0 not defined in file libosmoctrl.so.0 with link time reference* * *
You say you installed programs from .deb but you are still running the version of osmo-nitb from your compiled version. Use the one from packages to avoid this kind of issues, otherwise the version you built and the ones from the .deb packages won't much unless you really know what you are doing. -- - Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
Hi Pau Once again I truly appreciate your revert. You're right. I managed to pull the osmoBsc and compiled it together with the dependencies. Every thing works fine until I ran 'make' which throws this struct error In file included from gsm_04_80_utils.c:22:0: /usr/local/include/osmocom/gsm/gsm0480.h:120:14: note: declared here struct msgb *gsm0480_create_ussd_release_complete(void) ^ CC gsm_data.o CC handover_cfg.o CC handover_decision.o CC handover_decision_2.o CC handover_fsm.o CC handover_logic.o CC handover_vty.o CC lchan_fsm.o CC lchan_rtp_fsm.o lchan_rtp_fsm.c: In function ‘mgcp_pick_codec’: lchan_rtp_fsm.c:841:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param_present’ verb_info->param_present = true; ^ lchan_rtp_fsm.c:842:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned_present = true; ^ lchan_rtp_fsm.c:851:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned = true; ^ lchan_rtp_fsm.c:854:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned = lchan->conn->sccp.msc->amr_octet_aligned; ^ Makefile:616: recipe for target 'lchan_rtp_fsm.o' failed make[3]: *** [lchan_rtp_fsm.o] Error 1 make[3]: Leaving directory '/home/tyrus/osmo-bsc/src/osmo-bsc' Makefile:405: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/tyrus/osmo-bsc/src' Makefile:448: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/tyrus/osmo-bsc' Makefile:380: recipe for target 'all' failed make: *** [all] Error 2 So I have tried all weekend to debug it but unfortunately haven't made much headway. Any leads? Many thanks On Mon, May 13, 2019 at 12:30 PM Pau Espin Pedrol <pespin@sysmocom.de> wrote:
Hi.
On 5/10/19 10:20 AM, ty wrote:
tyrus@the-jedi-council:~/openbsc/openbsc/src/osmo-nitb$ ./osmo-nitb .*/osmo-nitb: /usr/lib/i386-linux-gnu/libosmoctrl.so.0: no version information available (required by ./osmo-nitb)* *./osmo-nitb: relocation error: ./osmo-nitb: symbol ctrl_vty_init, version LIBOSMOCTRL_1.0 not defined in file libosmoctrl.so.0 with link time reference* * *
You say you installed programs from .deb but you are still running the version of osmo-nitb from your compiled version. Use the one from packages to avoid this kind of issues, otherwise the version you built and the ones from the .deb packages won't much unless you really know what you are doing.
-- - Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
Hi Ty, On 13/05/2019 15.31, ty wrote:
In file included from gsm_04_80_utils.c:22:0: /usr/local/include/osmocom/gsm/gsm0480.h:120:14: note: declared here struct msgb *gsm0480_create_ussd_release_complete(void) ^
Most probably this is a deprecation warning that you could ignore.
CC lchan_rtp_fsm.o lchan_rtp_fsm.c: In function ‘mgcp_pick_codec’: lchan_rtp_fsm.c:841:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param_present’ verb_info->param_present = true; ^ lchan_rtp_fsm.c:842:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned_present = true; ^ lchan_rtp_fsm.c:851:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned = true; ^ lchan_rtp_fsm.c:854:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned = lchan->conn->sccp.msc->amr_octet_aligned; ^ Makefile:616: recipe for target 'lchan_rtp_fsm.o' failed make[3]: *** [lchan_rtp_fsm.o] Error 1 make[3]: Leaving directory '/home/tyrus/osmo-bsc/src/osmo-bsc'
Install the latest version of osmo-mgw from its maser branch and try again. These two members were added in commit 228e59158 and it seems you have installed an older version. Regards, Vasil
Hey all. Just bumping this since I haven’t heard any revert Thanks On Mon, 13 May 2019 at 15:31, ty <tyruskam@gmail.com> wrote:
Hi Pau Once again I truly appreciate your revert. You're right. I managed to pull the osmoBsc and compiled it together with the dependencies. Every thing works fine until I ran 'make' which throws this struct error
In file included from gsm_04_80_utils.c:22:0: /usr/local/include/osmocom/gsm/gsm0480.h:120:14: note: declared here struct msgb *gsm0480_create_ussd_release_complete(void) ^ CC gsm_data.o CC handover_cfg.o CC handover_decision.o CC handover_decision_2.o CC handover_fsm.o CC handover_logic.o CC handover_vty.o CC lchan_fsm.o CC lchan_rtp_fsm.o lchan_rtp_fsm.c: In function ‘mgcp_pick_codec’: lchan_rtp_fsm.c:841:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param_present’ verb_info->param_present = true; ^ lchan_rtp_fsm.c:842:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned_present = true; ^ lchan_rtp_fsm.c:851:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned = true; ^ lchan_rtp_fsm.c:854:12: error: ‘struct mgcp_conn_peer’ has no member named ‘param’ verb_info->param.amr_octet_aligned = lchan->conn->sccp.msc->amr_octet_aligned; ^ Makefile:616: recipe for target 'lchan_rtp_fsm.o' failed make[3]: *** [lchan_rtp_fsm.o] Error 1 make[3]: Leaving directory '/home/tyrus/osmo-bsc/src/osmo-bsc' Makefile:405: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/tyrus/osmo-bsc/src' Makefile:448: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/tyrus/osmo-bsc' Makefile:380: recipe for target 'all' failed make: *** [all] Error 2 So I have tried all weekend to debug it but unfortunately haven't made much headway. Any leads?
Many thanks
On Mon, May 13, 2019 at 12:30 PM Pau Espin Pedrol <pespin@sysmocom.de> wrote:
Hi.
On 5/10/19 10:20 AM, ty wrote:
tyrus@the-jedi-council:~/openbsc/openbsc/src/osmo-nitb$ ./osmo-nitb .*/osmo-nitb: /usr/lib/i386-linux-gnu/libosmoctrl.so.0: no version information available (required by ./osmo-nitb)* *./osmo-nitb: relocation error: ./osmo-nitb: symbol ctrl_vty_init, version LIBOSMOCTRL_1.0 not defined in file libosmoctrl.so.0 with link time reference* * *
You say you installed programs from .deb but you are still running the version of osmo-nitb from your compiled version. Use the one from packages to avoid this kind of issues, otherwise the version you built and the ones from the .deb packages won't much unless you really know what you are doing.
-- - Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
-- Excuse my brevity, sent on the run.
On 27/06/2019 21:55, ty wrote:
Hey all. Just bumping this since I haven’t heard any revert
In fact there was a reply, via the mailing list, from Vasil who explained the last hurdles you were facing. http://lists.osmocom.org/pipermail/openbsc/2019-May/012932.html IIUC, you seem to have a goal which is to test/run an ip.access nanoBTS, however it seems you are getting bogged down in problems which are more leading you in the direction of C development, possibly distracting from your goal? My suggestions are: 1) If at all possible, build a new VM or install a fresh OS and install the osmo stack from packages. https://osmocom.org/projects/cellular-infrastructure/wiki/Latest_Builds If a fresh OS install is really not possible, then clean up your existing work machine; * run make uninstall for each component you installed from source. * Even then, check for and remove and libosmo* (and maybe other lib* and/or executables from osmo source) from where ever you installed from source. This is probably /usr/local/lib * Now install from packages. 2) Test your ip.access nanoBTS and deal with learning how to configure all the parts of the osmo stack to have it work. 3) If you want, and now with the first hand knowledge of what a running system looks like, return to the project of building from source. Be aware that there is a lot of development and things often move quickly. It does happen that you cannot clone one repo, and expect to compile it's master branch against libraries you compiled yesterday. If you are going to compile the entire stack, know that sometimes dependencies are not in obvious places. but for now, How do you feel about cleaning up your work machine and using the packages to get your hardware running?
participants (5)
-
Harald Welte -
Keith -
Pau Espin Pedrol -
ty -
Vasil Velichkov