osmocom-net-gprs November 2018

osmocom-net-gprs@lists.osmocom.org

1 participants
3 discussions

RFC: unit tests for kernel GTP module
by Harald Welte 31 Dec '25

31 Dec '25

Dear GTP-interested folks, I would love to somehow get towards some degree of unit testing (or even "continuous integration") for teh kernel GTP code. We currently have the original code in the kernel, we had some recent small fixes and now are getting more patches into place. With relatively few active users out there (and probably none of them in production yet), it's particularly easy to introduce regressions while working on the code. Also, having tested new code even against a test set with limited covrage could help to get more confidence in new patches and thus get them merged sooner. Using tools like sgsnemu of OpenGGSN and the command line tools included in libgtpnl, it should be possibel to cook up some scripts for testing. Even the most basic set of tests would be an improvement over what we have now. One could also think about pcap replay to test with hand-crafted or real-world packets from other GTP implementations. As much as I'd like to put something like this into place myself, I don't think I will be able to work much on this in the near future. The GTP module at this point is a pure hobby and contrary to some years ago while I started it, I don't have any contract work in the GTP area at this point, so other projects currently unfortunately get more attention. So in case somebody among the GTP-interested parties (Travelping, OAI, ...) would want to do something in terms of testing, I'd be more than happy if somebody would step ahead. Otherwise it's all just vapourware going to end up on my ever-growing TODO list :/ Also, if netdev folks have some ideas/pointers about possible frameworks/tools for this kind of testing [it must exist for at least some other kernel networking code?]: Please let me know. I'd be interested to have a look if there's something that can be used as a basis (starting network namespaces, sending/transmitting packets, test case startup/teardown, ...) My "old school" approach would have been to start one or multiple user-mode-linux kernels (those that are to be tested), and then have scripts that set up a gtp socket and gtp tunnels via the libgtp command line tools, and throw packets at that. But I'm sure there must be quite powerful frameworks for that kind of testing in the 21st century? How do other tunneling implementations handle this? 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)

4 5

Can you tell me how to compile and install libgtpnl?
by luo 06 Dec '18

06 Dec '18

hello,Please forgive my childishness,Can you tell me how to compile and install libgtpnl?thanks I saw that you wrote the libgtpnl project on github, but there is no readme above.

2 1

[BUG][OSMO-PCU][OSMO-SGSN] GPRS and EGPRS attach procedure is not working with Kirin Modem phones
by Bipin Jaiswal 06 Dec '18

06 Dec '18

Hi, We are using Honor 7X mobile phone with Huawei Kirin modem and observed that GPRS and EGPRS attach is not working with Huawei Kirin Modem phones. There is no issue observed from OSMO-PCU. it seems either Huawei Kirin modem issue or OSMO-SGSN issue. Please check below analysis for this issue. 1- UE send attach request with IMSI and invalid MCC and MNC to SGSN. 2- SGSN send Identity Request with IMEI to UE. 3- UE responded Identity Response with IMEI to SGSN. 4- SGSN sends ATTACH ACCEPT message to SGSN with new PMTSI but UE is not responding ATTACH COMPLETE message to SGSN and resend ATTACH REQUEST message to SGSN. 5- SO SGSN re transmit ATTACH ACCEPT message to UE and after max number of re transmission , SGSN is release UE MM context. It seems that UE is not accepting ATTACH ACCEPT message. We also observed that Huawei Kirin UE is sending wrong LLC data to SGSN. UE had set more bit in RLC LME header and send invalid LLC data with 0x2B. So OSMO-PCU had forward this data to SGSN because more bit is set and SGSN is complaining LLC error for this LLC data. Please look into this issue or let us know if we have fix for this issue. Thanks, Bipin Jaiswal

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

osmocom-net-gprs November 2018