[srslte-users] [srsLTE] MAC code failure

Wed Jun 13 13:43:17 UTC 2018

Hello Pedro,

Yes, indeed the sim card was configured from factory to use the milenage
algorithm. another aspect, i am using a ETTUS USRP X310, sadly i am not
able to perform an LTE 20 MHz and also 64QAM, why do you think is this
behaviour?

maybe the LTE 20MHz i can think is because of my low sample ratio from the
eth0 1GB connection, which is feeding the data to 25Msper second and in
case of LTE 20MHz the sample rate is 30.72 Mhz and i am not respecting the
nyquist sampling rate.

My question is why not be able to use the 64QAM modulation? if i set it to
64QAM in the enb.conf basically the UEs cannot connect to the network
anymore. From you experience what it might be the cause? or...what should i
configure more?

Thank you,
Mihai

On Wed, Jun 13, 2018 at 4:34 PM, Pedro Alvarez <
pedro.alvarez at softwareradiosystems.com> wrote:

> Hi Mihai,
>
> My suspicion is that that card is configured with the MILENAGE algorithm.
> Can you check this please? There are some instructions on how to check the
> authentication algorithm in section 7.2.4 of the sysmoUSIM User Manual:
> https://www.sysmocom.de/manuals/sysmousim-manual.pdf
> You can also just change srsEPC authentication to MILENAGE and see if it
> works.
>
> Another thing is that srsEPC expects the OP on the SIM, not the OPc.
> This limitation should be addressed by the next version.
>
> Regards,
> Pedro
>
> On Tue, Jun 5, 2018 at 9:09 AM, Mihai Idu <idumihai16 at gmail.com> wrote:
>
>> Hello Pedro and all,
>>
>> The sim is an sysmocom SjS1.
>>
>> python pySim-prog.py
>> --pcsc-device=0
>> --type="sysmoUSIM-SJS1"
>> --mcc=208
>> --mnc=92
>> --imsi=208920100001100
>> --opc=e734f8734007d6c5ce7a0508809e7e9c
>> --ki=8baf473f2f8fd09487cccbd7097c6862
>> --iccid=8988211000000094808
>> --pin-adm=60969289
>> --acc=0001
>>
>> Indeed, in the network i am using as a authentication algorithm the XOR
>> and in the HSS is request only the OP. Now i am thinking more about this
>> perspective of yours. You think the sim is wrong programmed?
>>
>>
>> Thank you,
>> Mihai
>>
>>
>>
>> On Tue, Jun 5, 2018 at 10:58 AM, Pedro Alvarez <
>> pedro.alvarez at softwareradiosystems.com> wrote:
>>
>>> Hi Mihai,
>>>
>>> It seems that UE is rejecting the authentication from the network.
>>> Can you provide me with the following information:
>>>
>>> 1 - Is you SIM card using MILENAGE or XOR authentication algorithm?
>>> 2 - If MILENAGE, is the SIM you are using configured with OP or OPc?
>>>
>>> Regards,
>>> Pedro
>>>
>>> On Tue, Jun 5, 2018 at 7:50 AM, Mihai Idu <idumihai16 at gmail.com> wrote:
>>>
>>>> Hello Pedro and all,
>>>>
>>>> Could you help me with a resolution regarding the following error:
>>>> Attach Request -- UE is already attached.Attach request -- IMSI:
>>>> 901700000022950
>>>> Attach request -- eNB-UE S1AP Id: 19, MME-UE S1AP Id: 19
>>>> Attach request -- Attach type: 2
>>>> Attach Request -- UE Network Capabilities EEA: 11110000
>>>> Attach Request -- UE Network Capabilities EIA: 11110000
>>>> 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: false
>>>> Downlink NAS: Sending Authentication Request
>>>> Plain UL NAS: Authentication Failure
>>>> MAC code failure
>>>> Received UE Context Release Request. MME-UE S1AP Id 19
>>>> UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 19
>>>> UE is ECM IDLE.
>>>>
>>>> 
>>>>  enb.log
>>>> <https://drive.google.com/file/d/1d6H26FMvYWAuZG1fPzJ78yMJUfdVlq34/view?usp=drive_web>
>>>> 
>>>>  enb.pcap
>>>> <https://drive.google.com/file/d/1l1FMRX8DzmsZF64MgHmZ8PIOFXU9dhgO/view?usp=drive_web>
>>>> 
>>>>  epc.log
>>>> <https://drive.google.com/file/d/1gEyzxW7fzhwOwbM9CbGpAqoFTFYMbKC-/view?usp=drive_web>
>>>> 
>>>>
>>>> Thank you,
>>>> Mihai
>>>>
>>>> On Sun, Jun 3, 2018 at 9:39 PM, Pedro Alvarez <
>>>> pedro.alvarez at softwareradiosystems.com> wrote:
>>>>
>>>>> Hi Mihai,
>>>>>
>>>>> Does this happen when you try to connect one user only?
>>>>> Can you send the epc.log and the enb.pcap of the two user case?
>>>>>
>>>>> Regards,
>>>>> Pedro
>>>>>
>>>>> On Sun, Jun 3, 2018 at 11:45 AM, Mihai Idu <idumihai16 at gmail.com>
>>>>> wrote:
>>>>> > Hello srs users,
>>>>> >
>>>>> > i am writing this e-mail because i am finding myself into a blocking
>>>>> point,
>>>>> > and i would love a little help. I am implemented the following
>>>>> settup:
>>>>> >
>>>>> > 1. USRP X310 which is the enodeB and i have 2 users Huawei P9 lite
>>>>> >
>>>>> > I manage to define the users in the HSS and changed the MNC and MCC
>>>>> > according to the IMSI. but when i try to connect the phones to the
>>>>> network i
>>>>> > am facing the following :
>>>>> >
>>>>> > Attach Request -- UE is already attached.Attach request -- IMSI:
>>>>> > 901700000022950
>>>>> > Attach request -- eNB-UE S1AP Id: 19, MME-UE S1AP Id: 19
>>>>> > Attach request -- Attach type: 2
>>>>> > Attach Request -- UE Network Capabilities EEA: 11110000
>>>>> > Attach Request -- UE Network Capabilities EIA: 11110000
>>>>> > 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: false
>>>>> > Downlink NAS: Sending Authentication Request
>>>>> > Plain UL NAS: Authentication Failure
>>>>> > MAC code failure
>>>>> > Received UE Context Release Request. MME-UE S1AP Id 19
>>>>> > UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 19
>>>>> > UE is ECM IDLE.
>>>>> >
>>>>> >
>>>>> > If anyone has some idea to fix this issue please, let me know. from
>>>>> my
>>>>> > knowledge this error message appears when the MAC provided by the
>>>>> network is
>>>>> > not a correct one.
>>>>> >
>>>>> > Thank you,
>>>>> > Mihai
>>>>> >
>>>>> > _______________________________________________
>>>>> > srslte-users mailing list
>>>>> > srslte-users at lists.softwareradiosystems.com
>>>>> > http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>>> >
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20180613/e14a578e/attachment.htm>