OpenBSC September 2021

openbsc@lists.osmocom.org

7 participants
22 discussions

On the use of 'decmatch' in TTCN-3
by Harald Welte 27 Jan '26

27 Jan '26

Hi, I know that TTCN-3 is still new to a lot of you, but we are writing tons of integration testing against the various osmocom programs in it. It is quite amazing technology, and I would like to ask you to bear with me reading this mail :) Pau was stating the question earlier today on not finding an example on how to use decmatch. Indeed, it took me some months to find that gem in the TTCN-3 world. It solves the problem that you often have during test of layered protocol stacks: you have separate encoders/decoders for each protocol layer, and now you want to match on some of the *inner* payload. So normally, you have some kind of header definition + a binary (octetstring) payload. This happens in RSL with the L3_INFO IE, and just the same on BSSAP/DTAP where again the L3 message (for example call control) is encapsulated inside one information element. Now you have multiple options of addressing the problem: a) hand-written calls to the decoder function b) write na 'emulation' for the entire protocol layer c) use decmatch. a) would look like this (pseudo-code): var octetstring l3oct; var RSL_Message rsl RSL.receive(tr_RSL_DATA_REQ(g_chan_nr, ?, ?)) -> value rsl { var PDU_ML3_MS_NW l3 := dec_PDU_ML3_MS_NW(rsl.payload); if (match(l3, some_template)) { ... do something } ... } Which uses the built-in pattern-matching on the RSL port to match any message that matches the tr_RSL_DATA_REQ template, and stores the resulting RSL message in a variable. It then uses an explicit call to the decoder function of the L3 message, and then uses regular conditional expressions for further matching on that inner L3 payload. This is more or less how you would write in C, python or any other quite imperative programming languages. It's very verbose, time consuming and un-abstract/elegant. TTCN-3 has many declarative aspects to it. Code like the above is a waste of your time :) b) would mean that you implement some test component that handles the RSL messages on its bottom side test port, and the L3 messages on its top side test port. That is a possible way, and if you need a lot of state/logic of RSL, it maeks sense. But what if you really simply want to have a match? Then it would be a lot of effort and a large detour. c) decmatch to the rescue! You can write RSL.receive(tr_RSL_DATA_REQ(g_chan_nr, ?, decmatch tr_RRM_RR_STATUS)) which means: * do a receive on the RSL test port, and match on an incoming RSL message that matches the tr_RSL_DATA_REQ template, with channel number specified, link_id any (?), *and* if the octetstring payload, if decoded, matches the template tr_RRM_RR_STATUS ! This is *extremely* powerful and expressive. It allows you to condense complex, parametric template matching over multiple proocol layers. It would in the end match RSL DATA REQUEST, only if they contained a [valid] encoded RR STATUS. See https://gerrit.osmocom.org/6229 for the actual test case I used for the above examples. Please also note that I never had to even write the function name of the decoder (dec_PDU_ML3_MS_NW), but TTCN-3 *automatically* figures out which decoder function it must call in order to decode from the binary octetstring. Happy (TTCN-3) hacking + Osmocom bugfixing, 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)

3 3

osmo-gsm-manuals in project repos: I see no .pdf
by Neels Hofmeyr 08 Jan '26

08 Jan '26

Hi Oliver, so I merged the stuff to add the manuals to the individual git repositories, since you said that it works. But when I do --enable-manuals I don't see any PDF files generated. Also a manual 'make pdf' says "nothing to be done". (I probably should have tried it before merging after all) So what am I doing wrong? Alternatively, can you fix it please? ~N

3 3

Pysim error: SW match failed
by Martin Nagy 16 Aug '25

16 Aug '25

Hi all, After buying a super Sim Kit (16 in 1) from China, I tried the reader (green PCB inside a blue transparent plastic case with a blue LED) and SIM (identified as a fakesupersim) with pysim tool. However i am getting the following error: /pySim-prog.py -n 26C3 -c 49 -x 262 -y 42 -z 1234 -j 1 -t auto Insert card now (or CTRL-C to cancel) Autodetected card type fakemagicsim Generated card parameters : > Name : 26C3 > SMSP : e1ffffffffffffffffffffffff058100945555ffffffffffff000000 > ICCID : 8949262427518313026 > MCC/MNC : 262/42 > IMSI : 262422461512085 > Ki : 7b74741a1ee14337ec23f9ab92a13648 > OPC : ccd867d60797d8d45354a51b3ef568ff Programming ... Traceback (most recent call last): File "./pySim-prog.py", line 530, in <module> card.program(cp) File "/home/nadicek/pysim/pysim/pySim/cards.py", line 231, in program self._scc.update_binary('6f30', hplmn + 'ff' * (tl-3)) File "/home/nadicek/pysim/pysim/pySim/commands.py", line 53, in update_binary return self._tp.send_apdu_checksw(pdu) File "/home/nadicek/pysim/pysim/pySim/transport/__init__.py", line 87, in send_apdu_checksw raise RuntimeError("SW match failed ! Expected %s and got %s." % (sw.lower(), rv[1])) RuntimeError: SW match failed ! Expected 9000 and got 9804. I checked mailing lists and haven’t found anybody who had similar problem with pysim. Also I have tried forcing different models of SIM, but nothing is working. Obviously I can remove this check from the script file (__init__.py in /pySim/transport), however somebody had a reason to put such condition there. I would like to ask if it is safe to remove that line of code and the purpose of that line of code. Thanks a lot and best regards Martin

3 3

Re: Help with sccp library
by mosbah abdelkader 07 Jul '25

07 Jul '25

> I don't understand. This callback will be called with data you need to write > to the network. In case of MTP Level3 you will need to wrap that around the > msgb you got. I means: is the interaction with mtp3 layer implemented (is sending sccp data by mtp3 implemented by the library?)? Also, what about the reception of data from mtp3 layer. is that implemented in the sccp lib. I am asking these questions because I see the code of mtp3 in the lib but no significant call is present in the sccp part of the lib. Thank you for your help.

4 3

dynamic traffic channels
by Neels Hofmeyr 20 May '25

20 May '25

On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote: > [translated from german] > is it certain that we switch a channel to PDCH only when > gprs mode != none? A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we send a PDCH ACT message. We send a PDCH ACT message - during init (CHANNEL OML's state changed to enabled -> send PDCH ACT), - and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH. So the question is, when we receive a channel release ack, could that be the PDCH release and we switch PDCH right back on by accident? No, because we only receive a chan rel ack when the *TCH/F* is being released. That is because the PDCH release is initiated "internally" from the PDCH DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches on, which existed before dyn PDCH: if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) { LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n", gsm_lchan_name(lchan)); return 0; } In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but not in the rsl_rx_dyn_pdch(). This is analogous to the ip.access way -- the ip.access nanobts replies to a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel release ack. Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH for clarity? (But we shouldn't actually send a release ack, to stay compatible.) Even though it works as-is, we should indeed add another flag check: - We do check the flags that no ACT/DEACT is already pending; - And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE; - But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE. This should never happen, but it would make sense to ensure that. ~Neels

3 5

Problem while running NIB on Open Cellular Base sation
by Brackley Casinga 31 Jan '24

31 Jan '24

Hi, My name is Brackley Cassinga Form DRC, we run a community network called pamoja net where we offer gsm services using osmocom open source software and OC Base station. Recently I have tried to install another base station as the same installed but I could not find any resource guiding through all the steps to take to run NIB on a base station. I'm currently running Ubuntu and I will appreciate if you could guide me on the installation of BSC,hlr,MSC , in order to run a basic gsm network. Thank you. Regards -- *Ir Brackley heshima Casinga **Pacifique* *CEO and Founder of kwanzatechnologie* KwanzaTechnologies ,GlobalElectronics +243977265291 | +243977265291 | Pcassinga(a)gmail.com/ brackley(a)ensemblepourladifference.org www.kwantechnologies.jimdosite.com <http://www.kwantechnologies.com/> | Skype: Brackley cassinga <https://webapp.wisestamp.com/#> Av Semliki N 43

2 1

Cellspot v2 LTE femtocells available free of charge
by Harald Welte 26 Sep '21

26 Sep '21

Dear Osmocom community, some years ago sysmocom acquired a batch of > 30 T-Mobile Cellspot v2 femtocells, with the vague idea to "root" them and use them as a low-cost eNodeB with open5gs. They also seem to support HSPA in addition to LTE, with 8 simultaneous users on either of the two. Unfortunately we never found the time to really dig into them, and we primarily work with other more high-end eNodeBs these days. So we're giving them away for free. All you have to cover is the cost of shipping. Some information on those devices can be found at https://www.reddit.com/r/tmobile/comments/7ii5jm/4g_lte_cellspot_v2_virtual… - they are Alcatel-Lucent 9961 v2, based on a Qualcomm Femtocell chipset. Note: This really only makes sense for people who want to spend significant time to try to get them "owned" or "rooted" in order to use them with your own EPC rather than the one of T-Mobile. In case you're interested in one or multiple units: Please send an e-mail to sales(a)sysmocom.de stating the quantity as well as your shipping address. We will then get a shipping rete and send you a quote. Happy hacking, 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)

1 0

Osmo-BSC UL Power Loop
by Keith 26 Sep '21

26 Sep '21

Hi All, I am implementing uplink power control for the Ericsson RBS. I started with a vty command to force an ms power update on a timeslot and then I implemented a very crude loop and that "works". Next, I imported power_control.c from osmo-bts into osmo-bsc. This is where I began to wonder if this code is better moved some place where it can be shared by both projects. - There would be some small modifications necessary, I think. I also wonder if it is the right thing to do to integrate this bsc-side UL power control into the current (m|b)s-power control? Would it make sense to add a further "mode" there? ms-power-control mode dyn-bsc For example? Obviously one does not want both a BSC and BTS managing a power loop. Or maybe only allow the BSC side power loop to run with bts-type that is known to not do UL power control? There are some other issues I'm still unsure about, but this is enough by way of moving towards a patch fit for code review. Thanks! Keith.

4 5

Announcement of "OsmoDevCall" on September 24, 2021
by Harald Welte 23 Sep '21

23 Sep '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at September 24, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "ISO 7816 smart card interface FPGA softcore" by tnt 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - 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 0

Unable to program SIMs with pysim to use with srsRAN
by Andrea Valori 16 Sep '21

16 Sep '21

Hi everyone, I have a srsRAN installation, which works flawlessly with some Sysmocom SIMs I programmed some months ago using Pysim. Those SIMs still work perfectly, even if in the meantime I updated the srs installation. I am trying to program some other SIMs (bought in the same batch as the older ones which always worked), but failing miserably. Since the older programmed SIMs still work, I am focusing my attention on the SIM programming step, although I am fully aware that the issue might be on the enodeB side. For this reason I will post on both mailing lists. Apologise to the several people that may receive this twice being members of both communities. Many thanks in advance to everyone who might be able to help. Below are the steps I took and the results I got. *Programmed SIM with command (I believe this are exactly the parameters already programmed, doing this just for confirmation):* ./pySim-prog.py -p 0 -n Open5GS -i 901700000044987 -s 8988211000000449879 -k 833218D615B110706DB6E7FD69222BE9 -o D0C41ED07DFE2F9BB0DB083E5E347F5E -a 29728642 -x 001 -y 01 *Got the answer:* Using PC/SC reader interface Ready for Programming: Insert card now (or CTRL-C to cancel) Autodetected card type: sysmoISIM-SJA2 Generated card parameters : > Name : Open5GS > SMSP : e1ffffffffffffffffffffffff0581005155f5ffffffffffff000000 > ICCID : 8988211000000449879 > MCC/MNC : 001/01 > IMSI : 901700000044987 > Ki : 833218D615B110706DB6E7FD69222BE9 > OPC : D0C41ED07DFE2F9BB0DB083E5E347F5E > ACC : None > ADM1(hex): 3239373238363432 > OPMODE : None Programming ... Warning: Programming of the ICCID is not implemented for this type of card. Programming successful: Remove card from reader *Imported data into the HSS file:* # .csv to store UE's information in HSS # Kept in the following format: "Name,Auth,IMSI,Key,OP_Type,OP/OPc,AMF,SQN,QCI,IP_alloc" # # Name: Human readable name to help distinguish UE's. Ignored by the HSS # Auth: Authentication algorithm used by the UE. Valid algorithms are XOR # (xor) and MILENAGE (mil) # IMSI: UE's IMSI value # Key: UE's key, where other keys are derived from. Stored in hexadecimal # OP_Type: Operator's code type, either OP or OPc # OP/OPc: Operator Code/Cyphered Operator Code, stored in hexadecimal # AMF: Authentication management field, stored in hexadecimal # SQN: UE's Sequence number for freshness of the authentication # QCI: QoS Class Identifier for the UE's default bearer. # IP_alloc: IP allocation stratagy for the SPGW. # With 'dynamic' the SPGW will automatically allocate IPs # With a valid IPv4 (e.g. '172.16.0.2') the UE will have a statically assigned IP. # # Note: Lines starting by '#' are ignored and will be overwritten ue2,mil,001010123456780,00112233445566778899aabbccddeeff,opc,63bfa50ee6523365ff14c1f45f88737d,8000,000000001234,7,172.16.0.2 ue1,mil,901700000044980,82e9053a1882085ff2c020359938dae9,opc,bfd5771aaf4f6728e9bc6ef2c2533bdb,8437,00000000919a,7,172.16.0.3 ue3,mil,901700000044981,aa32df28e6f1ec860ed4b6d485d24c31,opc,d72f9533d860aea319d5dac95c6b5037,8438,0000000020cb,7,172.16.0.4 ue4,mil,901700000044982,8ca8891528cb25f046b13829283b0571,opc,c307259c2acc10253b68100bb249a117,8438,000000003407,7,172.16.0.5 ue5,mil,901700000044983,38d8c889d60b4cc9e6d5f00a0a1167cc,opc,166df27f5c79f2a1a2cb8349ec2f802a,8438,000000002ba3,7,172.16.0.6 ue6,mil,901700000044984,66c36c2b333b4d080e6913f51a7e9385,opc,17a44e6b270f1748ca7282d2b3da6899,8438,00000000386a,7,172.16.0.7 ue7,mil,901700000044985,e23b82b102293695c68931cd42a9e272,opc,c7a91401ec96a8a3284ec5b776da4b39,8438,000000002e16,7,172.16.0.8 ue8,mil,901700000044986,de98f28abd8caf114c5e968380a10153,opc,a72233bbc4e9860c60fdc85c30927716,9000,000000000000,9,172.16.0.9 *ue9,mil,901700000044987,833218d615b110706db6e7fd69222be9,opc,d0c41ed07dfe2f9bb0db083e5e347f5e,9000,0000000000c6,9,172.16.0.10* ue10,mil,901700000044988,df7720883094f1724e5f2158bc779bf3,opc,0ba0e79d6e79849beb40cd4badb803e5,9000,000000000000,9,172.16.0.11 *Started SRS (enb and epc), SIM in UE* *SRSepc stdout:* S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b S1 Setup Request - MCC:001, MNC:01 S1 Setup Request - TAC 7, B-PLMN 0xf110 S1 Setup Request - Paging DRX v128 Sending S1 Setup Response Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST Received Initial UE message -- Attach Request Attach request -- IMSI: 901700000044987 Attach request -- eNB-UE S1AP Id: 1 Attach request -- Attach type: 2 Attach Request -- UE Network Capabilities EEA: 11100000 Attach Request -- UE Network Capabilities EIA: 01100000 Attach Request -- MS Network Capabilities Present: true PDN Connectivity Request -- EPS Bearer Identity requested: 0 PDN Connectivity Request -- Procedure Transaction Id: 1 PDN Connectivity Request -- ESM Information Transfer requested: true Downlink NAS: Sending Authentication Request UL NAS: Authentication Failure MAC code failure Received UE Context Release Request. MME-UE S1AP Id 1 *epc.log (I have noticed that is two hours behind the computer time, which is probably GMT, not sure if it matters and is indication of timing used wrongly somewhere...):* 07:28:11.784226 [EPC ] [I] Built in Release mode using commit 89f16eed2 on branch master. --- Software Radio Systems EPC log --- 07:28:11.784232 [EPC ] [I] Using binary srsepc with arguments: 07:28:11.784294 [HSS ] [I] Opened DB file: /home/enodeb/.config/srsran/user_db.csv 07:28:11.784326 [HSS ] [D] Added user from DB, IMSI: 001010123456780 07:28:11.784327 [HSS ] [D] User Key : 0000: 00 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff 07:28:11.784328 [HSS ] [D] User OPc : 0000: 63 bf a5 0e e6 52 33 65 ff 14 c1 f4 5f 88 73 7d 07:28:11.784329 [HSS ] [D] AMF : 0000: 80 00 07:28:11.784330 [HSS ] [D] SQN : 0000: 00 00 00 00 12 34 07:28:11.784330 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784336 [HSS ] [I] static ip addr 172.16.0.2 07:28:11.784347 [HSS ] [D] Added user from DB, IMSI: 901700000044980 07:28:11.784348 [HSS ] [D] User Key : 0000: 82 e9 05 3a 18 82 08 5f f2 c0 20 35 99 38 da e9 07:28:11.784348 [HSS ] [D] User OPc : 0000: bf d5 77 1a af 4f 67 28 e9 bc 6e f2 c2 53 3b db 07:28:11.784349 [HSS ] [D] AMF : 0000: 84 37 07:28:11.784349 [HSS ] [D] SQN : 0000: 00 00 00 00 91 9a 07:28:11.784349 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784350 [HSS ] [I] static ip addr 172.16.0.3 07:28:11.784361 [HSS ] [D] Added user from DB, IMSI: 901700000044981 07:28:11.784361 [HSS ] [D] User Key : 0000: aa 32 df 28 e6 f1 ec 86 0e d4 b6 d4 85 d2 4c 31 07:28:11.784361 [HSS ] [D] User OPc : 0000: d7 2f 95 33 d8 60 ae a3 19 d5 da c9 5c 6b 50 37 07:28:11.784362 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784362 [HSS ] [D] SQN : 0000: 00 00 00 00 20 cb 07:28:11.784362 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784363 [HSS ] [I] static ip addr 172.16.0.4 07:28:11.784373 [HSS ] [D] Added user from DB, IMSI: 901700000044982 07:28:11.784373 [HSS ] [D] User Key : 0000: 8c a8 89 15 28 cb 25 f0 46 b1 38 29 28 3b 05 71 07:28:11.784374 [HSS ] [D] User OPc : 0000: c3 07 25 9c 2a cc 10 25 3b 68 10 0b b2 49 a1 17 07:28:11.784374 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784374 [HSS ] [D] SQN : 0000: 00 00 00 00 34 07 07:28:11.784375 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784375 [HSS ] [I] static ip addr 172.16.0.5 07:28:11.784386 [HSS ] [D] Added user from DB, IMSI: 901700000044983 07:28:11.784387 [HSS ] [D] User Key : 0000: 38 d8 c8 89 d6 0b 4c c9 e6 d5 f0 0a 0a 11 67 cc 07:28:11.784387 [HSS ] [D] User OPc : 0000: 16 6d f2 7f 5c 79 f2 a1 a2 cb 83 49 ec 2f 80 2a 07:28:11.784387 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784387 [HSS ] [D] SQN : 0000: 00 00 00 00 2b a3 07:28:11.784388 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784389 [HSS ] [I] static ip addr 172.16.0.6 07:28:11.784399 [HSS ] [D] Added user from DB, IMSI: 901700000044984 07:28:11.784399 [HSS ] [D] User Key : 0000: 66 c3 6c 2b 33 3b 4d 08 0e 69 13 f5 1a 7e 93 85 07:28:11.784399 [HSS ] [D] User OPc : 0000: 17 a4 4e 6b 27 0f 17 48 ca 72 82 d2 b3 da 68 99 07:28:11.784400 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784400 [HSS ] [D] SQN : 0000: 00 00 00 00 38 6a 07:28:11.784401 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784401 [HSS ] [I] static ip addr 172.16.0.7 07:28:11.784412 [HSS ] [D] Added user from DB, IMSI: 901700000044985 07:28:11.784412 [HSS ] [D] User Key : 0000: e2 3b 82 b1 02 29 36 95 c6 89 31 cd 42 a9 e2 72 07:28:11.784412 [HSS ] [D] User OPc : 0000: c7 a9 14 01 ec 96 a8 a3 28 4e c5 b7 76 da 4b 39 07:28:11.784413 [HSS ] [D] AMF : 0000: 84 38 07:28:11.784413 [HSS ] [D] SQN : 0000: 00 00 00 00 2e 16 07:28:11.784414 [HSS ] [D] Default Bearer QCI: 7 07:28:11.784414 [HSS ] [I] static ip addr 172.16.0.8 07:28:11.784425 [HSS ] [D] Added user from DB, IMSI: 901700000044986 07:28:11.784425 [HSS ] [D] User Key : 0000: de 98 f2 8a bd 8c af 11 4c 5e 96 83 80 a1 01 53 07:28:11.784426 [HSS ] [D] User OPc : 0000: a7 22 33 bb c4 e9 86 0c 60 fd c8 5c 30 92 77 16 07:28:11.784426 [HSS ] [D] AMF : 0000: 90 00 07:28:11.784426 [HSS ] [D] SQN : 0000: 00 00 00 00 00 00 07:28:11.784427 [HSS ] [D] Default Bearer QCI: 9 07:28:11.784427 [HSS ] [I] static ip addr 172.16.0.9 07:28:11.784438 [HSS ] [D] Added user from DB, IMSI: 901700000044987 07:28:11.784438 [HSS ] [D] User Key : 0000: 83 32 18 d6 15 b1 10 70 6d b6 e7 fd 69 22 2b e9 07:28:11.784438 [HSS ] [D] User OPc : 0000: d0 c4 1e d0 7d fe 2f 9b b0 db 08 3e 5e 34 7f 5e 07:28:11.784439 [HSS ] [D] AMF : 0000: 90 00 07:28:11.784439 [HSS ] [D] SQN : 0000: 00 00 00 00 00 e7 07:28:11.784439 [HSS ] [D] Default Bearer QCI: 9 07:28:11.784440 [HSS ] [I] static ip addr 172.16.0.10 07:28:11.784452 [HSS ] [D] Added user from DB, IMSI: 901700000044988 07:28:11.784454 [HSS ] [D] User Key : 0000: df 77 20 88 30 94 f1 72 4e 5f 21 58 bc 77 9b f3 07:28:11.784455 [HSS ] [D] User OPc : 0000: 0b a0 e7 9d 6e 79 84 9b eb 40 cd 4b ad b8 03 e5 07:28:11.784455 [HSS ] [D] AMF : 0000: 90 00 07:28:11.784457 [HSS ] [D] SQN : 0000: 00 00 00 00 00 00 07:28:11.784457 [HSS ] [D] Default Bearer QCI: 9 07:28:11.784458 [HSS ] [I] static ip addr 172.16.0.11 07:28:11.784465 [HSS ] [I] HSS Initialized. DB file /home/enodeb/.config/srsran/user_db.csv, MCC: 61441, MNC: 65281 07:28:11.784494 [S1AP ] [I] S1-MME Initializing 07:28:11.784543 [S1AP ] [I] S1AP Initialized 07:28:11.784544 [MME GTPC] [I] Initializing MME S11 interface. 07:28:11.784555 [MME GTPC] [I] MME S11 Initialized 07:28:11.784561 [MME GTPC] [I] MME GTP-C Initialized 07:28:11.784564 [S1AP ] [I] MME Initialized. MCC: 0xf001, MNC: 0xff01 07:28:11.784595 [GTPU ] [I] TUN file descriptor = 6 07:28:11.794434 [GTPU ] [I] Initialized SGi interface 07:28:11.794458 [GTPU ] [I] S1-U socket = 7 07:28:11.794463 [GTPU ] [I] S1-U IP = 127.0.1.100, Port = 2152 07:28:11.794463 [GTPU ] [I] Initialized S1-U interface 07:28:11.794464 [GTPU ] [I] SPGW GTP-U Initialized. 07:28:11.794770 [SPGW GTPC] [I] Initializing SPGW S11 interface. 07:28:11.794819 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.2 is reserved for imsi 001010123456780, not adding to pool 07:28:11.794826 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.3 is reserved for imsi 901700000044980, not adding to pool 07:28:11.794830 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.4 is reserved for imsi 901700000044981, not adding to pool 07:28:11.794833 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.5 is reserved for imsi 901700000044982, not adding to pool 07:28:11.794835 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.6 is reserved for imsi 901700000044983, not adding to pool 07:28:11.794836 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.7 is reserved for imsi 901700000044984, not adding to pool 07:28:11.794839 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.8 is reserved for imsi 901700000044985, not adding to pool 07:28:11.794841 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.9 is reserved for imsi 901700000044986, not adding to pool 07:28:11.794844 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.10 is reserved for imsi 901700000044987, not adding to pool 07:28:11.794845 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.11 is reserved for imsi 901700000044988, not adding to pool 07:28:11.794848 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.12 is added to pool 07:28:11.794850 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.13 is added to pool 07:28:11.794852 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.14 is added to pool 07:28:11.794853 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.15 is added to pool 07:28:11.794855 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.16 is added to pool 07:28:11.794857 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.17 is added to pool 07:28:11.794859 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.18 is added to pool 07:28:11.794860 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.19 is added to pool 07:28:11.794862 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.20 is added to pool 07:28:11.794864 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.21 is added to pool 07:28:11.794866 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.22 is added to pool 07:28:11.794867 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.23 is added to pool 07:28:11.794869 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.24 is added to pool 07:28:11.794871 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.25 is added to pool 07:28:11.794874 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.26 is added to pool 07:28:11.794875 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.27 is added to pool 07:28:11.794877 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.28 is added to pool 07:28:11.794878 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.29 is added to pool 07:28:11.794880 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.30 is added to pool 07:28:11.794881 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.31 is added to pool 07:28:11.794882 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.32 is added to pool 07:28:11.794884 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.33 is added to pool 07:28:11.794885 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.34 is added to pool 07:28:11.794887 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.35 is added to pool 07:28:11.794888 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.36 is added to pool 07:28:11.794890 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.37 is added to pool 07:28:11.794891 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.38 is added to pool 07:28:11.794893 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.39 is added to pool 07:28:11.794894 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.40 is added to pool 07:28:11.794895 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.41 is added to pool 07:28:11.794897 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.42 is added to pool 07:28:11.794898 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.43 is added to pool 07:28:11.794900 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.44 is added to pool 07:28:11.794901 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.45 is added to pool 07:28:11.794903 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.46 is added to pool 07:28:11.794904 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.47 is added to pool 07:28:11.794906 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.48 is added to pool 07:28:11.794907 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.49 is added to pool 07:28:11.794908 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.50 is added to pool 07:28:11.794910 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.51 is added to pool 07:28:11.794911 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.52 is added to pool 07:28:11.794913 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.53 is added to pool 07:28:11.794915 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.54 is added to pool 07:28:11.794916 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.55 is added to pool 07:28:11.794918 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.56 is added to pool 07:28:11.794920 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.57 is added to pool 07:28:11.794922 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.58 is added to pool 07:28:11.794924 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.59 is added to pool 07:28:11.794925 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.60 is added to pool 07:28:11.794927 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.61 is added to pool 07:28:11.794929 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.62 is added to pool 07:28:11.794930 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.63 is added to pool 07:28:11.794933 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.64 is added to pool 07:28:11.794934 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.65 is added to pool 07:28:11.794936 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.66 is added to pool 07:28:11.794937 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.67 is added to pool 07:28:11.794939 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.68 is added to pool 07:28:11.794941 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.69 is added to pool 07:28:11.794944 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.70 is added to pool 07:28:11.794946 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.71 is added to pool 07:28:11.794948 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.72 is added to pool 07:28:11.794949 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.73 is added to pool 07:28:11.794951 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.74 is added to pool 07:28:11.794953 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.75 is added to pool 07:28:11.794954 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.76 is added to pool 07:28:11.794956 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.77 is added to pool 07:28:11.794958 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.78 is added to pool 07:28:11.794960 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.79 is added to pool 07:28:11.794961 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.80 is added to pool 07:28:11.794963 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.81 is added to pool 07:28:11.794973 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.82 is added to pool 07:28:11.794979 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.83 is added to pool 07:28:11.794981 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.84 is added to pool 07:28:11.794982 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.85 is added to pool 07:28:11.794983 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.86 is added to pool 07:28:11.794984 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.87 is added to pool 07:28:11.794986 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.88 is added to pool 07:28:11.794987 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.89 is added to pool 07:28:11.794989 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.90 is added to pool 07:28:11.794991 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.91 is added to pool 07:28:11.794992 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.92 is added to pool 07:28:11.794994 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.93 is added to pool 07:28:11.794995 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.94 is added to pool 07:28:11.794997 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.95 is added to pool 07:28:11.794998 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.96 is added to pool 07:28:11.795000 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.97 is added to pool 07:28:11.795002 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.98 is added to pool 07:28:11.795003 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.99 is added to pool 07:28:11.795005 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.100 is added to pool 07:28:11.795007 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.101 is added to pool 07:28:11.795008 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.102 is added to pool 07:28:11.795010 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.103 is added to pool 07:28:11.795011 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.104 is added to pool 07:28:11.795013 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.105 is added to pool 07:28:11.795014 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.106 is added to pool 07:28:11.795016 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.107 is added to pool 07:28:11.795017 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.108 is added to pool 07:28:11.795019 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.109 is added to pool 07:28:11.795020 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.110 is added to pool 07:28:11.795022 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.111 is added to pool 07:28:11.795023 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.112 is added to pool 07:28:11.795025 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.113 is added to pool 07:28:11.795027 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.114 is added to pool 07:28:11.795028 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.115 is added to pool 07:28:11.795030 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.116 is added to pool 07:28:11.795032 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.117 is added to pool 07:28:11.795033 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.118 is added to pool 07:28:11.795035 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.119 is added to pool 07:28:11.795036 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.120 is added to pool 07:28:11.795038 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.121 is added to pool 07:28:11.795040 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.122 is added to pool 07:28:11.795043 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.123 is added to pool 07:28:11.795044 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.124 is added to pool 07:28:11.795046 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.125 is added to pool 07:28:11.795048 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.126 is added to pool 07:28:11.795049 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.127 is added to pool 07:28:11.795051 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.128 is added to pool 07:28:11.795054 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.129 is added to pool 07:28:11.795056 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.130 is added to pool 07:28:11.795058 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.131 is added to pool 07:28:11.795059 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.132 is added to pool 07:28:11.795061 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.133 is added to pool 07:28:11.795063 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.134 is added to pool 07:28:11.795065 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.135 is added to pool 07:28:11.795067 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.136 is added to pool 07:28:11.795068 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.137 is added to pool 07:28:11.795070 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.138 is added to pool 07:28:11.795071 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.139 is added to pool 07:28:11.795073 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.140 is added to pool 07:28:11.795074 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.141 is added to pool 07:28:11.795076 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.142 is added to pool 07:28:11.795077 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.143 is added to pool 07:28:11.795079 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.144 is added to pool 07:28:11.795081 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.145 is added to pool 07:28:11.795083 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.146 is added to pool 07:28:11.795085 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.147 is added to pool 07:28:11.795087 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.148 is added to pool 07:28:11.795088 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.149 is added to pool 07:28:11.795092 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.150 is added to pool 07:28:11.795094 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.151 is added to pool 07:28:11.795095 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.152 is added to pool 07:28:11.795097 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.153 is added to pool 07:28:11.795099 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.154 is added to pool 07:28:11.795100 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.155 is added to pool 07:28:11.795103 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.156 is added to pool 07:28:11.795104 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.157 is added to pool 07:28:11.795106 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.158 is added to pool 07:28:11.795108 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.159 is added to pool 07:28:11.795109 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.160 is added to pool 07:28:11.795111 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.161 is added to pool 07:28:11.795112 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.162 is added to pool 07:28:11.795114 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.163 is added to pool 07:28:11.795116 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.164 is added to pool 07:28:11.795117 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.165 is added to pool 07:28:11.795119 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.166 is added to pool 07:28:11.795120 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.167 is added to pool 07:28:11.795126 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.168 is added to pool 07:28:11.795127 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.169 is added to pool 07:28:11.795129 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.170 is added to pool 07:28:11.795132 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.171 is added to pool 07:28:11.795134 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.172 is added to pool 07:28:11.795135 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.173 is added to pool 07:28:11.795137 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.174 is added to pool 07:28:11.795138 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.175 is added to pool 07:28:11.795140 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.176 is added to pool 07:28:11.795141 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.177 is added to pool 07:28:11.795143 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.178 is added to pool 07:28:11.795145 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.179 is added to pool 07:28:11.795146 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.180 is added to pool 07:28:11.795150 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.181 is added to pool 07:28:11.795151 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.182 is added to pool 07:28:11.795153 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.183 is added to pool 07:28:11.795155 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.184 is added to pool 07:28:11.795156 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.185 is added to pool 07:28:11.795158 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.186 is added to pool 07:28:11.795160 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.187 is added to pool 07:28:11.795161 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.188 is added to pool 07:28:11.795163 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.189 is added to pool 07:28:11.795167 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.190 is added to pool 07:28:11.795168 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.191 is added to pool 07:28:11.795170 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.192 is added to pool 07:28:11.795171 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.193 is added to pool 07:28:11.795174 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.194 is added to pool 07:28:11.795176 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.195 is added to pool 07:28:11.795179 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.196 is added to pool 07:28:11.795181 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.197 is added to pool 07:28:11.795182 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.198 is added to pool 07:28:11.795184 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.199 is added to pool 07:28:11.795186 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.200 is added to pool 07:28:11.795187 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.201 is added to pool 07:28:11.795189 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.202 is added to pool 07:28:11.795190 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.203 is added to pool 07:28:11.795191 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.204 is added to pool 07:28:11.795193 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.205 is added to pool 07:28:11.795194 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.206 is added to pool 07:28:11.795196 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.207 is added to pool 07:28:11.795197 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.208 is added to pool 07:28:11.795199 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.209 is added to pool 07:28:11.795201 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.210 is added to pool 07:28:11.795202 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.211 is added to pool 07:28:11.795204 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.212 is added to pool 07:28:11.795205 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.213 is added to pool 07:28:11.795207 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.214 is added to pool 07:28:11.795208 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.215 is added to pool 07:28:11.795210 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.216 is added to pool 07:28:11.795212 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.217 is added to pool 07:28:11.795213 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.218 is added to pool 07:28:11.795215 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.219 is added to pool 07:28:11.795217 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.220 is added to pool 07:28:11.795219 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.221 is added to pool 07:28:11.795221 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.222 is added to pool 07:28:11.795223 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.223 is added to pool 07:28:11.795224 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.224 is added to pool 07:28:11.795226 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.225 is added to pool 07:28:11.795228 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.226 is added to pool 07:28:11.795231 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.227 is added to pool 07:28:11.795233 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.228 is added to pool 07:28:11.795234 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.229 is added to pool 07:28:11.795236 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.230 is added to pool 07:28:11.795238 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.231 is added to pool 07:28:11.795239 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.232 is added to pool 07:28:11.795241 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.233 is added to pool 07:28:11.795242 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.234 is added to pool 07:28:11.795245 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.235 is added to pool 07:28:11.795248 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.236 is added to pool 07:28:11.795250 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.237 is added to pool 07:28:11.795251 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.238 is added to pool 07:28:11.795254 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.239 is added to pool 07:28:11.795255 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.240 is added to pool 07:28:11.795257 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.241 is added to pool 07:28:11.795258 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.242 is added to pool 07:28:11.795260 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.243 is added to pool 07:28:11.795262 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.244 is added to pool 07:28:11.795264 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.245 is added to pool 07:28:11.795266 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.246 is added to pool 07:28:11.795267 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.247 is added to pool 07:28:11.795269 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.248 is added to pool 07:28:11.795272 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.249 is added to pool 07:28:11.795273 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.250 is added to pool 07:28:11.795275 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.251 is added to pool 07:28:11.795277 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.252 is added to pool 07:28:11.795278 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.253 is added to pool 07:28:11.795283 [SPGW GTPC] [D] SPGW: init_ue_ip ue ip addr 172.16.0.254 is added to pool 07:28:11.795283 [SPGW GTPC] [I] SPGW S11 Initialized. 07:28:11.795389 [SPGW ] [I] SP-GW Initialized. 07:28:11.845666 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:28:11.845712 [SPGW ] [D] Message received at SPGW: SGi Message 07:28:11.845721 [GTPU ] [D] Received SGi PDU. Bytes 48 07:28:11.845722 [GTPU ] [I] IPv6 not supported yet. 07:28:11.927805 [S1AP ] [I] Received S1AP msg. Size: 49 07:28:11.927922 [S1AP ] [I] Received Initiating PDU 07:28:11.927926 [S1AP ] [I] Received S1 Setup Request. 07:28:11.927942 [S1AP ] [I] Received S1 Setup Request. 07:28:11.927948 [S1AP ] [D] eNB SCTP association Id: 16 07:28:11.927956 [S1AP ] [I] S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b 07:28:11.927958 [S1AP ] [I] S1 Setup Request - MCC:001, MNC:01, PLMN: 61712 07:28:11.927962 [S1AP ] [I] S1 Setup Request - TAC 7, B-PLMN 0xf110 07:28:11.927974 [S1AP ] [I] Adding new eNB context. eNB ID 411 07:28:11.927994 [S1AP ] [D] Sending S1 Setup Response 07:28:11.928008 [S1AP ] [D] Transmitting S1AP PDU. eNB SCTP association Id: 16 07:28:11.928055 [S1AP ] [D] S1 Setup Response sent 07:28:11.928070 [S1AP ] [I] Sending S1 Setup Response 07:28:11.928074 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:28:15.607044 [SPGW ] [D] Message received at SPGW: SGi Message 07:28:15.607073 [GTPU ] [D] Received SGi PDU. Bytes 48 07:28:15.607075 [GTPU ] [I] IPv6 not supported yet. 07:28:23.035084 [SPGW ] [D] Message received at SPGW: SGi Message 07:28:23.035098 [GTPU ] [D] Received SGi PDU. Bytes 48 07:28:23.035099 [GTPU ] [I] IPv6 not supported yet. 07:28:37.623202 [SPGW ] [D] Message received at SPGW: SGi Message 07:28:37.623237 [GTPU ] [D] Received SGi PDU. Bytes 48 07:28:37.623240 [GTPU ] [I] IPv6 not supported yet. 07:29:08.599129 [SPGW ] [D] Message received at SPGW: SGi Message 07:29:08.599156 [GTPU ] [D] Received SGi PDU. Bytes 48 07:29:08.599158 [GTPU ] [I] IPv6 not supported yet. 07:30:10.039051 [SPGW ] [D] Message received at SPGW: SGi Message 07:30:10.039083 [GTPU ] [D] Received SGi PDU. Bytes 48 07:30:10.039086 [GTPU ] [I] IPv6 not supported yet. 07:32:06.775054 [SPGW ] [D] Message received at SPGW: SGi Message 07:32:06.775075 [GTPU ] [D] Received SGi PDU. Bytes 48 07:32:06.775078 [GTPU ] [I] IPv6 not supported yet. 07:32:46.340945 [S1AP ] [I] Received S1AP msg. Size: 114 07:32:46.341016 [S1AP ] [I] Received Initiating PDU 07:32:46.341024 [S1AP ] [I] Received Initial UE Message. 07:32:46.341121 [S1AP ] [I] Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST 07:32:46.341142 [S1AP ] [I] Received Initial UE message -- Attach Request 07:32:46.341229 [NAS ] [I] Attach request -- IMSI: 901700000044987 07:32:46.341249 [NAS ] [I] Attach request -- eNB-UE S1AP Id: 1 07:32:46.341256 [NAS ] [I] Attach request -- Attach type: 2 07:32:46.341266 [NAS ] [I] Attach Request -- UE Network Capabilities EEA: 11100000 07:32:46.341282 [NAS ] [I] Attach Request -- UE Network Capabilities EIA: 01100000 07:32:46.341299 [NAS ] [I] Attach Request -- MS Network Capabilities Present: true 07:32:46.341306 [NAS ] [I] PDN Connectivity Request -- EPS Bearer Identity requested: 0 07:32:46.341312 [NAS ] [I] PDN Connectivity Request -- Procedure Transaction Id: 1 07:32:46.341322 [NAS ] [I] PDN Connectivity Request -- ESM Information Transfer requested: true 07:32:46.341350 [NAS ] [D] NAS Context Initialized. MCC: 0xf001, MNC 0xff01 07:32:46.341359 [HSS ] [D] Generating AUTH info answer 07:32:46.341397 [HSS ] [D] User Key : 0000: 83 32 18 d6 15 b1 10 70 6d b6 e7 fd 69 22 2b e9 07:32:46.341405 [HSS ] [D] User OPc : 0000: d0 c4 1e d0 7d fe 2f 9b b0 db 08 3e 5e 34 7f 5e 07:32:46.341407 [HSS ] [D] User Rand : 0000: c6 0f b8 f2 fd 46 a9 c3 cf 05 50 7f e6 c3 e8 ad 07:32:46.341409 [HSS ] [D] User XRES: 0000: 9c f2 5e cf 5c ba 33 5c 07:32:46.341411 [HSS ] [D] User CK: 0000: e0 ea 1a 80 a2 14 18 8c bb cd 27 a3 f3 9d 69 b6 07:32:46.341413 [HSS ] [D] User IK: 0000: b4 09 56 cb 41 aa 18 2e 35 cd 8a 0a 91 b4 3f 8e 07:32:46.341414 [HSS ] [D] User AK: 0000: 80 63 4c 08 c8 05 07:32:46.341416 [HSS ] [D] User SQN : 0000: 00 00 00 00 00 e7 07:32:46.341418 [HSS ] [D] User MAC : 0000: bf 9b 72 8a 71 e8 26 01 07:32:46.341456 [HSS ] [D] User MCC : f001 MNC : ff01 07:32:46.341458 [HSS ] [D] User k_asme : 0000: 00 2d bf 35 52 67 fe 45 cb 66 62 c0 6c 5e 01 be 0010: 7f 25 d1 71 50 33 8a ce a1 bb 73 e8 4e 35 b1 57 07:32:46.341459 [HSS ] [D] User AUTN: 0000: 80 63 4c 08 c8 e2 90 00 bf 9b 72 8a 71 e8 26 01 07:32:46.341461 [HSS ] [D] Incremented SQN -- IMSI: 901700000044987 07:32:46.341462 [HSS ] [D] SQN: 0000: 00 00 00 00 01 08 07:32:46.341464 [S1AP ] [D] Saved UE context corresponding to IMSI 901700000044987 07:32:46.341465 [S1AP ] [D] Saved UE context corresponding to MME UE S1AP Id 1 07:32:46.341467 [S1AP ] [D] Added UE with MME-UE S1AP Id 1 to eNB with association 16 07:32:46.341468 [NAS ] [I] Packing Authentication Request 07:32:46.341481 [S1AP ] [D] Sending message to eNB with SCTP association 16. MME UE S1AP ID 1, eNB UE S1AP ID 1 07:32:46.341528 [S1AP ] [D] Transmitting S1AP PDU. eNB SCTP association Id: 16 07:32:46.341712 [NAS ] [I] Downlink NAS: Sending Authentication Request 07:32:46.341737 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:32:46.389109 [S1AP ] [I] Received S1AP msg. Size: 49 07:32:46.389146 [S1AP ] [I] Received Initiating PDU 07:32:46.389150 [S1AP ] [I] Received Uplink NAS Transport Message. 07:32:46.389152 [S1AP ] [D] Received uplink NAS and found UE NAS context. MME-UE S1AP id: 1 07:32:46.389157 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS, mac_vaild: no, msg_encrypted: no 07:32:46.389158 [S1AP ] [I] UL NAS: Authentication Failure 07:32:46.389189 [NAS ] [I] Received Authentication Failure 07:32:46.389201 [NAS ] [I] MAC code failure 07:32:46.389205 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:33:16.341382 [S1AP ] [I] Received S1AP msg. Size: 25 07:33:16.341425 [S1AP ] [I] Received Initiating PDU 07:33:16.341428 [S1AP ] [I] Received UE Context Release Request Message. 07:33:16.341431 [S1AP ] [I] Received UE Context Release Request. MME-UE S1AP Id: 1 07:33:16.341477 [S1AP ] [I] UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 1 07:33:16.341483 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:36:00.247148 [SPGW ] [D] Message received at SPGW: SGi Message 07:36:00.247183 [GTPU ] [D] Received SGi PDU. Bytes 48 07:36:00.247187 [GTPU ] [I] IPv6 not supported yet. 07:36:31.885971 [S1AP ] [I] Received S1AP msg. Size: 114 07:36:31.886033 [S1AP ] [I] Received Initiating PDU 07:36:31.886041 [S1AP ] [I] Received Initial UE Message. 07:36:31.886194 [S1AP ] [I] Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST 07:36:31.886226 [S1AP ] [I] Received Initial UE message -- Attach Request 07:36:31.886259 [NAS ] [I] Attach request -- IMSI: 901700000044987 07:36:31.886277 [NAS ] [I] Attach request -- eNB-UE S1AP Id: 2 07:36:31.886289 [NAS ] [I] Attach request -- Attach type: 2 07:36:31.886301 [NAS ] [I] Attach Request -- UE Network Capabilities EEA: 11100000 07:36:31.886313 [NAS ] [I] Attach Request -- UE Network Capabilities EIA: 01100000 07:36:31.886330 [NAS ] [I] Attach Request -- MS Network Capabilities Present: true 07:36:31.886341 [NAS ] [I] PDN Connectivity Request -- EPS Bearer Identity requested: 0 07:36:31.886350 [NAS ] [I] PDN Connectivity Request -- Procedure Transaction Id: 1 07:36:31.886360 [NAS ] [I] PDN Connectivity Request -- ESM Information Transfer requested: true 07:36:31.886362 [NAS ] [I] Attach Request -- Found previously attached UE. 07:36:31.886372 [MME GTPC] [I] Sending GTP-C Delete Session Request request. IMSI 901700000044987 07:36:31.886374 [MME GTPC] [E] Could not find GTP-C context to remove 07:36:31.886377 [S1AP ] [E] UE is not ECM connected. No send context release command. MME UE S1AP Id 1 07:36:31.886383 [S1AP ] [I] Released UE ECM Context. 07:36:31.886387 [S1AP ] [I] Deleted UE Context. 07:36:31.886396 [NAS ] [D] NAS Context Initialized. MCC: 0xf001, MNC 0xff01 07:36:31.886399 [HSS ] [D] Generating AUTH info answer 07:36:31.886407 [HSS ] [D] User Key : 0000: 83 32 18 d6 15 b1 10 70 6d b6 e7 fd 69 22 2b e9 07:36:31.886409 [HSS ] [D] User OPc : 0000: d0 c4 1e d0 7d fe 2f 9b b0 db 08 3e 5e 34 7f 5e 07:36:31.886411 [HSS ] [D] User Rand : 0000: 16 06 1d 16 3d 19 dd 43 65 d5 c1 f5 f5 ac 00 bb 07:36:31.886413 [HSS ] [D] User XRES: 0000: 8c fc 70 3e d0 99 00 7c 07:36:31.886415 [HSS ] [D] User CK: 0000: 53 cc 5c 3e 5a ae 68 a5 7e 25 70 09 0a f9 4b bf 07:36:31.886417 [HSS ] [D] User IK: 0000: 0a 0b 34 c5 d8 53 da d4 57 f0 68 76 fc 31 b5 23 07:36:31.886419 [HSS ] [D] User AK: 0000: 2b 91 b0 a2 97 a8 07:36:31.886422 [HSS ] [D] User SQN : 0000: 00 00 00 00 01 08 07:36:31.886425 [HSS ] [D] User MAC : 0000: 94 de 12 11 56 0f a2 09 07:36:31.886445 [HSS ] [D] User MCC : f001 MNC : ff01 07:36:31.886447 [HSS ] [D] User k_asme : 0000: 59 09 e2 cd 49 f3 3f ea c1 7c 41 ea ee 02 08 0e 0010: 8b cc 13 ad 14 e0 7d 86 de 85 80 e9 4b 45 fb ff 07:36:31.886449 [HSS ] [D] User AUTN: 0000: 2b 91 b0 a2 96 a0 90 00 94 de 12 11 56 0f a2 09 07:36:31.886452 [HSS ] [D] Incremented SQN -- IMSI: 901700000044987 07:36:31.886454 [HSS ] [D] SQN: 0000: 00 00 00 00 01 29 07:36:31.886458 [S1AP ] [D] Saved UE context corresponding to IMSI 901700000044987 07:36:31.886460 [S1AP ] [D] Saved UE context corresponding to MME UE S1AP Id 2 07:36:31.886462 [S1AP ] [D] Added UE with MME-UE S1AP Id 2 to eNB with association 16 07:36:31.886464 [NAS ] [I] Packing Authentication Request 07:36:31.886468 [S1AP ] [D] Sending message to eNB with SCTP association 16. MME UE S1AP ID 2, eNB UE S1AP ID 2 07:36:31.886486 [S1AP ] [D] Transmitting S1AP PDU. eNB SCTP association Id: 16 07:36:31.886778 [NAS ] [I] Downlink NAS: Sending Authentication Request 07:36:31.886817 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:36:31.925701 [S1AP ] [I] Received S1AP msg. Size: 49 07:36:31.925737 [S1AP ] [I] Received Initiating PDU 07:36:31.925742 [S1AP ] [I] Received Uplink NAS Transport Message. 07:36:31.925744 [S1AP ] [D] Received uplink NAS and found UE NAS context. MME-UE S1AP id: 2 07:36:31.925747 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS, mac_vaild: no, msg_encrypted: no 07:36:31.925748 [S1AP ] [I] UL NAS: Authentication Failure 07:36:31.925769 [NAS ] [I] Received Authentication Failure 07:36:31.925777 [NAS ] [I] MAC code failure 07:36:31.925781 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:37:01.885966 [S1AP ] [I] Received S1AP msg. Size: 25 07:37:01.885984 [S1AP ] [I] Received Initiating PDU 07:37:01.885985 [S1AP ] [I] Received UE Context Release Request Message. 07:37:01.885986 [S1AP ] [I] Received UE Context Release Request. MME-UE S1AP Id: 2 07:37:01.886006 [S1AP ] [I] UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 2 07:37:01.886008 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:37:25.148615 [S1AP ] [I] Received S1AP msg. Size: 114 07:37:25.148676 [S1AP ] [I] Received Initiating PDU 07:37:25.148679 [S1AP ] [I] Received Initial UE Message. 07:37:25.148725 [S1AP ] [I] Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST 07:37:25.148740 [S1AP ] [I] Received Initial UE message -- Attach Request 07:37:25.148772 [NAS ] [I] Attach request -- IMSI: 901700000044987 07:37:25.148796 [NAS ] [I] Attach request -- eNB-UE S1AP Id: 3 07:37:25.148809 [NAS ] [I] Attach request -- Attach type: 2 07:37:25.148828 [NAS ] [I] Attach Request -- UE Network Capabilities EEA: 11100000 07:37:25.148844 [NAS ] [I] Attach Request -- UE Network Capabilities EIA: 01100000 07:37:25.148861 [NAS ] [I] Attach Request -- MS Network Capabilities Present: true 07:37:25.148871 [NAS ] [I] PDN Connectivity Request -- EPS Bearer Identity requested: 0 07:37:25.148881 [NAS ] [I] PDN Connectivity Request -- Procedure Transaction Id: 2 07:37:25.148891 [NAS ] [I] PDN Connectivity Request -- ESM Information Transfer requested: true 07:37:25.148893 [NAS ] [I] Attach Request -- Found previously attached UE. 07:37:25.149300 [MME GTPC] [I] Sending GTP-C Delete Session Request request. IMSI 901700000044987 07:37:25.149315 [MME GTPC] [E] Could not find GTP-C context to remove 07:37:25.149319 [S1AP ] [E] UE is not ECM connected. No send context release command. MME UE S1AP Id 2 07:37:25.149326 [S1AP ] [I] Released UE ECM Context. 07:37:25.149330 [S1AP ] [I] Deleted UE Context. 07:37:25.149341 [NAS ] [D] NAS Context Initialized. MCC: 0xf001, MNC 0xff01 07:37:25.149345 [HSS ] [D] Generating AUTH info answer 07:37:25.149354 [HSS ] [D] User Key : 0000: 83 32 18 d6 15 b1 10 70 6d b6 e7 fd 69 22 2b e9 07:37:25.149363 [HSS ] [D] User OPc : 0000: d0 c4 1e d0 7d fe 2f 9b b0 db 08 3e 5e 34 7f 5e 07:37:25.149366 [HSS ] [D] User Rand : 0000: bc b8 ae b9 fe 57 7c cd 5c cc 4d 43 8f 35 f0 a5 07:37:25.149368 [HSS ] [D] User XRES: 0000: a5 e8 58 32 f9 59 28 07 07:37:25.149370 [HSS ] [D] User CK: 0000: 0b 72 c7 5c 11 0e a9 5b 88 4a e1 9e a6 21 f6 3b 07:37:25.149372 [HSS ] [D] User IK: 0000: 0a 96 88 bf f5 f7 5d 13 e7 20 cd d2 06 55 b6 a4 07:37:25.149374 [HSS ] [D] User AK: 0000: 2c ac 00 8a 54 53 07:37:25.149377 [HSS ] [D] User SQN : 0000: 00 00 00 00 01 29 07:37:25.149380 [HSS ] [D] User MAC : 0000: a4 62 ec c8 91 cb 82 6b 07:37:25.149402 [HSS ] [D] User MCC : f001 MNC : ff01 07:37:25.149406 [HSS ] [D] User k_asme : 0000: c0 3a f6 a2 91 97 a0 0e 9f 1c 1f 40 17 de 64 66 0010: 31 65 0d 76 6f 21 15 52 b9 08 72 20 3e 60 8a 58 07:37:25.149412 [HSS ] [D] User AUTN: 0000: 2c ac 00 8a 55 7a 90 00 a4 62 ec c8 91 cb 82 6b 07:37:25.149415 [HSS ] [D] Incremented SQN -- IMSI: 901700000044987 07:37:25.149514 [HSS ] [D] SQN: 0000: 00 00 00 00 01 4a 07:37:25.149519 [S1AP ] [D] Saved UE context corresponding to IMSI 901700000044987 07:37:25.149522 [S1AP ] [D] Saved UE context corresponding to MME UE S1AP Id 3 07:37:25.149524 [S1AP ] [D] Added UE with MME-UE S1AP Id 3 to eNB with association 16 07:37:25.149525 [NAS ] [I] Packing Authentication Request 07:37:25.149529 [S1AP ] [D] Sending message to eNB with SCTP association 16. MME UE S1AP ID 3, eNB UE S1AP ID 3 07:37:25.149546 [S1AP ] [D] Transmitting S1AP PDU. eNB SCTP association Id: 16 07:37:25.149648 [NAS ] [I] Downlink NAS: Sending Authentication Request 07:37:25.149690 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:37:25.188933 [S1AP ] [I] Received S1AP msg. Size: 49 07:37:25.189031 [S1AP ] [I] Received Initiating PDU 07:37:25.189033 [S1AP ] [I] Received Uplink NAS Transport Message. 07:37:25.189036 [S1AP ] [D] Received uplink NAS and found UE NAS context. MME-UE S1AP id: 3 07:37:25.189042 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS, mac_vaild: no, msg_encrypted: no 07:37:25.189043 [S1AP ] [I] UL NAS: Authentication Failure 07:37:25.189172 [NAS ] [I] Received Authentication Failure 07:37:25.189188 [NAS ] [I] MAC code failure 07:37:25.189194 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:37:55.148782 [S1AP ] [I] Received S1AP msg. Size: 25 07:37:55.148863 [S1AP ] [I] Received Initiating PDU 07:37:55.148871 [S1AP ] [I] Received UE Context Release Request Message. 07:37:55.148874 [S1AP ] [I] Received UE Context Release Request. MME-UE S1AP Id: 3 07:37:55.148912 [S1AP ] [I] UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 3 07:37:55.148917 [S1AP ] [D] Waiting for S1-MME or S11 Message 07:38:10.619267 [S1AP ] [I] Deleting eNB context. eNB Id: 0x19b 07:38:10.619320 [S1AP ] [I] Deleting UE EMM context. IMSI: 901700000044987 07:38:10.652215 [HSS ] [I] Opened DB file: /home/enodeb/.config/srsran/user_db.csv

1 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC September 2021