[srslte-users] SRSUE cannot send/recieve data

Tošovský Bohumil Bohumil.Tosovsky at nordictelecom.cz
Mon Dec 10 14:52:17 UTC 2018


Hello,

The problem was caused by the only "allowed ciphered traffic only"  on the eNodeB. When I disabled cipherng on the eNodeB, everything works well.

Is there already supported any other algorithms than EEA0 and EIA0  on the SRS_UE ?


Thanks 

Bohumil Tosovsky



-----Original Message-----
From: Tošovský Bohumil 
Sent: Friday, November 30, 2018 7:38 PM
To: Andre Puschmann <andre.puschmann at softwareradiosystems.com>; srslte-users at lists.softwareradiosystems.com
Subject: RE: [srslte-users] SRSUE cannot send/recieve data

Hello,

Please find attached logs, little update: the data are  passed to the Bearer, but when I trace on the S1 interface, they are corrupted in the GTP tunnel.

16:18:31.004757 [PHY_LIB] [I] [03388]  Searching UL C-RNTI in 0 ue locations
16:18:31.004979 [GW  ] [I] TX PDU
             0000: 45 00 00 54 f6 1d 40 00 40 01 3f a1 64 42 90 98 
             0010: 08 08 08 08 08 00 ff 2a 5f 3f 00 02 c7 54 01 5c 
             0020: 00 00 00 00 12 10 00 00 00 00 00 00 10 11 12 13 
             0030: 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23
16:18:31.005004 [PDCP] [I] TX DRB1 SDU, SN: 1, do_integrity = false, do_encryption = true
             0000: 45 00 00 54 f6 1d 40 00 40 01 3f a1 64 42 90 98 
             0010: 08 08 08 08 08 00 ff 2a 5f 3f 00 02 c7 54 01 5c 
             0020: 00 00 00 00 12 10 00 00 00 00 00 00 10 11 12 13 
             0030: 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23
16:18:31.005023 [PDCP] [I] TX DRB1 SDU (encrypted)
             0000: 80 01 c0 e5 aa 3a 8c 99 97 ce b5 13 84 9a 49 22 
             0010: af 2b 8c 00 8d 85 3a 35 53 29 85 e1 09 7d 79 c1 
             0020: 37 f5 e8 d4 13 ae ba 4a 54 5e b4 83 14 5b 9b 48 
             0030: 0d 44 a8 c2 00 c2 dd c5 b2 93 a1 d1 4e d0 e7 04
16:18:31.005039 [RLC ] [I] DRB1 Tx SDU (86 B, tx_sdu_queue_len=1)
             0000: 80 01 c0 e5 aa 3a 8c 99 97 ce b5 13 84 9a 49 22 
             0010: af 2b 8c 00 8d 85 3a 35 53 29 85 e1 09 7d 79 c1 
             0020: 37 f5 e8 d4 13 ae ba 4a 54 5e b4 83 14 5b 9b 48 
             0030: 0d 44 a8 c2 00 c2 dd c5 b2 93 a1 d1 4e d0 e7 04
16:18:31.005051 [PHY_LIB] [I] [03388]  SYNC TRACK: sf_idx=8, ret=1, next_state=1
16:18:31.005168 [PHY_LIB] [I] [03389]  Decoded CFI=2 with correlation 41.92, sf_idx=8

Here is the icmp packet sent via tun.

Many Thanks

B.T.


 
-----Original Message-----
From: Andre Puschmann <andre.puschmann at softwareradiosystems.com>
Sent: Friday, November 30, 2018 4:19 PM
To: Tošovský Bohumil <Bohumil.Tosovsky at nordictelecom.cz>; srslte-users at lists.softwareradiosystems.com
Subject: Re: [srslte-users] SRSUE cannot send/recieve data

please send full logs.

On 28/11/18 19:44, Tošovský Bohumil wrote:
> Hello,
> 
>  
> 
> We are trying SRS_UE running with B210 with real eNodeB equipment, UE 
> performs correct RRC Connection and Attach procedure, receive IP 
> address, but when I cannot  send/receive data.
> 
> In the UE.log I found this:
> 
>  
> 
> 15:34:04.945625 [RRC ] [D] State CONNECTED
> 
> 15:34:04.946082 [GW  ] [D] Read 220 bytes from TUN fd=17, idx=0
> 
> 15:34:04.946091 [GW  ] [I] TX PDU
> 
>              0000: 45 00 00 dc ac 0d 40 00 40 06 fd 01 c0 a8 01 ae
> 
>              0010: 4e 88 80 2e 83 ea 06 bb 60 3a fa 40 41 2a 0f 65
> 
>              0020: 80 18 00 1e 59 2e 00 00 01 01 08 0a 01 13 6c 1b
> 
>              0030: 4f d9 07 e4 00 a8 00 01 1a 2b 3c 4d 00 07 00 00
> 
> 15:34:04.946109 [GW  ] [I] LCID=3 not active, requesting NAS attach
> (0/40)
> 
> 15:34:04.946116 [NAS ] [I] Attach Request
> 
> 15:34:04.946123 [NAS ] [I] NAS is already registered and RRC connected
> 
>  
> 
> On the S1 interface I can see packets in the GTP tunnel, but they are 
> corrupted (Incorrect IP headers,length… )
> 
>  
> 
> Thanks Bohumil
> 
> 
> _______________________________________________
> srslte-users mailing list
> srslte-users at lists.softwareradiosystems.com
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> 





More information about the srsran-users mailing list