- nextepc - lists.osmocom.org

Re: Play RTP packets payload obtained from the mobile phone in a call service

by Harald Welte

On Fri, Feb 24, 2023 at 09:15:29AM +0100, Tomcsanyi, Domonkos wrote: > AFAIR Wireshark cannot play our RTP streams because it has a very limited set of codecs, mostly focusing on regular VoIP audio. it can play GSM. Our patches for AMR codec support unfortunately were refused even after everyone assumed the patents had expired and hence no IPR issues were known anymore. We'd still love to get AMR codec support in - especailly since wireshark wouldn't even contain the codec itself but just link to a system-installed libopencore-amrnb which probably every distribution ships these days. -- - Harald Welte <laforge(a)osmocom.org> https://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

9 months, 2 weeks

1
0
0 0

closing the nextecpc/open5gs mailing list

by Harald Welte

Dear subscribers of nextepc(a)lists.osmocom.org, after discussions with Sukchan, this mailing list will be officially closed. It was mainly useful during the days when there was no github "discussions" forum yet. But since that feature was introduced (and Sukchan enabled it for open5gs), the posts on this list have declined steadily, with the last post being more than a year ago. The list archives will of course stay available, but posting will be disabled. Please direct any future questions / discussions regarding open5gs to the github discussions at https://github.com/open5gs/open5gs/discussions. So long, and thanks for all the fish [tm]. Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 year, 9 months

1
0
0 0

enroll----系统警告

by support_noreply

1 year, 12 months

1
0
0 0

Open5gs computer configuration requirements

by Sun

Hi all    I'm new here and I wan to konw the computer configuration requirements of Open5gs. Thanks, Sun

3 years, 2 months

1
0
0 0

NB-IoT support

by Giovanni Rigazzi

Hi All, I read a previous thread on adding NB-IoT support and wanted to know if there is any update on this topic. We are very interested in contributing to the development. In fact, we have a working NB-IoT testbed (commercial UE, eNB and EPC) and we can share pcap traces. Let me know! Best Regards, Giovanni

3 years, 6 months

4
6
0 0

Regarding GNU Affero General Public License (GNU AGPLv3) Next EPC (nas_message.py) nas encoder and decoder script

by Raghav Vishwakarma

Hi NextEPC Team, I need some information regarding the GNU Affero General Public License (GNU AGPLv3) used by nextEPC. I want to use the Next EPC (nas_message.py) nas encoder and decoder script for commercial purpose. So we can use it for free, if not please let me know what is licensing agreement. Some help of information here will be very useful. Regards Raghav

3 years, 7 months

2
2
0 0

Regarding GNU Affero General Public License (GNU AGPLv3) Next EPC (nas_message.py) nas encoder and decoder script

by Raghav Vishwakarma

Hi NextEPC Team, I need some information regarding the GNU Affero General Public License (GNU AGPLv3) used by nextEPC. I want to use the Next EPC (nas_message.py) nas encoder and decoder script for commercial purpose. So we can use it for free, if not please let me know what is licensing agreement. Some help of information here will be very useful. Regards Raghav

3 years, 7 months

1
0
0 0

Multiple PLMN

by david＠ispsupplies.com

Is there a procedure for authenticating multiple PLMN codes on the same HSS? David

3 years, 7 months

1
0
0 0

Bridged APN

by david＠ispsupplies.com

Does anyone have any experience with a bridged APN on Open5GS? David

3 years, 8 months

2
5
0 0

Connect OCS to PCRF

by Abiola Ganiyu

Hi Everyone, I would like to know if anyone has been able to connect an OCS to open5gs PCRF. I know OCS talks to the PCRF using the Sy interface and the Gy interface to connect to the PCEF Lastly, how do I define these interfaces? Regards,

3 years, 8 months

2
2
0 0

Reject message

by david＠ispsupplies.com

Does anyone know why I am getting this reject reason for network entry on a UE? 03/17 16:56:55.026: [mme] DEBUG: [EMM] Authentication request (../src/mme/nas-path.c:180) 03/17 16:56:55.026: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:181) 03/17 16:56:55.026: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.026: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.026: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.189: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.189: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.189: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.189: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: [EMM] Authentication response (../src/mme/emm-sm.c:512) 03/17 16:56:55.189: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:513) 03/17 16:56:55.189: [emm] DEBUG: emm_state_authentication(): EXIT (../src/mme/emm-sm.c:488) 03/17 16:56:55.189: [emm] DEBUG: emm_state_security_mode(): ENTRY (../src/mme/emm-sm.c:649) 03/17 16:56:55.189: [mme] DEBUG: [EMM] Security mode command (../src/mme/nas-path.c:207) 03/17 16:56:55.189: [mme] DEBUG: IMSI[311980000033212] (../src/mme/nas-path.c:208) 03/17 16:56:55.190: [emm] DEBUG: Replayed UE SEC[LEN:2 EEA:0xe0 EIA:0xe0 UEA:0x0 UIA:0x0 GEA:0x0] (../src/mme/emm-build.c:287) 03/17 16:56:55.190: [emm] DEBUG: Selected[Integrity:0x1 Encrypt:0x0] (../src/mme/emm-build.c:289) 03/17 16:56:55.190: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.190: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.190: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.229: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.230: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.230: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.230: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.230: [mme] DEBUG: mme_state_operational(): MME_EVT_EMM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.230: [emm] DEBUG: emm_state_security_mode(): MME_EVT_EMM_MESSAGE (../src/mme/emm-sm.c:649) 03/17 16:56:55.230: [emm] DEBUG: [EMM] Security mode complete (../src/mme/emm-sm.c:676) 03/17 16:56:55.230: [emm] DEBUG: IMSI[311980000033212] (../src/mme/emm-sm.c:677) 03/17 16:56:55.230: [mme] DEBUG: [MME] Update-Location-Request (../src/mme/mme-fd-path.c:444) 03/17 16:56:55.231: [emm] DEBUG: emm_state_security_mode(): EXIT (../src/mme/emm-sm.c:649) 03/17 16:56:55.231: [emm] DEBUG: emm_state_initial_context_setup(): ENTRY (../src/mme/emm-sm.c:817) 03/17 16:56:55.234: [mme] DEBUG: [MME] Update-Location-Answer (../src/mme/mme-fd-path.c:610) 03/17 16:56:55.234: [mme] DEBUG: Result Code: 2001 (../src/mme/mme-fd-path.c:651) 03/17 16:56:55.234: [mme] DEBUG: From 'hss.localdomain' (../src/mme/mme-fd-path.c:680) 03/17 16:56:55.234: [mme] DEBUG: ('localdomain') (../src/mme/mme-fd-path.c:693) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_S6A_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.234: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.234: [esm] DEBUG: esm_state_initial(): ENTRY (../src/mme/esm-sm.c:38) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): ENTRY (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [mme] INFO: Added a session. Number of sessions is now 1 (../src/mme/mme-context.c:79) 03/17 16:56:55.234: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.234: [esm] DEBUG: [ESM] PDN Connectivity request (../src/mme/esm-sm.c:82) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:84) 03/17 16:56:55.234: [esm] DEBUG: EIT(ESM information transfer)[1] (../src/mme/esm-handler.c:59) 03/17 16:56:55.234: [esm] DEBUG: [ESM] ESM information request (../src/mme/esm-build.c:75) 03/17 16:56:55.234: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-build.c:77) 03/17 16:56:55.235: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.235: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.235: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.269: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.270: [mme] DEBUG: [MME] Uplink NAS transport (../src/mme/s1ap-handler.c:330) 03/17 16:56:55.270: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:347) 03/17 16:56:55.270: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:354) 03/17 16:56:55.270: [mme] DEBUG: mme_state_operational(): MME_EVT_ESM_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.270: [mme] DEBUG: mme_bearer_find_or_add_by_message() [PTI:8, EBI:0] (../src/mme/mme-context.c:2847) 03/17 16:56:55.270: [esm] DEBUG: esm_state_inactive(): MME_EVT_ESM_MESSAGE (../src/mme/esm-sm.c:61) 03/17 16:56:55.270: [esm] DEBUG: [ESM] ESM information response (../src/mme/esm-sm.c:93) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] EBI[5] (../src/mme/esm-sm.c:95) 03/17 16:56:55.270: [mme] DEBUG: [EMM] Attach reject (../src/mme/nas-path.c:134) 03/17 16:56:55.270: [mme] DEBUG: IMSI[311980000033212] Cause[8] (../src/mme/nas-path.c:135) 03/17 16:56:55.270: [esm] DEBUG: [ESM] PDN connectivity reject (../src/mme/esm-build.c:39) 03/17 16:56:55.270: [esm] DEBUG: IMSI[311980000033212] PTI[8] Cause[27] (../src/mme/esm-build.c:41) 03/17 16:56:55.271: [mme] DEBUG: [MME] DownlinkNASTransport (../src/mme/s1ap-build.c:186) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-build.c:231) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.271: [esm] DEBUG: esm_state_inactive(): EXIT (../src/mme/esm-sm.c:61) 03/17 16:56:55.271: [esm] DEBUG: esm_state_exception(): ENTRY (../src/mme/esm-sm.c:345) 03/17 16:56:55.271: [mme] DEBUG: [MME] UE Context release command (../src/mme/s1ap-path.c:285) 03/17 16:56:55.271: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-path.c:287) 03/17 16:56:55.271: [mme] DEBUG: Group[3] Cause[0] Action[3] Delay[0] (../src/mme/s1ap-path.c:306) 03/17 16:56:55.271: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-path.c:79) 03/17 16:56:55.275: [mme] DEBUG: mme_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/mme-sm.c:129) 03/17 16:56:55.275: [mme] DEBUG: s1ap_state_operational(): MME_EVT_S1AP_MESSAGE (../src/mme/s1ap-sm.c:60) 03/17 16:56:55.275: [mme] DEBUG: [MME] UE Context release complete (../src/mme/s1ap-handler.c:919) 03/17 16:56:55.276: [mme] DEBUG: IP[10.100.108.9] ENB_ID[67177119] (../src/mme/s1ap-handler.c:933) 03/17 16:56:55.276: [mme] DEBUG: ENB_UE_S1AP_ID[41] MME_UE_S1AP_ID[17] (../src/mme/s1ap-handler.c:950) 03/17 16:56:55.276: [mme] DEBUG: Action: UE context remove() (../src/mme/s1ap-handler.c:963) 03/17 16:56:55.276: [mme] INFO: Removed a UE. Number of UEs is now 0 (../src/mme/mme-context.c:63) 03/17 16:56:55.276: [emm] DEBUG: emm_state_initial_context_setup(): EXIT

3 years, 8 months

3
10
0 0

Fwd: Open5GS Traffic Accounting

by Romeu Medeiros

Hello all and @Sukchan Lee <acetcom(a)gmail.com>, I was thinking about one way to generate traffic accounting from the LTE users of the Open5GS. I'm rearching something using the iptables (in Linux), in this link we can check a way to generate some traffic account in the linux: https://catonmat.net/traffic-accounting-with-iptables I'm thinking about writing a code, where the PGW adds a new line in iptables with the IP/IPv6 address (TRAFFIC_ACCT_IN and TRAFFIC_ACCT_OUT) when a new session is added and remove the same line when the session is ended, with this the counter will restart, being able to use an external program to get this information about the traffic sent and received by a given user. The bad from this idea is that this code only will work correctly in a Linux box. Does anyone have any other suggestions? Thanks Romeu Medeiros

3 years, 9 months

4
7
0 0

PCRF

by david＠ispsupplies.com

Does anyone have any experience or knowledge on using Open5gs with an external MVNO? <http://www.ispsupplies.com/> David Peterson Senior Engineer 855-947-7776 ext. 9214 d 979-314-1305 c 419-706-7355 <https://www.ispsupplies.com/> https://www.ispsupplies.com <https://facebook.com/ispsupplies> <https://twitter.com/ispsupplies> <https://www.linkedin.com/company/isp-supplies/>

3 years, 9 months

2
1
0 0

Get all debug info possible

by Rafael Diniz

Hi all, Which cmd line should I use to get all the debug information possible from the EPC components? Thanks, Rafael Diniz

3 years, 9 months

3
5
0 0

Programmer needed

by david＠ispsupplies.com

I am looking for a programmer to integrate webhooks into the open5gs database. <http://www.ispsupplies.com/> David Peterson Senior Engineer 855-947-7776 ext. 9214 d 979-314-1305 c 419-706-7355 <https://www.ispsupplies.com/> https://www.ispsupplies.com <https://facebook.com/ispsupplies> <https://twitter.com/ispsupplies> <https://www.linkedin.com/company/isp-supplies/> <https://linkprotect.cudasvc.com/url?a=https://i.xink.io/Images/Get/N1644/p. jpg&c=E,1,ZrPTDE38thL9cON4IQDlhgWa90HqTLTcVKAvisogqwtefGFx-779ueyEMN5vmMGUA9 8j20izDtiw8e6BeMsUnQOeSHopvHu6uQ3SR9svdZSv1D8EzXOV-g,,&typo=1>

3 years, 9 months

1
0
0 0

Which repository to use for a 4G development

by Rafael Diniz

Hi all, Which repository should I look for to get the most stable NextEPC for a real-world LTE deploying? Thanks, Rafael

3 years, 10 months

4
15
0 0

Regarding available documents

by Murali Sb

Hi I'm using this project as a reference and it would be useful if i get any document on this. It'll be really helpful. Regards -- Murali.S

4 years

2
1
0 0

Regarding IP address assignment

by Murali Sb

Hi In my project, I'm using IP address as 55.55.0.25/16 in nextepc.conf My tunnel inet gets 55.55.0.25 , mask is 255.255.0.0 IP address for my route from the pool is 55.55.0.1. Why is this happening? I want my route to start from 55.55.0.26 and so on... how to do this? please help -- Murali.S

4 years, 1 month

3
3
0 0

Any major issues on master?

by Spencer Sevilla

Hi everyone, I admin a couple of small-scale networks, one with ~20 users and one with ~100. They are basic, data-only LTE networks, and do not provide any voice services, 2g fallback, or interconnect at all. One has two eNBs and the other has one. We currently use the OAI EPC, but are very interested in moving over to NextEPC for reasons of stability. I’ve tested NextEPC in our lab (with only two phones and an SDR) and it seems to work great. I’ve looked through the code, implemented a feature or two, and it is much much cleaner than OAI. I’ve also heard widely good reports of some other deployments. Anything I should know, or any major issues I should be aware of before I go ahead and deploy the current master branch? I don’t mind finding/fixing a couple of bugs and will certainly commit any fixes upstream, just more asking about any already known fundamental problems, features unimplemented, or reasons I should postpone a rollout. Thanks! Spencer

4 years, 1 month

2
1
0 0

Regarding configuration files.

by Murali Sb

Hi I have a question regarding conf files in nextEPC. I know for example, mme.conf is generated from mme.conf.in, so I've added few of my configuration settings in mme.conf.in and same is populated in mme.conf. I use the same YAML parser to read my new configurations. It's working. I've a problem now, How is nextEPC reading these parameters? and from where? I know I've to update a structure for this. But I don't know which structure. Anybody done this before? any help is really appreciated. Thanks Murali

4 years, 2 months

1
0
0 0

GDB help

by Murali Sb

Hi How to debug the nextepc code using GDB? If i try " gdb next-epcd ". I get an error message, its not an executable. Please advise. -- Murali.S

4 years, 2 months

2
1
0 0

Database functions

by Romeu Medeiros

Hello all and Sukchan, I'll try to use another database with nextepc. (PostgreSQL). Let me ask something, only the HSS need the database connection? Thanks Romeu Medeiros

4 years, 3 months

2
2
0 0

nextepc based LTE network @ CCCamp2019

by Harald Welte

Hi all, During the Chaos Communication Camp 2019 (an international hacker camp with about 5500 participants) last week, there is a tradition to operate Osmocom based 2G and more recently also 3G networks. This time I operated a nextepc based 4G/LTE network next to the camp 2G/3G networks. In order to share one subscriber database, I have implemented osmo_dia2gsup, which can translate the S6a/S6d diameter into Osmocom GSUP protocol, so nextepc can be used without nextepc-hssd but with osmo-hlr instead. The network was operating six Ericsson RBS6402 in Band 7 (2600 MHz). Some more details can be found at Regarding the nextepc side: * 2439 uniqua IMSIs were seen ** 147 unique IMSIs of CCC SIM cards (26242) ** 2292 non-CCC IMSIs ** 75 unique MCC-MNC tuples ** 34 unique MCCs ** The usual suspects (Europe + North America), but also... *** Malaysia, Indonesia, Australia, New Zealand, South Africa * 560 Attach accept (CCC SIM cards) * 46590 Attach reject (commercial operator SIM cards) * 629 PDN context (APN) activations * 235 handovers between cells (X2) * 64 crashes + restarts of nextepc-mme * 9 crashes + restarts of nextepc-pgw * 0 crashes + restarts of nextepc-sgw * 10 crashes + restarts of nextepc-pcrf In general, it worked quite nicely, and I have to congratulate Sukchan on his work at nextepc. I investigated some of the crashes, reported them to the issue tracker and attempted to fix some of them on-site. The actual codebase that was running can be found at https://github.com/laf0rge/nextepc/commits/laforge/cccamp19 >From my experience with operating such a "large" nextepc network for the first time, I have the following overall feedback, which basically boils down to three major areas: == the use of assert() == ASSERT should never be triggered by anything that is received from another network entity. So if a eNB sends an unknown S1AP-ID, or if a SGW sends an unknown TEID, or if the NAS MAC validation fails, or a EMM message cannot be decoded - all of those must be handled gracefully without terminating the program. This 'fail fast' way of programming can be done when writing code in C++ (exceptions that are caught) or in erlang (one process per message, crashing that one doesn't bring the entire MME down). I've tried my best to review all ogs_assert() in the MME and came up with the following patch: https://github.com/laf0rge/nextepc/commit/3b528af8fd51c85769123338eb57a4635… which requires https://github.com/laf0rge/ogslib/commit/dc36ccbb080038306666931bdc97f6204f… which introduces ogs_expect() and ogs_expect_or_return() macros that can be used in many places instead of ogs_assert(). It would also be possible to use this kind of 'fail fast' approach in C programs, but then one would have to use longjmp() from the 'assert', and you would have to use some kind of hierarchical memory allocator so that in the 'exception handler' you can release any dynamic allocations that were made before. == the lack of introspection == When you operate a network, it is vital to have some visibility. For the MME you want to inspect how many subscribers are currently attached, where they are attached (TAC), whether they currently have an UE Context (and at which eNB), which TMSI/GUTI was allocated, etc. Likewise, for both SGW and PGW you want to see which PDN contexts exist, from which peer IP adresses, which APN was used, what IP addresses have been allocated, etc. In the Osmocom world, we implement this introspection in two ways: * by means of the VTY interface (for the human user) * by means of the CTRL interface (for other programs) If I hadn't been busy with debugging various other issues, I would have actually attempted to add a basic VTY interface to nextepc-mmed. For sure there may be better ways to expose this state (ideally with the same piece of code providing access to both human users as well as external programs), but I'm not aware of any nice C language implementation in FOSS that one could use right away. == logging without context == When looking at log file output, it is very important that this log file output always carry sufficient context. IF there are many subscribers acting in parallel, you need to know which subscriber / pdn context / ... a given log message relates to, otherwise the log message is rather useless. For example, if you get [mme] DEBUG: [MME] Authentication-Information-Answer (mme-fd-path.c:211) then even at DEBUG level you have no indication what so ever for which particular subscriber this AIA was received. I would normally expect that the UE is resolved from the DIAMETER session-id, and then the UEs identity (IMSI) can be printed. I also find it suboptimal that log lines often span multiple lines, which means you cannot simply 'grep' for something, as you always need to check some lines before and/or after. But I guess conrary to the lack of context, this is a matter of teste and one can have different opinions about it. I'll try to contribute as much as I can regarding bug fixes and enhancements. Thanks again for all the great work so far! 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 years, 3 months

3
5
0 0

What's next plan?

by Sukchan Lee

Dear Community People. Some people are asking about next plan. I didn't answer correctly because I don't know how much time I have or how much my abilities are possible. But now I think I need to start sharing what I want to do. I don't know if it's possible to this, but I'd just like to prepare to move 5G Core. But there are a lots of things before that and I don't know exactly when this project is going on. Anyway, in order to share the code used by 4G/5G, I will separate the repository as follows: Repo1 : libogscore - apt install libogscore-dev Repo2 : libogs-asn1c - common : apt install libogs-asn1c-common-dev - s1ap : apt install libogs-asn1c-s1ap-dev Repo3 : libogs-freeDiameter - apt install libogs-freeDiameter-dev - libfdcore - libfdproto Repo4 : libogslib - apt install libogslib-dev - s1ap : apt install libogs-s1ap-dev DEPEND libogs-asn1c-common-dev libogs-asn1c-s1ap - nas : apt install libogs-nas-dev - gtp : apt install libogs-gtp-dev - diameter : apt install libogs-diameter-dev DEPEND libogs-freeDiameter-dev - app : apt install libogs-app-dev Repo5 : ogs-mme - apt install ogs-mme ; DEPEND libogs-app-dev libogs-s1ap-dev libogs-nas-dev libogs-gtp-dev libogs-diameter-dev Repo6 : ogs-hss - apt install ogs-hss ; DEPEND libogs-app-dev libogs-diameter-dev Repo7 : ogs-pcrf - apt install ogs-pcrf ; DEPEND libogs-app-dev libogs-diameter-dev Repo8 : ogs-sgw - apt install ogs-sgw ; DEPEND libogs-app-dev libogs-gtp-dev Repo9 : ogs-pgw - apt install ogs-pgw ; DEPEND libogs-app-dev libogs-gtp-dev libogs-diameter-dev Repo10 : ogs-epc ; if all stuff are available, current nextepc repo is changed to ogs-dev for managing issues list This approach is similar to the osmocom project. In fact, I'm not sure whether this is good or not. However, osmocom manages 2G/3G like this and I believe that experience. So I'll do it from now. P.S. Please, feel free to give any idea the above plan. Expecially, 'NAMING'. ^^; Thanks a lot! Best Regards, Sukchan

4 years, 3 months

2
2
0 0

nextepc vs nextepc

by Mathieu

Hi everyone, Does someone know the difference between these two projects: https://github.com/open5gs/nextepc https://github.com/nextepc/nextepc They seem to share some code, but the second one seems to be owned by a US company, and the code as not been updated for months. (only 14 commits in the repo) There are nextepc packages in the universe ubuntu repo too now, but I don't know which version it is. Any idea ? Which project should be used ? Thanks, Mathieu

4 years, 3 months

2
2
0 0

PGW without root or changing /dev/net/tun permissions

by Harald Welte

Hi Sukchan and friends, the installation instructions recommend changing the permissions of /dev/net/tun, which can be dangerous as it gives permissions to potentially many other processes. There are several better alternatives to this: 1) give CAP_NET_ADMIN permission to the pgw binary: Simply execute "setcap cap_net_admin=ep /usr/local/bin/nextepc-pgwd" and then you can run the process as 'nextepc' user, like the other processes. The sad part about this is that nextepc-pgwd has now the power to reconfigure anything about linux netwowrking. The best approach would be to drop those capabiligies after creating/configuring the tun devices using prctl(PR_CAPBSET_DROP, CAP_NET_ADMIN) - this way it is ensured that after start-up, no capabilities survive, and even if somebody manages to get code execution in the PGW, it is not a privilege escalation. 2) create the tun devices *before* starting the P-GW, and then start the PGW as non-root. We offer this method in OsmoGGSN, see Section 8.3 of http://ftp.osmocom.org/docs/latest/osmoggsn-usermanual.pdf This can even be done with systemd now. I suggest to first change the documentation to recomend the setcap approach, and then later to adopt privilege dropping or another approach. 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 years, 3 months

2
1
0 0

ignore initial APN

by Mathieu

Hi, I'm trying to setup nextepc to provide service for multiple ISPs with the same core network. Is there a way to ignore the APN configured in the UE, and rather use the one configured with the webui ? On the same topic, is it possible to restrict a UE to the apn configured with the webui ? Thanks, Best regards,

4 years, 3 months

5
7
0 0

CS Fallback in NextEPC

by Sukchan Lee

Dear Osmocom & NextEPC Community, Today I've added CS Fallback and released NextEPC v0.5.0 So, I'd just like to test this part with Osmocom project, but it seems to be a difficult task. The reason is why I have little knowledge about 2G/3G. Nevertheless, I will try to do it BTW, I don't know if there is anyone who wants to integrate this big thing. Even though I'm not sure if this will help, but let me introduce the configuration of the NextEPC. To use SGsAP, change the mme.conf as follows: # # <sgsap> # # o Single MSC/VLR # sgsap: # addr: 127.0.0.2 # plmn_id: # mcc: 001 # mnc: 01 # tac: 4130 # lac: 43690 # # o Multiple MSC/VLR # sgsap: # - addr: 127.0.0.2 # plmn_id: # mcc: 001 # mnc: 01 # tac: 4131 # lac: 43692 # - addr # - 127.0.0.3 # - fe80::2%lo0 # plmn_id: # mcc: 001 # mnc: 01 # tac: 4132 # lac: 43692 # - name: msc.open5gs.org # plmn_id: # mcc: 001 # mnc: 01 # tac: 4133 # lac: 43693 # FYI, I also attach the pcap that I run with nextepc simulator as below. $ ./tests/testcsfb mo-idle-test : SUCCESS mt-idle-test : SUCCESS mo-active-test : SUCCESS mt-active-test : SUCCESS All tests passed. Feel free to raise any questions about this things. Best Regards, Sukchan

4 years, 4 months

5
13
0 0

Nextepc died in some MT-Fallback

by Romeu Medeiros

Hello, In some situations the Nextepc is crashing when try the MT-CSFB. Here is the log: 07/17 17:48:53.270: [mme] WARNING: EMM_CAUSE : IMSI Unknown in HSS (mme-sm.c:339) 07/17 17:48:54.480: [mme] WARNING: ERROR DIAMETER Result Code(5001) (mme-fd-path.c:298) 07/17 17:48:54.480: [mme] WARNING: EMM_CAUSE : IMSI Unknown in HSS (mme-sm.c:339) 07/17 17:48:55.611: [s1ap] ERROR: Failed to encode S1AP-PDU[-1] (s1ap-encoder.c:41) 07/17 17:48:55.611: [mme] ERROR: s1ap_encode_pdu() failed (s1ap-build.c:555) 07/17 17:48:55.611: [mme] FATAL: s1ap_send_initial_context_setup_request: Assertion `rv == OGS_OK && s1apbuf' failed. (s1ap-path.c:252) File Logging: '//var/log/nextepc/mme.log' Configuration: '//etc/nextepc/mme.conf' 07/17 17:48:58.215: [mme] INFO: MME initialize...done (mme.c:28) NextEPC daemon v0.5.0.26-b642c 07/17 17:48:58.215: [gtp] INFO: gtp_server() [10.3.15.38]:2123 (gtp-path.c:36) 07/17 17:48:58.215: [gtp] INFO: gtp_server() [2804:828:3:15:b010:37ff:fe46:4521]:2123 (gtp-path.c:36) 07/17 17:48:58.215: [gtp] INFO: gtp_server() [2804:828:3:208:48a0:1cff:fed9:b7c9]:2123 (gtp-path.c:36) 07/17 17:48:58.215: [gtp] INFO: gtp_connect() [127.0.0.2]:2123 (gtp-path.c:61) 07/17 17:48:58.216: [mme] INFO: sgsap client() [127.0.0.1]:29118 (sgsap-lkpath.c:47) 07/17 17:48:58.216: [mme] INFO: s1ap_server() [10.3.15.38]:36412 (s1ap-lkpath.c:44) 07/17 17:48:58.217: [fd] INFO: CONNECTED TO 'hss.localdomain' (TCP,soc#14): (fd-logger.c:113) 07/17 17:48:58.802: [mme] INFO: eNB-S1 accepted[10.12.0.3]:36412 in s1_path module (s1ap-lkpath.c:70) In the attached file is the pcap from this moment, I will try to find what is happened. Thanks Romeu Medeiros

4 years, 4 months

3
7
0 0

SMS

by Romeu Medeiros

Hello guys and @Sukchan Lee <acetcom(a)gmail.com> I tested with sucess the send and receive SMS in new version of NextEPC running together with OSMO-MSC/HLR (SGS). Thanks Romeu Medeiros

4 years, 4 months

3
10
0 0

SNOW-3G / ZUC implementation under FOSS license?

by Paul Sutton

Hi Harald, The srsLTE implementation is taken from the ETSI specs simulation program listings: http://cryptome.org/uea2-uia2/etsi_sage_06_09_06.pdf and http://cryptome.org/uea2-uia2/snow_3g_spec.pdf https://www.etsi.org/intellectual-property-rights#mytoc3 and https://www.etsi.org/images/files/IPR/etsi-ipr-policy.pdf outline the copyright licensing details for software incorporated in ETSI standards however I have not taken legal advice on compatibility of this license with AGPLv3. >From a quick review, it looks like the CryptoMobile and NextEPC versions have taken the same approach. It would be good as you say to have a "clean copyright" implementation - perhaps this is something we could help with. Best regards, Paul > Hi! > > I'm now at a point where I would like to add SNOW-3G (EIA1/EEA1) support for > NAS integrity protection and ciphering to my upcoming TTCN-3 testsuite for the MME. > > However, it seems there is no real FOSS implementation of the SNOW-3G algoritm > around? All I could find was: > > * https://github.com/mitshell/CryptoMobile with unclear source of the code, > without a copyright statement or license annotation > > * https://github.com/rcatolino/libressl-snow3g/blob/master/crypto/snow3g/main… > without a copyright statement or license annotation > > * https://github.com/Jadson27101/SNOW_3G in go, > without a copyright statement or license annotation > > * https://github.com/KsirbJ/SNOW-3G > without a copyright statement or license annotation > > * https://github.com/open5gs/nextepc/blob/master/src/mme/snow-3g.c > without a copyright statement or license annotation. Looks rather similar > to CryptoMobile. Possible just copy+pasted from ETSI reference implementation? > > * https://github.com/srsLTE/srsLTE/blob/master/lib/src/common/snow_3g.cc > also contains no coypright statement or license, but might be construed > to be AGPLv3 like all of srsLTE. However, it states it is "adapted" > from ETSI/SAGE specifications. Does that mean it is an independent > implementation of the algorithm by just reading the specs, or does it > contain actual ETSI-copyrighted code? > > It's also odd that the 3GPP specs (35.215 / 35.216, with usual copyright statement) > don't contain any actual information but all just point to the ETSI SAGE specification > which can be found (at the very least) here: > https://www.gsma.com/aboutus/wp-content/uploads/2014/12/uea2uia2d1v21.pdf > and interestingly doesn't contain any copyright statement whatsoever. > > This discussion is not about any potentially 'essential patents' that may or may > not apply in some jurisdictions on the algorithm itself. I'm currently only interested > in a "clean copyright" implementation of any of the EIA/EEA implementations used > on the LTE NAS layer. > > I'd appreciate any useful comments. Thanks! > > -- > - Harald Welte <laforge at gnumonks.org <https://lists.osmocom.org/mailman/listinfo/openbsc>> http://laforge.gnumonks.org/ > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) -- ________________________________________________________________ Paul Sutton Ph.D. Software Radio Systems (SRS) http://www.softwareradiosystems.com paul(a)softwareradiosystems.com PGP Key ID: 3B4A5292 Fingerprint: B0AC 19C9 B228 A6EB 86E1 82B2 90C7 EC95 3B4A 5292 ________________________________________________________________

4 years, 4 months

2
1
0 0

osmocom CN domain and keyword

by Peter Liu

(It's very urgent, please transfer this email to your CEO. Thanks) We are a Network Service Company which is the domain name registration center in Shanghai, China. On July 16, 2019, we received an application from Kaiqian Ltd requested "osmocom" as their internet keyword and China (CN) domain names (osmocom.cn, osmocom.com.cn, osmocom.net.cn, osmocom.org.cn). But after checking it, we find this name conflict with your company name or trademark. In order to deal with this matter better, it's necessary to send email to you and confirm whether your company have connection with this Chinese company or not? Best Regards *************************************** Peter Liu | Service & Operations Manager China Registry (Head Office) | 6012, Xingdi Building, No. 1698 Yishan Road, Shanghai 201103, China Tel: +86-02164193517 | Fax: +86-02164198327 | Mob: +86-13816428671 Email: peter(a)chinaregistry.org Web: www.chinaregistry.org *************************************** This email contains privileged and confidential information intended for the addressee only. If you are not the intended recipient, please destroy this email and inform the sender immediately. We appreciate you respecting the confidentiality of this information by not disclosing or using the information in this email.

4 years, 4 months

1
0
0 0

OCS interface/NB-IoT support

by Daniel Feferman

Hi, First of all congrats for the work, I've been testing over this week and it has been really nice to stress it. I have two questions: 1- It would be really nice to see an OCS integration, is it possible to connect the PCRF and PGW with it? I believe this would be done by a 127.0.0.X IP, right? Is this something simple to implement? It would be nice to check the support to OCS 2- I believe you are developing NB-IoT support as part of your roadmap, what are the main challenges you see in this task? Is it just programming the messages of NB-IoT? Or is it something else? I can try to help you with this task. Best regards, Daniel <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Livre de vírus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

4 years, 4 months

2
2
0 0

Re: CS Fallback in NextEPC

by Romeu Medeiros

Hello Sukchan, I already go out from the lab today, but Monday I will made this test that you ask for. Have a great day there. Romeu Medeiros Em sáb, 13 de jul de 2019 às 21:01, Sukchan Lee <acetcom(a)gmail.com> escreveu: > Hi Romeu, > > I'm really appreciate testing CSFB even though I have never been testing > this feature in the lab. > > BTW, I have one question. If we want to remove Security-Related IE in UE > Context Modification Request, > I think NextEPC should not derive kENB in Extended Service Request handler. > > Nevertheless, I've merged your pull request since it is properly worked at > first. ^^; > > If your lab is available, could you test one more by removing the > following code? > > In src/mme/emm-handler.c > 586 if (SECURITY_CONTEXT_IS_VALID(mme_ue)) { > 587 mme_kdf_enb(mme_ue->kasme, mme_ue->ul_count.i32, mme_ue->kenb); > 588 mme_kdf_nh(mme_ue->kasme, mme_ue->kenb, mme_ue->nh); > 589 mme_ue->nhcc = 1; > 590 } > > Just test it. If my expectation is true, I will fix all other things. > > Thank you for your GREAT job! > > Best regards, > Sukchan > > > > > > On Sun, Jul 14, 2019 at 8:04 AM Romeu Medeiros <medeiros(a)medeiros.eng.br> > wrote: > >> Hello Sukchan, >> >> Now after remove this everything run correctly. >> >> [image: image.png] >> >> I will made the change more beatiful and pull the modification to the git >> to you aprove. >> >> Thanks >> >> Romeu Medeiros >> >> On Sat, Jul 13, 2019 at 6:50 PM Romeu Medeiros <medeiros(a)medeiros.eng.br> >> wrote: >> >>> I found this in the 3GPP documentations [1]: >>> >>> [image: image.png] >>> >>> I will change the code to send only the CSFallback indicator in this >>> case to see if can solve the problem. >>> >>> Thanks >>> >>> Romeu Medeiros >>> >>> 1. >>> https://www.etsi.org/deliver/etsi_ts/136400_136499/136413/09.10.00_60/ts_13… >>> >>> On Sat, Jul 13, 2019 at 6:35 PM Romeu Medeiros <medeiros(a)medeiros.eng.br> >>> wrote: >>> >>>> Hello Sukchan and friends. >>>> >>>> I'm trying to use the CSFB in test lab, and every time that nextepc >>>> send the UEContextModificationRequest, the UE respond with an >>>> UEContextModificationFaliure [ Protocol-cause=semantic-error ]. >>>> >>>> [image: image.png] >>>> >>>> I'm looking why I'm getting this. Someone have any idea? >>>> >>>> Thanks >>>> >>>> Romeu Medeiros >>>> >>>> On Thu, Jul 11, 2019 at 12:15 PM Sukchan Lee <acetcom(a)gmail.com> wrote: >>>> >>>>> Dear Osmocom & NextEPC Community, >>>>> >>>>> Today I've added CS Fallback and released NextEPC v0.5.0 >>>>> >>>>> So, I'd just like to test this part with Osmocom project, but it seems >>>>> to be a difficult task. The reason is why I have little knowledge about >>>>> 2G/3G. Nevertheless, I will try to do it >>>>> >>>>> BTW, I don't know if there is anyone who wants to integrate this big >>>>> thing. >>>>> Even though I'm not sure if this will help, but let me introduce the >>>>> configuration of the NextEPC. >>>>> >>>>> To use SGsAP, change the mme.conf as follows: >>>>> >>>>> # >>>>> # <sgsap> >>>>> # >>>>> # o Single MSC/VLR >>>>> # sgsap: >>>>> # addr: 127.0.0.2 >>>>> # plmn_id: >>>>> # mcc: 001 >>>>> # mnc: 01 >>>>> # tac: 4130 >>>>> # lac: 43690 >>>>> # >>>>> # o Multiple MSC/VLR >>>>> # sgsap: >>>>> # - addr: 127.0.0.2 >>>>> # plmn_id: >>>>> # mcc: 001 >>>>> # mnc: 01 >>>>> # tac: 4131 >>>>> # lac: 43692 >>>>> # - addr >>>>> # - 127.0.0.3 >>>>> # - fe80::2%lo0 >>>>> # plmn_id: >>>>> # mcc: 001 >>>>> # mnc: 01 >>>>> # tac: 4132 >>>>> # lac: 43692 >>>>> # - name: msc.open5gs.org >>>>> # plmn_id: >>>>> # mcc: 001 >>>>> # mnc: 01 >>>>> # tac: 4133 >>>>> # lac: 43693 >>>>> # >>>>> >>>>> FYI, I also attach the pcap that I run with nextepc simulator as below. >>>>> >>>>> $ ./tests/testcsfb >>>>> mo-idle-test : SUCCESS >>>>> mt-idle-test : SUCCESS >>>>> mo-active-test : SUCCESS >>>>> mt-active-test : SUCCESS >>>>> All tests passed. >>>>> >>>>> Feel free to raise any questions about this things. >>>>> >>>>> Best Regards, >>>>> Sukchan >>>>> >>>>>

4 years, 4 months

2
10
0 0

Question on Uplink 'sequence count' handling in MME

by Harald Welte

Hi Sukchan and list, I'm currently reading the MME code and I'm having some trouble understanding the handling of the uplink counter for NAS security. I only see mme_ue->ul_count.i32 ever being set to '0' when a new security context is used. But I don't see it ever being incremented? I only see ul_count.sqn incremented, but then the nas_mac_calculate() always gets ul_count.i32 passed as input. So I'm somehow not understanding how the MAC can ever verify on any uplink message beyond/after the first one which establishes a new security context. What am I missing? Thanks for your insight! -- - 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 years, 4 months

2
1
0 0

SNOW-3G / ZUC implementation under FOSS license?

by Harald Welte

Hi! I'm now at a point where I would like to add SNOW-3G (EIA1/EEA1) support for NAS integrity protection and ciphering to my upcoming TTCN-3 testsuite for the MME. However, it seems there is no real FOSS implementation of the SNOW-3G algoritm around? All I could find was: * https://github.com/mitshell/CryptoMobile with unclear source of the code, without a copyright statement or license annotation * https://github.com/rcatolino/libressl-snow3g/blob/master/crypto/snow3g/main… without a copyright statement or license annotation * https://github.com/Jadson27101/SNOW_3G in go, without a copyright statement or license annotation * https://github.com/KsirbJ/SNOW-3G without a copyright statement or license annotation * https://github.com/open5gs/nextepc/blob/master/src/mme/snow-3g.c without a copyright statement or license annotation. Looks rather similar to CryptoMobile. Possible just copy+pasted from ETSI reference implementation? * https://github.com/srsLTE/srsLTE/blob/master/lib/src/common/snow_3g.cc also contains no coypright statement or license, but might be construed to be AGPLv3 like all of srsLTE. However, it states it is "adapted" from ETSI/SAGE specifications. Does that mean it is an independent implementation of the algorithm by just reading the specs, or does it contain actual ETSI-copyrighted code? It's also odd that the 3GPP specs (35.215 / 35.216, with usual copyright statement) don't contain any actual information but all just point to the ETSI SAGE specification which can be found (at the very least) here: https://www.gsma.com/aboutus/wp-content/uploads/2014/12/uea2uia2d1v21.pdf and interestingly doesn't contain any copyright statement whatsoever. This discussion is not about any potentially 'essential patents' that may or may not apply in some jurisdictions on the algorithm itself. I'm currently only interested in a "clean copyright" implementation of any of the EIA/EEA implementations used on the LTE NAS layer. I'd appreciate any useful comments. Thanks! -- - 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 years, 4 months

2
1
0 0

Easy way to add subscribers to hss without node.js / web UI

by Harald Welte

Hi Sukchan and list, I was wondering if there was a way to create subscribers in the HSS from a script or from the command line and avoid/bypass all the node.js and npm "nightmare" (I know, it's a matter of taste, but to me it is). Particularly for automated tests, I wouldnt't want to write scripts against a web gui to create subscribers. Also, for most operators (small or big), I guess they want to import a bulk CSV (or other format) file with key data. If there was a way to add subscribers from a script / command line, I could e.g. writea script to import the CSV for the sysmoUSIM/SJS1 easily. Thanks for any assistance. -- - 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 years, 4 months

2
2
0 0

Wy does the MME need a mongodb database?

by Harald Welte

Hi Sukchan and othres, I'm wondering why the MME itself is currently requiring a mongodb database? What is it used for? I'm a bit confused, I thought mongodb was only used by the HSS for subscriber storage. However, it seems that (at least with current nextepc), the MME also needs mongodb. I cannot immediately find any code that uses it? 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 years, 5 months

2
1
0 0

Security research

by Holtmanns, Silke (Nokia - FI/Espoo)

Hi, I'm part of security research and we are mainly interested in the core network part and not on the UE part. What we want to do is have a PGW which has some the EPC "machinery" behind to get a TEID and have MME, HSS, SGW initialized and some not real UEs i.e. the fake UEs would sit in or next to the eNB. In the end we are interested in plugging this EPC next to a real one with a real S8 connection. We do not need real internet connection for the "fake UE" and user plane is also not that important for us. So how can we get a "fake UE" into the eNB, so that is makes all the protocol runs for data communication set-up. Any hints? Greetings silke

4 years, 5 months

3
2
0 0

License for our test suites

by Harald Welte

Dear Osmocom community, during recent years we have developed a quite extensive set of test suites for virtually all interfaces on all protocol levels of our 2G stack, and recently even extended at least with some 3G IuCS coverage. Those test suites are considerably valuable for testing any kind of implementation of 2G / 3G network elements, even beyond Osmocom. I'm a bit worried that they might be used to test proprietary implementations, which would bring no value to growing FOSS in mobile communications. Whether we license the test suites under GPL or AGPL doesn't actually change much here: Imagine "EvilCorp" developing a BSC, using our test suites against it. They neither distribute the test suite, nor do they provide "access over a network" to it, an hence they could keep any modifications/extensions/derivatives private without having to contribute those back. I think this is problematic. We develop those test suites because we care about having well-tested FOSS in cellular communications, whether Osmocom or other FOSS projects. I certainly don't want to spend my spare time, or invest sysmocom resources towards improving the test coverage of any non-FOSS implementations. If such users are out there, they should at the very least contribute to the development effort in one way (code) or another (funding). For 2G/3G, I think this discussion is quite theoretical, as there is unlikely anyone else implementing those old technologies in proprietary systems - Osmocom is probably typically the latest player in the market to do so. However, as I'm currently working on a first set of TTCN3 tests for testing a LTE MME (initially attacing to S1 and SGs), I'm wondering if we should continue to release related code under traditional copyleft licenses. One idea would be to have a license that permits the use of the test suites to test only FOSS software. In theory, that would mean that all projects we care about (such as currently srsLTE, nextepc, OAI EPC, ...) could use the test suites to test their software. On the other hand, if some vendor of proprietary MME/EPC software would want to [legally] use the tests, they would need to obtain a different (paid) license to the test suite. Of course they could simply ignore the license and we'd have little chance to learn about it - but I would argue most proper companies typically would obtain a license if they used some software they knew they had to license. This is a very double-edged sword. Drafting such a new license would cause license proliferation, which is always bad. It also raises quesetions of license compatibility with e.g. some of our common existing 'library' code that would need to be investigated. Finally, it also means that we'd no longer be writing "free software" nor "open source", as the respective relevant definitions always require "non discriminatory use for any purpose", which would no longer be the case here. This is currently an early stage brainstorming. Now is the right point in time to talk about this, before we release any LTE/EPC related tests. Let me know if you have any thoughts to share. While I'm cross-posting this to openbsc@ and nextepc@ lists, pleaes follow-up-to openbsc(a)lists.osmocom.org, as that's the main Osmocom mailing list and we don't have any specifically only for the test suites. -- - 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 years, 5 months

1
0
0 0

RE: Somebody tried this (or parts of it)

by Holtmanns, Silke (Nokia - FI/Espoo)

Maybe it goes through this time. Seems it did not make it the first time... From: Holtmanns, Silke (Nokia - FI/Espoo) Sent: Friday, July 5, 2019 12:55 PM To: nextepc(a)lists.osmocom.org Cc: Kalliola, Aapo (Nokia - FI/Espoo) <aapo.kalliola(a)nokia-bell-labs.com> Subject: Somebody tried this (or parts of it) Hi, are mainly interested in the core network part and not on the UE part. What we want to do is have a PGW which has some the EPC "machinery" behind to get a TEID and have MME, HSS, SGW initialized and some not real UEs i.e. the fake UEs would sit in or next to the eNB. We do not need real internet connection for the "fake UE" and user plane is also not that important for us. Any hints? Greetings silke

4 years, 5 months

1
0
0 0

PCAP file from a CSFB

by Romeu Medeiros

Hello to all. Someone have a pcap from a CSFB to send to me? I will have some freetime and i want implement this in the nextepc. Thanks Romeu Medeiros

4 years, 6 months

3
4
0 0

Configuration of SGSAP

by Sukchan Lee

Hi, I need to implement SGsAP before I go to a CSFB. I have one question about the configuration. I gonna create a configuration of mme.conf as shown below. mme: sgsap: addr: 127.0.0.2 tai: plmn_id: mcc: 001 mnc: 01 tac: 4130 lai: plmn_id: mcc: 001 mnc: 01 lac: 43690 However, if both TAC and LAC are alway the same PLMN_ID, the configuration can be changed as follows: mme: sgsap: addr: 127.0.0.2 plmn_id: mcc: 001 mnc: 01 tac: 4130 lac: 43690 I don't have enough knowledge about 2G/3G, so I hesitate in this part for a while. Perhaps, I will do it the first way. Do you have anybody to help? P.S. You can see the full configuration in this like: https://github.com/open5gs/nextepc/blob/master/support/config/nextepc.conf.… Thanks a lot!

4 years, 6 months

2
1
0 0

S1 handover failure

by Redes Comunicaciones Móviles

Hello! I am testing the handover functionality on S1 with 2 eNB of the OpenAirInterface implementation, both transmitting on the same frequency and with the same TAC. The way I do it is ass follows: - I start the EPC. - I start one of the eNBs. - I connect the UE to the network. - I start the second eNB. - I move the UE away from the first eNB as I move it closer to the second eNB. By following these steps, instead of the handover taking place, what happens is that the second eNB stops, showing an error, and the UE remains connected to the first eNB. Here is the error of the second eNB: [image: image] <https://user-images.githubusercontent.com/50883711/58153355-165e3e80-7c6f-1…> And in the interface S1 there is no message related to the handover. I wonder if I am doing something wrong or if this functionality is not available with the OpenAirInterface eNBs or something like that. I attach my configuration files and the log of the mme. I am not sure if the reason for this failure is the NextEPC core or the eNBs, because I have tried the same EPC configuration with srsENBs and the messages in the S1 interface are the same. Kind regards, Salvador. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Libre de virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

4 years, 6 months

1
0
0 0

Two APN/PGW per UI

by Liubinskii Pavel

Hello Guys and thanks a lot for a great product. Have a question which I couldn't find in documentation. Is it possible to use two separate PGWs with NextEPC? Each PGW represents a different network (i.e one for Internet, another for some kind of LAN). I also would like to add two different APNs per UI in this scenario. I have already done a singe PGW configuration with default 'internet' APN, but stuck a bit with the second PGW. I will highly appreciate for any thoughts, advise or configuration examples. Thanks in advance. BR, Pavel

4 years, 6 months

2
3
0 0

stats

by Mathieu

Hi all, Is there a way in nextepc to have statistics, for example, which enodeB/CPE are connected, througput ? I checked in the database but can't find anything. Thanks, Mathieu

4 years, 8 months

2
1
0 0

VoLTE and SMS support

by Rafael Diniz

Hi all, Is there a working IMS I can use with NextEPC to have VoLTE and, if possible, also SMS support? Thanks, Rafael Diniz

4 years, 8 months

3
7
0 0

How is IP address assigned

by Suman Bhunia

Hello! We just started using NextEPC at our lab and came across a few problems. I was wondering if anyone could provide me some guideline on how the EPC assigned IP address to the UEs. Any document or even pointing me to the correct section of code in the GitHub will be helpful. Thank you for your kind help. Thanks, Suman Bhunia Postdoctoral scholar Texas A&M University

4 years, 8 months

2
1
0 0

Test of new nextepc list

by Harald Welte

please ignore -- - 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 years, 8 months

1
0
0 0

2023

2022

2021

2020

2019

nextepc