[srslte-users] srslte-users Digest, Vol 44, Issue 12

Tue Nov 13 10:49:56 UTC 2018

Thanks Jason for following up on this.
I see in the epc.log that the Authentication algorithm is still set to XOR.

Can you change it to milenage in the epc.conf? If still doesn't work,
can you resend the logs and pcaps?
On Tue, Nov 13, 2018 at 10:29 AM Jason N <mbzoutlaw at gmail.com> wrote:
>
> Sorry to respond almost a month later.  I have updated to the latest srsLTE.  I tried this with an iPhone 6 and a Nexus 5x.  Same errors.  See attached log files and users db.
>
>
>
> On Tue, Oct 16, 2018 at 8:38 AM <srslte-users-request at lists.softwareradiosystems.com> wrote:
>>
>> Send srslte-users mailing list submissions to
>>         srslte-users at lists.softwareradiosystems.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>> or, via email, send a message with subject or body 'help' to
>>         srslte-users-request at lists.softwareradiosystems.com
>>
>> You can reach the person managing the list at
>>         srslte-users-owner at lists.softwareradiosystems.com
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of srslte-users digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: iPhone registration (Pedro Alvarez)
>>    2. Re: iPhone registration (Kewin Rausch)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 15 Oct 2018 15:22:12 +0100
>> From: Pedro Alvarez <pedro.alvarez at softwareradiosystems.com>
>> To: mbzoutlaw at gmail.com
>> Cc: srslte-users <srslte-users at lists.softwareradiosystems.com>
>> Subject: Re: [srslte-users] iPhone registration
>> Message-ID:
>>         <CACYSAhehogR-XWrqHtxAqj-7hMM5DMKG0Pf_9pQfvuX+r8eUmg at mail.gmail.com>
>> Content-Type: text/plain; charset="UTF-8"
>>
>> Jason --
>>
>> srsLTE version 18.03 is a bit old. There were some bugs in the EPC
>> regarding the handling of the OP code and the re-synch procedures that
>> got fixed in newer releases. Could you try the latest public version,
>> 18.09?
>>
>> If the problem persists, can you please resend the logs and the
>> epc.conf and users_db.csv?
>>
>> Regards,
>> Pedro
>> On Mon, Oct 15, 2018 at 3:01 PM Jason N <mbzoutlaw at gmail.com> wrote:
>> >
>> > Thanks Kewin,
>> >
>> > I did change the AMF to 8000.  I do see where the SQN is being added and incremented now.  Still having the same problem.  I have verified the OPc and Ki and IMSI.  What else could this be?  I have attached new logs and pcap files.
>> >
>> > On Fri, Oct 12, 2018 at 2:44 AM Kewin Rausch <krausch at fbk.eu> wrote:
>> >>
>> >> Hi there,
>> >>
>> >> For SQN it should be fine to leave it to 0; will be updated as the connection succeed.
>> >> Try to set AMF to 8000.
>> >>
>> >> Cheers,
>> >> Kewin R.
>> >>
>> >> On Fri, Oct 12, 2018 at 6:54 AM Jason N <mbzoutlaw at gmail.com> wrote:
>> >>>
>> >>> I am running an Ettus b205mini board.  srsLTE version 18.03.01.   I am using a known IMSI with Ki and OPC codes.  I don’t know the AMF or SQN so I set them as 0.  I have set milenage algorithm. The UE can see the base station and requests a connection, but I get an MAC error.
>> >>>
>> >>>
>> >>>
>> >>> Where can I get the SQN and AMF?  I have attached the log files.
>> >>>
>> >>>
>> >>>
>> >>> Thanks for your help
>> >>>
>> >>> _______________________________________________
>> >>> srslte-users mailing list
>> >>> srslte-users at lists.softwareradiosystems.com
>> >>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>> >>
>> >>
>> >> --
>> >> Le informazioni contenute nella presente comunicazione sono di natura privata e come tali sono da considerarsi riservate ed indirizzate esclusivamente ai destinatari indicati e per le finalità strettamente legate al relativo contenuto. Se avete ricevuto questo messaggio per errore, vi preghiamo di eliminarlo e di inviare una comunicazione all’indirizzo e-mail del mittente.
>> >> --
>> >> The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material.
>> >
>> > _______________________________________________
>> > srslte-users mailing list
>> > srslte-users at lists.softwareradiosystems.com
>> > http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 15 Oct 2018 16:25:13 +0200
>> From: Kewin Rausch <krausch at fbk.eu>
>> To: Pedro Alvarez <pedro.alvarez at softwareradiosystems.com>
>> Cc: srslte-users <srslte-users at lists.softwareradiosystems.com>, Jason
>>         N <mbzoutlaw at gmail.com>
>> Subject: Re: [srslte-users] iPhone registration
>> Message-ID:
>>         <CAFN=RORSK_7+skEDYMMq+9SiGD3x8kj-Lb+CxarVJzdgc_cUTg at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> I agree with Pedro.
>>
>> The problem here is a MAC failure: 09:49:03.920613 [S1AP] [I] MAC code
>> failure. I have this problem when the EPC does not want to proceed with the
>> authentication, and I solve it by revewing db info. From Google you can
>> also get:
>>
>> MAC code failure: If the UE finds that the MAC code supplied by the core
>> > network in the AUTN parameter is invalid, then the UE shall send an
>> > AUTHENTICATION FAILURE message to the network, with the EMM cause #20 "MAC
>> > failure". The network may initiate an identification procedure to obtain
>> > the IMSI from the UE or may also decides to terminate the authentication
>> > procedure
>>
>>
>> This is probably due the CN not trying to authenticate the UE. Try to
>> update everything to a newer version, maintaining same DB and configuration.
>>
>> Kewin R.
>>
>>
>> On Mon, Oct 15, 2018 at 4:22 PM Pedro Alvarez <
>> pedro.alvarez at softwareradiosystems.com> wrote:
>>
>> > Jason --
>> >
>> > srsLTE version 18.03 is a bit old. There were some bugs in the EPC
>> > regarding the handling of the OP code and the re-synch procedures that
>> > got fixed in newer releases. Could you try the latest public version,
>> > 18.09?
>> >
>> > If the problem persists, can you please resend the logs and the
>> > epc.conf and users_db.csv?
>> >
>> > Regards,
>> > Pedro
>> > On Mon, Oct 15, 2018 at 3:01 PM Jason N <mbzoutlaw at gmail.com> wrote:
>> > >
>> > > Thanks Kewin,
>> > >
>> > > I did change the AMF to 8000.  I do see where the SQN is being added and
>> > incremented now.  Still having the same problem.  I have verified the OPc
>> > and Ki and IMSI.  What else could this be?  I have attached new logs and
>> > pcap files.
>> > >
>> > > On Fri, Oct 12, 2018 at 2:44 AM Kewin Rausch <krausch at fbk.eu> wrote:
>> > >>
>> > >> Hi there,
>> > >>
>> > >> For SQN it should be fine to leave it to 0; will be updated as the
>> > connection succeed.
>> > >> Try to set AMF to 8000.
>> > >>
>> > >> Cheers,
>> > >> Kewin R.
>> > >>
>> > >> On Fri, Oct 12, 2018 at 6:54 AM Jason N <mbzoutlaw at gmail.com> wrote:
>> > >>>
>> > >>> I am running an Ettus b205mini board.  srsLTE version 18.03.01.   I am
>> > using a known IMSI with Ki and OPC codes.  I don’t know the AMF or SQN so I
>> > set them as 0.  I have set milenage algorithm. The UE can see the base
>> > station and requests a connection, but I get an MAC error.
>> > >>>
>> > >>>
>> > >>>
>> > >>> Where can I get the SQN and AMF?  I have attached the log files.
>> > >>>
>> > >>>
>> > >>>
>> > >>> Thanks for your help
>> > >>>
>> > >>> _______________________________________________
>> > >>> srslte-users mailing list
>> > >>> srslte-users at lists.softwareradiosystems.com
>> > >>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>> > >>
>> > >>
>> > >> --
>> > >> Le informazioni contenute nella presente comunicazione sono di natura
>> > privata e come tali sono da considerarsi riservate ed indirizzate
>> > esclusivamente ai destinatari indicati e per le finalità strettamente
>> > legate al relativo contenuto. Se avete ricevuto questo messaggio per
>> > errore, vi preghiamo di eliminarlo e di inviare una comunicazione
>> > all’indirizzo e-mail del mittente.
>> > >> --
>> > >> The information transmitted is intended only for the person or entity
>> > to which it is addressed and may contain confidential and/or privileged
>> > material. If you received this in error, please contact the sender and
>> > delete the material.
>> > >
>> > > _______________________________________________
>> > > srslte-users mailing list
>> > > srslte-users at lists.softwareradiosystems.com
>> > > http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>> >
>>
>> --
>> --
>> Le informazioni contenute nella presente comunicazione sono di natura
>> privata e come tali sono da considerarsi riservate ed indirizzate
>> esclusivamente ai destinatari indicati e per le finalità strettamente
>> legate al relativo contenuto. Se avete ricevuto questo messaggio per
>> errore, vi preghiamo di eliminarlo e di inviare una comunicazione
>> all’indirizzo e-mail del mittente.
>>
>> --
>> The information transmitted is
>> intended only for the person or entity to which it is addressed and may
>> contain confidential and/or privileged material. If you received this in
>> error, please contact the sender and delete the material.
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://www.softwareradiosystems.com/pipermail/srslte-users/attachments/20181015/f58d5c3a/attachment-0001.html>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> srslte-users mailing list
>> srslte-users at lists.softwareradiosystems.com
>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>
>>
>> ------------------------------
>>
>> End of srslte-users Digest, Vol 44, Issue 12
>> ********************************************
>
> _______________________________________________
> srslte-users mailing list
> srslte-users at lists.softwareradiosystems.com
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users