[srslte-users] NAS integrity error

Fri May 3 12:35:55 UTC 2019

Sorry for my mistake. In attachment I send the wright file.

Thank you.

Best regards,

Samuel Pereira

________________________________
De: Pedro Alvarez <pedro.alvarez at softwareradiosystems.com>
Enviado: 3 de maio de 2019 12:40:25
Para: Samuel Pereira
Cc: srslte-users
Assunto: Re: [srslte-users] NAS integrity error

Not the epc.conf, the epc.pcap. You can enable it by doing "srsepc
--pcap.enable=true" or changing the epc.conf accordingly.
The logs and pcaps are stored by default in the "/tmp" folder.

On Fri, May 3, 2019 at 12:30 PM Samuel Pereira <samuel.s.pereira at ua.pt> wrote:
>
> Yes, I send it in attachment.
>
>
> Best regards,
>
> Samuel Pereira
>
> ________________________________
> De: Pedro Alvarez <pedro.alvarez at softwareradiosystems.com>
> Enviado: 3 de maio de 2019 10:35:49
> Para: Samuel Pereira
> Cc: srslte-users
> Assunto: Re: [srslte-users] NAS integrity error
>
> Can you send the epc.pcap?
> I want to understand why the UE is sending a pdn connectivity request after the attach procedure.
>
> On Fri, 3 May 2019, 10:22 Samuel Pereira, <samuel.s.pereira at ua.pt> wrote:
>
> Hi Pedro,
>
>
> I am using srsapn on the dongle. I think that we are supposed to used the one specified in epc.conf, right?
>
>
> Best regards,
>
> Samuel Pereira
>
> ________________________________
> De: Pedro Alvarez <pedro.alvarez at softwareradiosystems.com>
> Enviado: 2 de maio de 2019 12:25:02
> Para: Samuel Pereira
> Cc: srslte-users at lists.softwareradiosystems.com
> Assunto: Re: [srslte-users] NAS integrity error
>
> Samuel --
>
> Does the APN settings on the dongle match the one in srsEPC?
> What APN are you using on the dongle?
>
> Cheers,
> Pedro
>
> On Thu, May 2, 2019 at 8:27 AM Samuel Pereira <samuel.s.pereira at ua.pt> wrote:
> >
> > Hello everyone,
> >
> >
> > I am using a Huawei dongle ref. E398 with SRSLTE enb and epc. The system works both with the SRSUE and with a Samsung S4. However, with this dongle we are receiving an error: "Unhandled NAS integrity protected message LIBLTE_MME_MSG_TYPE_PDN_CONNECTIVITY_REQUEST".
> >
> > The previous was the following:
> >
> > Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST
> > Received Initial UE message -- Attach Request
> > Attach request -- IMSI Style Attach request
> > Attach request -- IMSI: 268080000000002
> > Attach request -- eNB-UE S1AP Id: 1720
> > 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
> > Attach Request -- Found previously attach UE.
> > Downlink NAS: Sending Authentication Request
> > UL NAS: Received Authentication Response
> > Authentication Response -- IMSI 268080000000002
> > UE Authentication Accepted.
> > Generating KeNB with UL NAS COUNT: 0
> > Downlink NAS: Sending NAS Security Mode Command.
> > UL NAS: Received Security Mode Complete
> > Security Mode Command Complete -- IMSI: 268080000000002
> > Getting subscription information -- QCI 7
> > Sending Create Session Request.
> > Creating Session Response -- IMSI: 268080000000002
> > Creating Session Response -- MME control TEID: 41
> > SPGW: GTP-C context for IMSI 268080000000002 already exists.
> > SPGW: Deleted previous context.
> > SPGW: Allocated Ctrl TEID 41
> > SPGW: Allocated User TEID 41
> > SPGW: Allocate UE IP 172.16.0.42
> > Received Create Session Response
> > Create Session Response -- SPGW control TEID 41
> > Create Session Response -- SPGW S1-U Address: 127.0.1.100
> > SPGW Allocated IP 172.16.0.42 to ISMI 268080000000002
> > Adding attach accept to Initial Context Setup Request
> > Initial Context Setup Request -- eNB UE S1AP Id 1720, MME UE S1AP Id 1223
> > Initial Context Setup Request -- E-RAB id 5
> > Initial Context Setup Request -- S1-U TEID 0x29. IP 127.0.1.100
> > Initial Context Setup Request -- S1-U TEID 0x29. IP 127.0.1.100
> > Initial Context Setup Request -- QCI 7
> > Received Initial Context Setup Response
> > E-RAB Context Setup. E-RAB id 5
> > E-RAB Context -- eNB TEID 0x20320003; eNB GTP-U Address 127.0.1.1
> > UL NAS: Received Attach Complete
> > Unpacked Attached Complete Message. IMSI 268080000000002
> > Unpacked Activate Default EPS Bearer message. EPS Bearer id 5
> > Sending EMM Information
> > Unhandled NAS integrity protected message LIBLTE_MME_MSG_TYPE_PDN_CONNECTIVITY_REQUEST
> > Unhandled NAS integrity protected message LIBLTE_MME_MSG_TYPE_PDN_CONNECTIVITY_REQUEST
> > Unhandled NAS integrity protected message LIBLTE_MME_MSG_TYPE_PDN_CONNECTIVITY_REQUEST
> >
> > The same problem was observed with a Huawei PCIe modem.
> >
> >
> > Best regards,
> >
> > Samuel Pereira
> >
> > _______________________________________________
> > 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/20190503/555237e3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: epc.pcap
Type: application/vnd.tcpdump.pcap
Size: 3649 bytes
Desc: epc.pcap
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190503/555237e3/attachment.pcap>