[srslte-users] Plain UL NAS: Authentication Failure

[putaogan]

Hi,Andre
you mean i should add two lines in the file in srsLTE/srsue/src/upper/nas.cc
+  ctxt.rx_count++;
+
I find the program in nas.cc and it seems it is different from what you say.
It is :
void nas::parse_authentication_request(uint32_t lcid, byte_buffer_t *pdu) {
  LIBLTE_MME_AUTHENTICATION_REQUEST_MSG_STRUCT auth_req;
  LIBLTE_MME_AUTHENTICATION_RESPONSE_MSG_STRUCT auth_res;


  nas_log->info("Received Authentication Request\n");
  liblte_mme_unpack_authentication_request_msg((LIBLTE_BYTE_MSG_STRUCT *) pdu, &auth_req);


  // Reuse the pdu for the response message
  pdu->reset();


  // Generate authentication response using RAND, AUTN & KSI-ASME
  uint16 mcc, mnc;
  mcc = rrc->get_mcc();
I attempt to add the two lines like this：
void nas::parse_authentication_request(uint32_t lcid, byte_buffer_t *pdu) {
  LIBLTE_MME_AUTHENTICATION_REQUEST_MSG_STRUCT auth_req;
  LIBLTE_MME_AUTHENTICATION_RESPONSE_MSG_STRUCT auth_res;


  nas_log->info("Received Authentication Request\n");
  liblte_mme_unpack_authentication_request_msg((LIBLTE_BYTE_MSG_STRUCT *) pdu, &auth_req);


  // Reuse the pdu for the response message
  pdu->reset();
  ctxt.rx_count++;

  // Generate authentication response using RAND, AUTN & KSI-ASME
  uint16 mcc, mnc;
  mcc = rrc->get_mcc();
But it does not work.
I do not know why it is.
What should i do?


Thanks,
Dongxu












At 2018-06-06 17:56:09, "Andre Puschmann" <andre.puschmann at softwareradiosystems.com> wrote:
>Hey,
>
>this is a bug in the current release that is fixed in 18.06 already,
>which will be available shortly. For the moment, you can add it manually
>if you wish.
>
>diff --git a/srsue/src/upper/nas.cc b/srsue/src/upper/nas.cc
>index 4df7d5c31..8bc8e5d12 100644
>--- a/srsue/src/upper/nas.cc
>+++ b/srsue/src/upper/nas.cc
>@@ -732,6 +732,8 @@ void nas::parse_authentication_request(uint32_t
>lcid, byte_buffer_t *pdu) {
>   // Deallocate PDU after parsing
>   pool->deallocate(pdu);
>
>+  ctxt.rx_count++;
>+
>   // Generate authentication response using RAND, AUTN & KSI-ASME
>   uint16 mcc, mnc;
>   mcc = rrc->get_mcc();
>
>
>Cheers
>Andre
>
>
>On 06/06/18 11:51, putaogan wrote:
>> Dear all，
>> Yesterday i succeeded in connecting my phone to srsepc and have access
>> to internet.
>> But today i try again and find something wrong.
>> I can find something in srsepc as follows:
>> /Received Attach Request /
>> /Attach Request -- IMSI-style attach request/
>> /Attach Request -- UE is already attached.Attach request -- IMSI:
>> 001010123456789/
>> /Attach request -- eNB-UE S1AP Id: 2, MME-UE S1AP Id: 2/
>> /Attach request -- Attach type: 2/
>> /Attach Request -- UE Network Capabilities EEA: 11110000/
>> /Attach Request -- UE Network Capabilities EIA: 01110000/
>> /Attach Request -- MS Network Capabilities Present: true/
>> /PDN Connectivity Request -- EPS Bearer Identity requested: 0/
>> /PDN Connectivity Request -- Procedure Transaction Id: 16/
>> /PDN Connectivity Request -- ESM Information Transfer requested: true/
>> /Downlink NAS: Sending Authentication Request/
>> /Plain UL NAS: Authentication Failure/
>> /Sequence number synch failure/
>> /Downlink NAS: Sent Authentication Request/
>> /DL NAS: Sent Downlink NAS Message. DL NAS Count=0, UL NAS count=1/
>> /DL NAS: MME UE S1AP id 2/
>> /Plain UL NAS: Authentication Failure/
>> /Sequence number synch failure/
>> /Downlink NAS: Sent Authentication Request/
>> /DL NAS: Sent Downlink NAS Message. DL NAS Count=0, UL NAS count=2/
>> /DL NAS: MME UE S1AP id 2/
>> /Received UE Context Release Request. MME-UE S1AP Id 2/
>> /UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 2/
>> /UE is ECM IDLE./
>> The epc.log is in the attachment.
>> If angone knows the reason about this,please let me know.
>> 
>> Thanks.
>> Dongxu
>> 
>> 
>> /
>> /
>> /
>> /
>> 
>> 
>> 
>> 
>> 
>>  
>> 
>> 
>> 
>> _______________________________________________
>> 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/20180607/174ab070/attachment.htm>