From laforge at gnumonks.org Mon Jan 1 17:47:05 2018 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 1 Jan 2018 18:47:05 +0100 Subject: Osmocom Year 2017 Review Message-ID: <20180101174705.GG20410@nataraja> Dear all, I've written up a "short" review of what I perceive as the most important events in the Osmocom Cellular Infrastructure projects in 2017. See http://osmocom.org/news/84 for all details, or below for a raw copy+paste: h1. Osmocom Review 2017 This is a review of the most significant changes and events in the Osmocom Cellular Infrastructure projects in 2017 h2. January 2017 * announce of first ever public [[OsmoCon:]] conference in April * osmo-bts ** Add Abis OML failure event reporting ** fix memory leaks in osmo-bts-{sysmo,lc15} at every channel activation * openbsc/osmo-bsc ** support multiple UARFCNs in SI2quater * osmo-hlr ** add test suite for 2G and 3G authentication ** fix UMTS AKA re-sync h2. February 2017 * weekly manual testing with related weekly test reports to mailing list * "heads-up about the (lack of a )future of osmo-nitb":http://lists.osmocom.org/pipermail/openbsc/2017-February/010300.html * "heads-up about libosmo-sccp SIGTRAN work":http://lists.osmocom.org/pipermail/openbsc/2017-February/010274.html * "sysmo-usim-tool":http://lists.osmocom.org/pipermail/openbsc/2017-February/010317.html * libosmo-abis ** unix domain socket support (for Ericsson L2TP) * osmo-bts ** fix AMR HR DTX FSM logic ** fix SACCH sending fo system information with enum value > 7 ** osmo-bts-trx: fix RXGAIN and POWER parameters on second TRX ** fix TCH/H interleaving table bit position ** sysmoBTS 1020/1100: slow power ramp-up on TRX enable * osmo-sgsn ** fix PDP context activation memory allocation bug ** integrate support for UMTS AKA * openggsn ** fix kernel-gtp tunnel creation/removal for GTPv1 ** release 0.93 h3. March 2017 * "cgit improvements":http://lists.osmocom.org/pipermail/openbsc/2017-March/010448.html (about page, change-ID hyperlinks, issue hyperlinks) * Add README.md files to all our repositories * libosmocore ** migrate gsm 05.03 coding from OsmoBTS to libosmocore ** fix SQN / SEQ handling in UMTS AKA ** 3GPP AoIP message encoding/decoding * libosmo-abis ** fix ever-increasing jitter buffer * libosmo-netif ** handle SCTP in in stream server ** doxygen documentation on stream an datagram modules * osmo-bts ** octphy: CBCH support ** include MS timing offset in RSL measurements * osmo-sgsn ** handle IMSIs with leading zeroes * osmo-bsc ** fix T3186 encoding in SI13 ** Improved Ericsson OM2000/RBS2000 support ** new ctrl2soap proxy in python * osmo-hlr ** add CTRL interface ** fix SQN/SEQ handling in UMTS AKA h3. April 2017 * "update of coding style for longer line lengths":http://lists.osmocom.org/pipermail/openbsc/2017-April/010502.html * [[osmo-dev-con:OsmoCon2017]] and [[osmo-dev-con:OsmoDevCon2017]] * libosmocore ** "control interface for osmo_fsm":http://lists.osmocom.org/pipermail/openbsc/2017-April/010542.html * libosmo-netif ** fix file descriptor leak in error paths ** work around linux kenrel SCTP bug with sender_dry_events ** RTP marker bit support * libosmo-sccp ** Add new [[libosmo-sigtran:]] library with SS7 AS/ASP Link/Linkset handling, M3UA support, new FSM based SCCP implementation ** Add [[osmo-stp:]] program * osmo-bts ** inform BSC of PCU disconnect ** fix measurement reporting period ** exclude idle channels from uplink measurement processing ** octphy: measurement reports h3. May 2017 * libosmocore ** fix embedded builds ** import and generalise 'sercomm' from osmocom-bb into libosmocore ** SSE optimized convolutional coder ** fix wrong GSM FR codec SID frame generation ** doxygen docs for libosmocoding * osmo-bsc ** TS 04.14 mobile station side loop control * osmo-bts ** consistently check all RSL and OML TLVs for minimum length value ** fix bit-order in every HR codec parameter (spec compliance) ** OML get/set attribute handling ** SI2quater support ** bypass radio link timeout for lab testing * osmo-bsc ** PCU socket support for BSC-colocated PCU for Ericsson RBS2000 ** reelase 1.0.1 * "M3UA and SUA testing as part of jenkins":http://lists.osmocom.org/pipermail/openbsc/2017-May/010698.html * "osmo-gsm-tester produces successful runs with NITB as well as new AoIP":http://lists.osmocom.org/pipermail/openbsc/2017-May/010760.html h3. June 2017 * libosmocore ** doxygen autobrief ** doxygen documentation for libosmogb * osmo-bts ** use CLOCK_MONOTONIC timer for GSM frame timer ** PDTCH loopback support h3. July 2017 * "Plan for openbsc.git split and code review":http://lists.osmocom.org/pipermail/openbsc/2017-July/010914.html * libosmocore ** PDP charging characteristics in GSUP ** PRBS sequence generators ** multicast IP related helper functions ** 'make release' target * libosmo-sccp ** SCCP address book * osmo-bts ** new virtual BTS @osmo-bts-virtual@ for testing without radio hardware ** don't send dummy UI frames on unused BCCH slots on TC=5 ** GSMTAP: don't log/send fill frames consisting of only padding * osmo-hlr ** change to default GSUP port 4222 h3. August 2017 * "Support for SMPP Delivery Receipt / GSM03.40 Status Report":http://lists.osmocom.org/pipermail/openbsc/2017-August/011023.html * "Jenkins now executing M3UA, SUA and GGSN testsuite":http://lists.osmocom.org/pipermail/openbsc/2017-August/011043.html * libosmocore ** fix crash in lapd_est_req() * libosmo-abis ** release 0.4.0 * osmo-bts ** osmo-bts-trx: fix MS power control loop ** release 0.6.0 ** support sending/removing SI13 to/from PCU * osmo-bsc ** indicate R99+ MSC in SI3 to enable UMTS AKA over GERAN * osmo-sgsn ** properly report GERAN/UTRAN mode in PDP CTX ACT REQ to GGSN * osmo-msc ** implement IuCS support ** split openbsc.git into osmo-bsc.git, osmo-msc.git and osmo-sgsn.git * openggsn ** Add IPv6 address pool and IPV6 user (inner) plane support ** release 0.94 h3. September 2017 * libosmocore.git ** "'show talloc-context' VTY introspection":http://lists.osmocom.org/pipermail/openbsc/2017-June/010771.html ** CTRL parsing unit tests ** unification of vty exit/end commands * osmo-hlr ** CTRL interface tests -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From viktor.tsymbalyuk at gmail.com Thu Jan 18 08:59:20 2018 From: viktor.tsymbalyuk at gmail.com (Viktor Tsymbalyuk) Date: Thu, 18 Jan 2018 10:59:20 +0200 Subject: sgsnemu: why --listen and --remote in one network? Message-ID: <76cbff98-9036-2826-7b8e-1c22f116f2fd@gmail.com> Hello, I'm querying? why sgsnemu shoul work in a same network with ggsn? What the reason for such limitation? -- Viktor From laforge at gnumonks.org Thu Jan 18 16:37:50 2018 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 18 Jan 2018 17:37:50 +0100 Subject: sgsnemu: why --listen and --remote in one network? In-Reply-To: <76cbff98-9036-2826-7b8e-1c22f116f2fd@gmail.com> References: <76cbff98-9036-2826-7b8e-1c22f116f2fd@gmail.com> Message-ID: <20180118163750.g7smilusk557kwfu@nataraja> Hi Viktor, On Thu, Jan 18, 2018 at 10:59:20AM +0200, Viktor Tsymbalyuk wrote: > Hello, > I'm querying? why sgsnemu shoul work in a same network with ggsn? > What the reason for such limitation? can you please be more specific, what you are referrinng to? If you think some statement or documentation is incorrect, please quote and/or point exactly to what you are referring. There's code comments, readme files in the source repository, wiki, manuals, ... -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From viktor.tsymbalyuk at gmail.com Fri Jan 19 11:07:05 2018 From: viktor.tsymbalyuk at gmail.com (Viktor Tsymbalyuk) Date: Fri, 19 Jan 2018 13:07:05 +0200 Subject: sgsnemu: why --listen and --remote in one network? In-Reply-To: <20180118163750.g7smilusk557kwfu@nataraja> References: <76cbff98-9036-2826-7b8e-1c22f116f2fd@gmail.com> <20180118163750.g7smilusk557kwfu@nataraja> Message-ID: Hello Harald, On 2018-01-18 18:37, Harald Welte wrote: > Hi Viktor, > > On Thu, Jan 18, 2018 at 10:59:20AM +0200, Viktor Tsymbalyuk wrote: >> Hello, >> I'm querying? why sgsnemu shoul work in a same network with ggsn? >> What the reason for such limitation? > can you please be more specific, what you are referrinng to? If you > think some statement or documentation is incorrect, please quote and/or > point exactly to what you are referring. There's code comments, readme files > in the source repository, wiki, manuals, ... > Sorry, it's was my fault. Let's close thread. I were confused by sting "Use the same LAN switch as the one your SGSN is connected to." from http://git.osmocom.org/osmo-ggsn/about/ If you interesting my mind, it's better to remove this string. and delete "--dns 10.20.38.51" from "sgsnemu --listen 10.0.0.50 --remote 10.0.0.40 --dns 10.20.38.51 --timelimit 10 --contexts 0" in point 4. DNS not needed in echo mechanism. From laforge at gnumonks.org Fri Jan 19 14:10:09 2018 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 19 Jan 2018 15:10:09 +0100 Subject: sgsnemu: why --listen and --remote in one network? In-Reply-To: References: <76cbff98-9036-2826-7b8e-1c22f116f2fd@gmail.com> <20180118163750.g7smilusk557kwfu@nataraja> Message-ID: <20180119141007.7vf25gpj7ivptpg7@nataraja> Hi Viktor, On Fri, Jan 19, 2018 at 01:07:05PM +0200, Viktor Tsymbalyuk wrote: > I were confused by sting "Use the same LAN switch as the one your SGSN is > connected to." from http://git.osmocom.org/osmo-ggsn/about/ > If you interesting my mind, it's better to remove this string. Thanks, I have submitted the following patch https://gerrit.osmocom.org/#/c/5927/ -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From viktor.tsymbalyuk at gmail.com Wed Jan 24 13:37:36 2018 From: viktor.tsymbalyuk at gmail.com (Viktor Tsymbalyuk) Date: Wed, 24 Jan 2018 15:37:36 +0200 Subject: sgsnemu ignoring Request accepted Message-ID: <3d21d66d-53a4-f2dd-1e53-64767b267548@gmail.com> Hello, I continue to play with sgsnemu, and found that it stopped for some reason after "Request accepted". Does sgsnemu working? At my mind problem inside `create_pdp_conf` function . After small changes, I start to see icmp inside gtp tunnel in trace. Please check attachments with console output, patch and pcap. May be I has wrong understanding. -- Viktor -------------- next part -------------- ## original ``` ubuntu at test:~/osmo-ggsn$ sudo sgsnemu --listen 10.121.0.18 --remote 91.184.97.160 --contexts 1 --apn internet.ge.beeline.net --imsi 282040234567890 --rai=282.04.0001.0001 --nsapi=5 --qos=34824735 --charging=2 --createif --defaultroute -d --pingcount=3 --pinghost=10.123.0.18 remote: 91.184.97.160 listen: 10.121.0.18 debug: 1 imsi: 282040234567890 qos: 0x213621f qose1: 0x9396404074f9ffff qose2: 0x11 qose3: 0x0101 qose4: 0x4040 charging: 0x02 apn: internet.ge.beeline.net msisdn: 46702123456 uid: mig pwd: hemmelig pidfile: ./sgsnemu.pid statedir: ./ contexts: 1 timelimit: 0 createif: 1 defaultroute: 1 pinghost: 10.123.0.18 pingrate: 1 pingsize: 56 pingcount: 3 pingquiet: 0 norecovery: 0 no-tx-gpdu-seq: 0 Using default DNS server Local IP address is: 10.121.0.18 (10.121.0.18) Remote IP address is: 91.184.97.160 (91.184.97.160) IMSI is: 282040234567890 (0xf098765432040282) Using NSAPI: 5 Using GTP version: 1 Using APN: internet Using selection mode: 1 Using RAI: 282.04.0001.0001 ->mcc : 282 ->mnc : 04 ->LAC: 0001 ->RAC : 0001 Using MSISDN: 46702123456 Using ping host: 10.123.0.18 (10.123.0.18) Initialising GTP library <000d> gtp.c:757 GTP: gtp_newgsn() started at 10.121.0.18 <000d> gtp.c:714 State information file (.//gsn_restart) not found. Creating new file. Setting up interface Done initialising GTP library Sending off echo request Setting up PDP context #0 Waiting for response from ggsn........ idletime.tv_sec 3, idleTime.tv_usec 0 Received echo response idletime.tv_sec 3, idleTime.tv_usec 0 idletime.tv_sec 3, idleTime.tv_usec 0 Received create PDP context response. Cause value: 128 ``` ## patch (in46a_from_eua(&pdp->eua, &addr)<=0) ``` ubuntu at test:~/osmo-ggsn$ sudo sgsnemu --listen 10.121.0.18 --remote 91.184.97.160 --contexts 1 --apn internet.ge.beeline.net --imsi 282040234567890 --rai=282.04.0001.0001 --nsapi=5 --qos=34824735 --charging=2 --createif --defaultroute -d --pingcount=3 --pinghost=10.123.0.18 remote: 91.184.97.160 listen: 10.121.0.18 debug: 1 imsi: 282040234567890 qos: 0x213621f qose1: 0x9396404074f9ffff qose2: 0x11 qose3: 0x0101 qose4: 0x4040 charging: 0x02 apn: internet.ge.beeline.net msisdn: 46702123456 uid: mig pwd: hemmelig pidfile: ./sgsnemu.pid statedir: ./ contexts: 1 timelimit: 0 createif: 1 defaultroute: 1 pinghost: 10.123.0.18 pingrate: 1 pingsize: 56 pingcount: 3 pingquiet: 0 norecovery: 0 no-tx-gpdu-seq: 0 Using default DNS server Local IP address is: 10.121.0.18 (10.121.0.18) Remote IP address is: 91.184.97.160 (91.184.97.160) IMSI is: 282040234567890 (0xf098765432040282) Using NSAPI: 5 Using GTP version: 1 Using APN: internet Using selection mode: 1 Using RAI: 282.04.0001.0001 ->mcc : 282 ->mnc : 04 ->LAC: 0001 ->RAC : 0001 Using MSISDN: 46702123456 Using ping host: 10.123.0.18 (10.123.0.18) Initialising GTP library <000d> gtp.c:757 GTP: gtp_newgsn() started at 10.121.0.18 Setting up interface Done initialising GTP library Sending off echo request Setting up PDP context #0 Waiting for response from ggsn........ idletime.tv_sec 3, idleTime.tv_usec 0 Received echo response idletime.tv_sec 3, idleTime.tv_usec 0 Received create PDP context response. IP address: 10.16.0.2 Create_ping 0 idletime.tv_sec 0, idleTime.tv_usec 999952 Create_ping -1140 idletime.tv_sec 0, idleTime.tv_usec 998791 idletime.tv_sec 0, idleTime.tv_usec 998218 Create_ping -1039 idletime.tv_sec 10, idleTime.tv_usec 0 idletime.tv_sec 10, idleTime.tv_usec 0 Disconnecting PDP context #0 ----10.123.0.18 PING Statistics---- 3 packets transmitted in 12.012 seconds, 0 packets received, 100% packet loss 0 packets received in total 0 packets transmitted idletime.tv_sec 3, idleTime.tv_usec 0 Received delete PDP context response. Cause value: 128 ``` -------------- next part -------------- diff --git a/sgsnemu/sgsnemu.c b/sgsnemu/sgsnemu.c index bb55b1c..ffe9293 100644 --- a/sgsnemu/sgsnemu.c +++ b/sgsnemu/sgsnemu.c @@ -1400,7 +1400,7 @@ static int create_pdp_conf(struct pdp_t *pdp, void *cbp, int cause) return EOF; /* Not what we expected */ } - if (in46a_from_eua(&pdp->eua, &addr)) { + if (in46a_from_eua(&pdp->eua, &addr)<=0) { printf ("Received create PDP context response. Cause value: %d\n", cause); -------------- next part -------------- A non-text attachment was scrubbed... Name: sgsnemu_orig.pcap Type: application/octet-stream Size: 816 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sgsnemu_patch.pcap Type: application/octet-stream Size: 1724 bytes Desc: not available URL: From pespin at sysmocom.de Wed Jan 24 15:18:36 2018 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Wed, 24 Jan 2018 16:18:36 +0100 Subject: sgsnemu ignoring Request accepted In-Reply-To: <3d21d66d-53a4-f2dd-1e53-64767b267548@gmail.com> References: <3d21d66d-53a4-f2dd-1e53-64767b267548@gmail.com> Message-ID: <8e85a7bb-a04b-70c2-c635-276825ce8756@sysmocom.de> Hi Viktor, indeed, you found a bug I introduced in osmo-ggsn 2d6a69e69a4b4cb2b8cc63c4810dae44e5a4d8f6, sorry for that, I didn't notice it since I was testing it with osmo-sgsn instead of using sgsnemu. You patch is fine, but I'd argue it would be more correct to use "< 1" for the condition since it now returns the amount of addresses parsed (or -1 in case of error). And better add whitespace in the comparison. Can you please submit the patch to gerrit? Add a reference to its description: Fixes: 2d6a69e69a4b4cb2b8cc63c4810dae44e5a4d8f6 ("Add support for IPv4v6 End User Addresses") You can add me as reviewer. Also please note that sgsnemu doesn't yet support IPv4v6 EUAs as opposed to osmo-ggsn. I only added support for it (in the commit introducing the bug) because modems in osmo-gsm-tester were using that one and I needed to support it in osmo-ggsn to have the tests working. As I never used sgsnemu before, I only patched it to account for the changes in libgtp but without adding the support for the new feature there. Regards, -- - Pau Espin Pedrol 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 From viktor.tsymbalyuk at gmail.com Thu Jan 25 14:52:02 2018 From: viktor.tsymbalyuk at gmail.com (Viktor Tsymbalyuk) Date: Thu, 25 Jan 2018 16:52:02 +0200 Subject: sgsnemu ignoring Request accepted In-Reply-To: <8e85a7bb-a04b-70c2-c635-276825ce8756@sysmocom.de> References: <3d21d66d-53a4-f2dd-1e53-64767b267548@gmail.com> <8e85a7bb-a04b-70c2-c635-276825ce8756@sysmocom.de> Message-ID: <154d19b2-e80c-8a30-1bd2-e26647b309e1@gmail.com> Hello Pau, Thank you for detailed answer. > Can you please submit the patch to gerrit? yes, I'll do it. But please give me some time. gerrit - is a new challenge for me)))) Thank you. -- Viktor On 2018-01-24 17:18, Pau Espin Pedrol wrote: > Hi Viktor, > > indeed, you found a bug I introduced in osmo-ggsn > 2d6a69e69a4b4cb2b8cc63c4810dae44e5a4d8f6, sorry for that, I didn't > notice it since I was testing it with osmo-sgsn instead of using sgsnemu. > > You patch is fine, but I'd argue it would be more correct to use "< 1" > for the condition since it now returns the amount of addresses parsed > (or -1 in case of error). And better add whitespace in the comparison. > > Can you please submit the patch to gerrit? Add a reference to its > description: > Fixes: 2d6a69e69a4b4cb2b8cc63c4810dae44e5a4d8f6 ("Add support for > IPv4v6 End User Addresses") > > You can add me as reviewer. > > Also please note that sgsnemu doesn't yet support IPv4v6 EUAs as > opposed to osmo-ggsn. I only added support for it (in the commit > introducing the bug) because modems in osmo-gsm-tester were using that > one and I needed to support it in osmo-ggsn to have the tests working. > As I never used sgsnemu before, I only patched it to account for the > changes in libgtp but without adding the support for the new feature > there. > > Regards, > From pespin at sysmocom.de Thu Jan 25 14:56:34 2018 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Thu, 25 Jan 2018 15:56:34 +0100 Subject: sgsnemu ignoring Request accepted In-Reply-To: <154d19b2-e80c-8a30-1bd2-e26647b309e1@gmail.com> References: <3d21d66d-53a4-f2dd-1e53-64767b267548@gmail.com> <8e85a7bb-a04b-70c2-c635-276825ce8756@sysmocom.de> <154d19b2-e80c-8a30-1bd2-e26647b309e1@gmail.com> Message-ID: <5bda687e-5079-929e-0a96-193f504d7387@sysmocom.de> Hi Viktor, You can find all the related gerrit information in https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit Feel free to improve if you see something wrong/missing. If you lack wiki edit permissions, ask for them in IRC. -- - Pau Espin Pedrol 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 From viktor.tsymbalyuk at gmail.com Fri Jan 26 11:05:56 2018 From: viktor.tsymbalyuk at gmail.com (Viktor Tsymbalyuk) Date: Fri, 26 Jan 2018 13:05:56 +0200 Subject: sgsnemu ignoring Request accepted In-Reply-To: <5bda687e-5079-929e-0a96-193f504d7387@sysmocom.de> References: <3d21d66d-53a4-f2dd-1e53-64767b267548@gmail.com> <8e85a7bb-a04b-70c2-c635-276825ce8756@sysmocom.de> <154d19b2-e80c-8a30-1bd2-e26647b309e1@gmail.com> <5bda687e-5079-929e-0a96-193f504d7387@sysmocom.de> Message-ID: Hello Pau, Thank you for the link. I've done it. Thank you. ?-- Viktor On 2018-01-25 16:56, Pau Espin Pedrol wrote: > Hi Viktor, > > You can find all the related gerrit information in > https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit > > Feel free to improve if you see something wrong/missing. If you lack > wiki edit permissions, ask for them in IRC. > From xinke.zhang at hotmail.com Mon Jan 29 06:51:19 2018 From: xinke.zhang at hotmail.com (XINKE ZHANG) Date: Mon, 29 Jan 2018 06:51:19 +0000 Subject: Problem when building OsmoSGSN In-Reply-To: References: Message-ID: Hi all, I built OsmoSGSN with the these following instructions. git clone git://git.osmocom.org/osmo-sgsn cd osmo-sgsn autoreconf -fi ./configure --enable-iu make -j5 make check make install sudo ldconfig And no error came out during building process, but no ?osmo-sgsn? executable was found. Pls help me. Thank you in advance. Best Regards, Xinke -------------- next part -------------- An HTML attachment was scrubbed... URL: From pespin at sysmocom.de Mon Jan 29 11:36:58 2018 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Mon, 29 Jan 2018 12:36:58 +0100 Subject: Problem when building OsmoSGSN In-Reply-To: References: Message-ID: <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> Hi, it's difficult to say if you don't provide any log or detailed information other than "it is not working", but from your input I'd say that usually you need to run make install as root (sudo make install). If you check more closely you will see that it most probably is outputting some "Permission denied" error during that step. -- - Pau Espin Pedrol 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 From pespin at sysmocom.de Tue Jan 30 09:19:27 2018 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Tue, 30 Jan 2018 10:19:27 +0100 Subject: Problem when building OsmoSGSN In-Reply-To: References: <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> Message-ID: <679ce868-a14e-45f9-eb0e-c4c9ab1b2f51@sysmocom.de> Hi, I think you forgot to attach the "make install" log, which is the interesting one in this case. -- - Pau Espin Pedrol 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 From xinke.zhang at hotmail.com Tue Jan 30 06:53:22 2018 From: xinke.zhang at hotmail.com (XINKE ZHANG) Date: Tue, 30 Jan 2018 06:53:22 +0000 Subject: Problem when building OsmoSGSN In-Reply-To: <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> References: , <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> Message-ID: Hi, Thanks for your advice. I ran make install as root, and there was no "Permission denied" error. Log files are attached to this email. Pls help check this problem. Thank you. Best Regards, Xinke ________________________________ From: Pau Espin Pedrol Sent: Monday, January 29, 2018 11:36 To: XINKE ZHANG; osmocom-net-gprs at lists.osmocom.org Subject: Re: Problem when building OsmoSGSN Hi, it's difficult to say if you don't provide any log or detailed information other than "it is not working", but from your input I'd say that usually you need to run make install as root (sudo make install). If you check more closely you will see that it most probably is outputting some "Permission denied" error during that step. -- - Pau Espin Pedrol http://www.sysmocom.de/ sysmocom - custom-tailored mobile telephony solutions www.sysmocom.de News: sysmocom introduces new sysmoBTS 2100. The sysmoBTS 2100 is a new, low-power, small-formfactor IP-backhaul GSM BTS for medium coverage outdoor applications. ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: autoreconf.log Type: text/x-log Size: 1399 bytes Desc: autoreconf.log URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: configure.log Type: text/x-log Size: 7444 bytes Desc: configure.log URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: make.log Type: text/x-log Size: 2972 bytes Desc: make.log URL: From lynxis at fe80.eu Tue Jan 30 13:59:31 2018 From: lynxis at fe80.eu (Alexander Couzens) Date: Tue, 30 Jan 2018 14:59:31 +0100 Subject: Problem when building OsmoSGSN In-Reply-To: References: <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> Message-ID: <20180130145931.35de57a6@lazus.yip> On Tue, 30 Jan 2018 06:53:22 +0000 XINKE ZHANG wrote: > checking for LIBGTP... no > checking for LIBCARES... no You need to install libc-ares-dev and libc-ares2 (debian package) and compile libgtp (also an osmocom project). ./configure should hard fail, when it's missing those depdencies. I'll fix this bug later. Best, lynxis -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From pespin at sysmocom.de Tue Jan 30 14:38:49 2018 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Tue, 30 Jan 2018 15:38:49 +0100 Subject: Problem when building OsmoSGSN In-Reply-To: <20180130145931.35de57a6@lazus.yip> References: <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> <20180130145931.35de57a6@lazus.yip> Message-ID: <87672603-f95c-3b4e-1b70-b2072e42650d@sysmocom.de> On 30/01/18 14:59, Alexander Couzens wrote: > On Tue, 30 Jan 2018 06:53:22 +0000 > XINKE ZHANG wrote: > >> checking for LIBGTP... no >> checking for LIBCARES... no > You need to install libc-ares-dev and libc-ares2 (debian package) and > compile libgtp (also an osmocom project). > fyi, libgtp can be found and built/installed from osmo-ggsn.git. -- - Pau Espin Pedrol 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 From xinke.zhang at hotmail.com Wed Jan 31 01:01:25 2018 From: xinke.zhang at hotmail.com (XINKE ZHANG) Date: Wed, 31 Jan 2018 01:01:25 +0000 Subject: Problem when building OsmoSGSN In-Reply-To: <679ce868-a14e-45f9-eb0e-c4c9ab1b2f51@sysmocom.de> References: <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> , <679ce868-a14e-45f9-eb0e-c4c9ab1b2f51@sysmocom.de> Message-ID: Hi, I add the "make install" log. Pls check it. Thank you. Best Regards, Xinke ________________________________ From: Pau Espin Pedrol Sent: Tuesday, January 30, 2018 9:19 To: XINKE ZHANG; osmocom-net-gprs at lists.osmocom.org Subject: Re: Problem when building OsmoSGSN Hi, I think you forgot to attach the "make install" log, which is the interesting one in this case. -- - Pau Espin Pedrol http://www.sysmocom.de/ sysmocom - custom-tailored mobile telephony solutions www.sysmocom.de News: sysmocom introduces new sysmoBTS 2100. The sysmoBTS 2100 is a new, low-power, small-formfactor IP-backhaul GSM BTS for medium coverage outdoor applications. ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: make_install.log Type: text/x-log Size: 5794 bytes Desc: make_install.log URL: From pespin at sysmocom.de Wed Jan 31 10:14:39 2018 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Wed, 31 Jan 2018 11:14:39 +0100 Subject: Problem when building OsmoSGSN In-Reply-To: References: <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> <20180130145931.35de57a6@lazus.yip> Message-ID: <0c698df4-1056-3475-467b-59d18d4dd9a5@sysmocom.de> On 31/01/18 01:57, XINKE ZHANG wrote: > Hi, > > > I didn't find the *libgtp* project int the url of > "https://projects.osmocom.org/". Pls show me how to fetch the *libgtp* > codes. Thank you. As I said in my previous message, libgtp can be found, built and installed from osmo-ggsn.git. https://git.osmocom.org/osmo-ggsn/ -- - Pau Espin Pedrol 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 From xinke.zhang at hotmail.com Wed Jan 31 00:57:57 2018 From: xinke.zhang at hotmail.com (XINKE ZHANG) Date: Wed, 31 Jan 2018 00:57:57 +0000 Subject: Problem when building OsmoSGSN In-Reply-To: <20180130145931.35de57a6@lazus.yip> References: <1e4be474-5c2d-100f-ab6d-75babbf316da@sysmocom.de> , <20180130145931.35de57a6@lazus.yip> Message-ID: Hi, I didn't find the libgtp project int the url of "https://projects.osmocom.org/". Pls show me how to fetch the libgtp codes. Thank you. Best Regards, Xinke ________________________________ From: Alexander Couzens Sent: Tuesday, January 30, 2018 13:59 To: XINKE ZHANG Cc: Pau Espin Pedrol; osmocom-net-gprs at lists.osmocom.org Subject: Re: Problem when building OsmoSGSN On Tue, 30 Jan 2018 06:53:22 +0000 XINKE ZHANG wrote: > checking for LIBGTP... no > checking for LIBCARES... no You need to install libc-ares-dev and libc-ares2 (debian package) and compile libgtp (also an osmocom project). ./configure should hard fail, when it's missing those depdencies. I'll fix this bug later. Best, lynxis -------------- next part -------------- An HTML attachment was scrubbed... URL: From xinke.zhang at hotmail.com Mon Jan 29 00:56:16 2018 From: xinke.zhang at hotmail.com (XINKE ZHANG) Date: Mon, 29 Jan 2018 00:56:16 -0000 Subject: Problem when building OsmoSGSN Message-ID: Hi all, I built OsmoSGSN with the these following instructions. git clone git://git.osmocom.org/osmo-sgsn cd osmo-sgsn autoreconf -fi ./configure --enable-iu make -j5 make check make install sudo ldconfig And no error came out during building process, but no ?osmo-sgsn? executable was found. Pls help me. Thank you in advance. Best Regards, Xinke -------------- next part -------------- An HTML attachment was scrubbed... URL: