[srslte-users] Internet Connectivity Extremely Slow

Francisco Paisana francisco.paisana at softwareradiosystems.com
Mon Jul 6 20:55:36 UTC 2020 

Hey Bennett,

Are you sure the enb.log and enb.pcap are relative to the same run? I need
to match the results between the two. If not, can you send a new log/pcap?

Also, can you set the phy log to INFO by passing the command line arg
"--log.phy_level=info"? Otherwise, the log files become gigantic. Also,
after the first Reestablishment Reject, you can stop the enb, as the logs
after that are not relevant.

Kind Regards,
Francisco


On Mon, Jul 6, 2020 at 4:19 PM Bennett Gogarty <thetanu861 at gmail.com> wrote:

> Sorry, here is the enb.log file.
>  enb.log
> <https://drive.google.com/file/d/1E1AD9ZRDdkdo5jak4NMurNs0e7c7QOaI/view?usp=drive_web>
>
> On Fri, Jul 3, 2020 at 10:47 AM Bennett Gogarty <thetanu861 at gmail.com>
> wrote:
>
>> Here are the DEBUG enb.log and pcap files. It won't let me send the
>> attachments to the mailing list unfortunately.
>>
>> On Fri, Jul 3, 2020 at 10:22 AM Bennett Gogarty <thetanu861 at gmail.com>
>> wrote:
>>
>>> Francisco,
>>> I will get these over to you shortly. I was out of town for a few days
>>> so i'll get this done in a bit. I will also keep cc'ing the mailing list as
>>> well. Thanks for all your help on this!
>>>
>>> On Mon, Jun 29, 2020 at 2:49 PM Francisco Paisana <
>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>
>>>> Hey Bennett,
>>>>
>>>> This is very weird. The eNB is sending the SN=5, but it is not
>>>> receiving the ACK from the UE.
>>>>
>>>> Could you send the enb logs in DEBUG level again, but this time, could
>>>> you also include the respective enb.pcap (you can enable it via the
>>>> enb.conf file).
>>>>
>>>> Kind Regards,
>>>> Francisco
>>>>
>>>>
>>>> On Mon, Jun 29, 2020 at 7:00 PM Francisco Paisana <
>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>
>>>>> Hey Bennett,
>>>>>
>>>>> It was just letting the ping on in what's about to become the UE IP
>>>>> (default: 192.168.10.2), so that the eNB doesn't release the UE due to
>>>>> inactivity, after the UE establishes the connection. But looking at the
>>>>> latest logs, I don't think this will solve anything. I will try to come
>>>>> back to you, once I find a fix.
>>>>>
>>>>> Btw, I would suggest keeping the mailing list in Cc, as other people
>>>>> may know how to fix this issue.
>>>>>
>>>>> Kind Regards,
>>>>> Francisco
>>>>>
>>>>>
>>>>> On Fri, Jun 26, 2020 at 5:01 PM Bennett Gogarty <thetanu861 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Also, how do i send a ping in the DL direction before connecting? try
>>>>>> to ping the gateway?
>>>>>>
>>>>>> On Fri, Jun 26, 2020 at 11:39 AM Bennett Gogarty <
>>>>>> thetanu861 at gmail.com> wrote:
>>>>>>
>>>>>>> Sure, here are the logs with DEBUG level.
>>>>>>>  enb.log
>>>>>>> <https://drive.google.com/file/d/1zBUBZ9yZ3vrK3gwtIaueSnGDzqhUq72A/view?usp=drive_web>
>>>>>>>
>>>>>>> On Fri, Jun 26, 2020 at 8:13 AM Francisco Paisana <
>>>>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>>>>
>>>>>>>> Without the earlier "fixes", can you test again but with the eNB
>>>>>>>> MAC log level set to DEBUG this time? Thanks
>>>>>>>>
>>>>>>>> Kind Regards,
>>>>>>>> Francisco
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Jun 26, 2020 at 10:31 AM Francisco Paisana <
>>>>>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>>>>>
>>>>>>>>> Hey Bennett,
>>>>>>>>>
>>>>>>>>> Let's include the rest of the mailing list, as someone might have
>>>>>>>>> an answer.
>>>>>>>>>
>>>>>>>>> Weird that the phone couldn't connect to 25 PRBs. Observations
>>>>>>>>> regarding the enb logs:
>>>>>>>>> - the eNB is receiving a lot of scheduling requests from the UE.
>>>>>>>>> e.g.
>>>>>>>>>
>>>>>>>>>> 23:21:07.574190 [PHY0] [I] [ 3120] PUCCH: cc=0; rnti=0x46, f=2,
>>>>>>>>>> n_pucch=0, dmrs_corr=0.986, corr=0.996, *sr=yes*, cqi=15
>>>>>>>>>
>>>>>>>>> It then schedules the UL grant
>>>>>>>>>
>>>>>>>>>> 23:21:07.574242 [MAC ] [I] [ 3120] SCHED: *UL tx* rnti=0x46,
>>>>>>>>>> cc=0, pid=0, dci=(1,0), prb=(2,22), n_rtx=0, tbs=389, bsr=0 (512-389)
>>>>>>>>>
>>>>>>>>>  It is able to decode the UL data sent by the UE
>>>>>>>>>
>>>>>>>>>> 23:21:07.582289 [PHY0] [I] [ 3128] PUSCH: cc=0, rnti=0x46,
>>>>>>>>>> rb=(2,21), nof_re=2880, tbs=389, mod=2, rv=0, *crc=OK*,
>>>>>>>>>> avg_iter=1.0, snr=13.0 dB, epre=5.6 dBfs, ta=0.1 us, t=161 us
>>>>>>>>>
>>>>>>>>> but no data is being forwarded to the upper layers (e.g. RLC).
>>>>>>>>> Eventually the RRC inactivity timer expires.
>>>>>>>>> - Also after being provided with a scheduling request, the UE is
>>>>>>>>> not updating any buffer status report. It is almost as if it doesn't have
>>>>>>>>> data to transmit, and is just playing with the eNB.
>>>>>>>>>
>>>>>>>>> Can you experiment with letting a ping on in the DL direction
>>>>>>>>> before connecting the phone? Maybe this will stop the inactivity timer from
>>>>>>>>> expiring.
>>>>>>>>>
>>>>>>>>> Can you also experiment with setting to "> 0" instead of ">64",
>>>>>>>>> the following check in the file "srsenb/src/stack/mac/ue.cc" :
>>>>>>>>>
>>>>>>>>> if (mac_msg_ul.get()->get_payload_size() > 64) { // do not count RLC status messages only
>>>>>>>>>   rrc->set_activity_user(rnti);
>>>>>>>>>   log_h->debug("UL activity rnti=0x%x, n_bytes=%d\n", rnti, nof_bytes);
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> Kind Regards,
>>>>>>>>> Francisco
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Jun 26, 2020 at 12:33 AM Bennett Gogarty <
>>>>>>>>> thetanu861 at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Francisco,
>>>>>>>>>>
>>>>>>>>>> Here is the output from srsenb when i run with 25 PRB, I will
>>>>>>>>>> also include the log file. I still cannot get access out from the phone.
>>>>>>>>>> ---  Software Radio Systems LTE eNodeB  ---
>>>>>>>>>>
>>>>>>>>>> Reading configuration file /etc/srslte/enb.conf...
>>>>>>>>>>
>>>>>>>>>> Built in Release mode using commit c892ae56b on branch master.
>>>>>>>>>>
>>>>>>>>>> /home/lte/srsLTE/srsenb/src/enb_cfg_parser.cc.883: Force DL
>>>>>>>>>> EARFCN for cell PCI=1 to 800
>>>>>>>>>>
>>>>>>>>>> Opening 1 channels in RF device=default with args=default
>>>>>>>>>> Soapy has found device #0: addr=1d50:6108, driver=lime,
>>>>>>>>>> label=LimeSDR-USB [USB 3.0] 90706024F152C, media=USB 3.0, module=FX3,
>>>>>>>>>> name=LimeSDR-USB, serial=00090706024F152C,
>>>>>>>>>> Selecting Soapy device: 0
>>>>>>>>>> [INFO] Make connection: 'LimeSDR-USB [USB 3.0] 90706024F152C'
>>>>>>>>>> [INFO] Reference clock 30.72 MHz
>>>>>>>>>> [INFO] Device name: LimeSDR-USB
>>>>>>>>>> [INFO] Reference: 30.72 MHz
>>>>>>>>>> [INFO] LMS7002M calibration values caching Disable
>>>>>>>>>> Setting up Rx stream with 1 channel(s)
>>>>>>>>>> Setting up Tx stream with 1 channel(s)
>>>>>>>>>> Available device sensors:
>>>>>>>>>>  - clock_locked
>>>>>>>>>>  - lms7_temp
>>>>>>>>>> Available sensors for Rx channel 0:
>>>>>>>>>>  - lo_locked
>>>>>>>>>> [INFO] Tx calibration finished
>>>>>>>>>> [INFO] Rx calibration finished
>>>>>>>>>> State of gain elements for Rx channel 0 (AGC not supported):
>>>>>>>>>>  - TIA: 9.00 dB
>>>>>>>>>>  - LNA: 30.00 dB
>>>>>>>>>>  - PGA: -4.00 dB
>>>>>>>>>> State of gain elements for Tx channel 0 (AGC not supported):
>>>>>>>>>>  - PAD: 45.00 dB
>>>>>>>>>>  - IAMP: 0.00 dB
>>>>>>>>>> Rx antenna set to LNAL
>>>>>>>>>> Tx antenna set to BAND1
>>>>>>>>>>
>>>>>>>>>> ==== eNodeB started ===
>>>>>>>>>> Type <t> to view trace
>>>>>>>>>> Setting frequency: DL=1950.0 Mhz, UL=1870.0 MHz for cc_idx=0
>>>>>>>>>> [WARNING] L
>>>>>>>>>> RACH:  tti=1751, preamble=35, offset=1, temp_crnti=0x46
>>>>>>>>>> RACH:  tti=6271, preamble=26, offset=1, temp_crnti=0x47
>>>>>>>>>> Disconnecting rnti=0x46.
>>>>>>>>>> RACH:  tti=7021, preamble=29, offset=1, temp_crnti=0x48
>>>>>>>>>> Disconnecting rnti=0x48.
>>>>>>>>>> RACH:  tti=7151, preamble=35, offset=1, temp_crnti=0x49
>>>>>>>>>> Disconnecting rnti=0x47.
>>>>>>>>>> RACH:  tti=8011, preamble=6, offset=1, temp_crnti=0x4a
>>>>>>>>>> Disconnecting rnti=0x4a.
>>>>>>>>>> RACH:  tti=8141, preamble=21, offset=1, temp_crnti=0x4b
>>>>>>>>>> Disconnecting rnti=0x49.
>>>>>>>>>> RACH:  tti=8941, preamble=27, offset=1, temp_crnti=0x4c
>>>>>>>>>> Disconnecting rnti=0x4c.
>>>>>>>>>> RACH:  tti=9071, preamble=11, offset=1, temp_crnti=0x4d
>>>>>>>>>> Disconnecting rnti=0x4b.
>>>>>>>>>> RACH:  tti=9831, preamble=27, offset=1, temp_crnti=0x4e
>>>>>>>>>> Disconnecting rnti=0x4e.
>>>>>>>>>> RACH:  tti=10001, preamble=2, offset=1, temp_crnti=0x4f
>>>>>>>>>> Disconnecting rnti=0x4d.
>>>>>>>>>> RACH:  tti=4351, preamble=7, offset=1, temp_crnti=0x50
>>>>>>>>>> Disconnecting rnti=0x4f.
>>>>>>>>>> RACH:  tti=5161, preamble=28, offset=1, temp_crnti=0x51
>>>>>>>>>> Disconnecting rnti=0x51.
>>>>>>>>>> RACH:  tti=5301, preamble=15, offset=1, temp_crnti=0x52
>>>>>>>>>> Disconnecting rnti=0x50.
>>>>>>>>>> RACH:  tti=8391, preamble=25, offset=1, temp_crnti=0x53
>>>>>>>>>> Disconnecting rnti=0x52.
>>>>>>>>>> RACH:  tti=9101, preamble=12, offset=1, temp_crnti=0x54
>>>>>>>>>> Disconnecting rnti=0x54.
>>>>>>>>>> RACH:  tti=9271, preamble=23, offset=1, temp_crnti=0x55
>>>>>>>>>> Disconnecting rnti=0x53.
>>>>>>>>>> RACH:  tti=10021, preamble=49, offset=1, temp_crnti=0x56
>>>>>>>>>> Disconnecting rnti=0x56.
>>>>>>>>>> RACH:  tti=10191, preamble=5, offset=1, temp_crnti=0x57
>>>>>>>>>> Disconnecting rnti=0x55.
>>>>>>>>>> RACH:  tti=4481, preamble=0, offset=1, temp_crnti=0x58
>>>>>>>>>> Disconnecting rnti=0x57.
>>>>>>>>>> RACH:  tti=9011, preamble=38, offset=1, temp_crnti=0x59
>>>>>>>>>> Disconnecting rnti=0x58.
>>>>>>>>>> RACH:  tti=3311, preamble=14, offset=1, temp_crnti=0x5a
>>>>>>>>>> Disconnecting rnti=0x59.
>>>>>>>>>> RACH:  tti=4021, preamble=21, offset=1, temp_crnti=0x5b
>>>>>>>>>> Disconnecting rnti=0x5b.
>>>>>>>>>> RACH:  tti=4191, preamble=19, offset=1, temp_crnti=0x5c
>>>>>>>>>> Disconnecting rnti=0x5a.
>>>>>>>>>>
>>>>>>>>>> On Mon, Jun 22, 2020 at 7:48 PM Bennett Gogarty <
>>>>>>>>>> thetanu861 at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I was still seeing the "L" in the screen even after scaling the
>>>>>>>>>>> governor. I changed the number of PRB's to 25, but now the phone doesn't
>>>>>>>>>>> seem to want to connect to the network. I've put the phone into airplane
>>>>>>>>>>> mode and then take it out several times but the phone doesn't connect. When
>>>>>>>>>>> I change the PRB back to 50 the phone connects.
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Jun 18, 2020 at 2:47 PM Francisco Paisana <
>>>>>>>>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> The number of PRBs in the enb.conf. After setting the scaling
>>>>>>>>>>>> governor, do you still see "L" in the screen?
>>>>>>>>>>>>
>>>>>>>>>>>> Kind Regards,
>>>>>>>>>>>> Francisco
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Jun 18, 2020 at 6:56 PM Bennett Gogarty <
>>>>>>>>>>>> thetanu861 at gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Ok I set the CPU governor to performance and I still have the
>>>>>>>>>>>>> issue of no internet connectivity. You mentioned reducing the bandwidth...
>>>>>>>>>>>>> bandwidth for what specifically? CPU bandwidth or a setting in the enb.conf
>>>>>>>>>>>>> file?
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Jun 18, 2020 at 1:11 PM Francisco Paisana <
>>>>>>>>>>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> To check the current governor, run in the terminal the
>>>>>>>>>>>>>> following command:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> To change it to performance, run:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> echo performance | sudo tee
>>>>>>>>>>>>>>> /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Kind Regards,
>>>>>>>>>>>>>> Francisco
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Thu, Jun 18, 2020 at 3:39 PM Bennett Gogarty <
>>>>>>>>>>>>>> thetanu861 at gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> How do i check the scaling governor to see if it's in
>>>>>>>>>>>>>>> performance mode?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Thu, Jun 18, 2020 at 5:15 AM Francisco Paisana <
>>>>>>>>>>>>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Can you check your scaling governor, and set it to
>>>>>>>>>>>>>>>> performance? If it was already in performance mode, try reducing the
>>>>>>>>>>>>>>>> bandwidth. I want to confirm that those lates are not causing your phone to
>>>>>>>>>>>>>>>> go out of sync.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>> Francisco
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, 17 Jun 2020, 17:16 Bennett Gogarty, <
>>>>>>>>>>>>>>>> thetanu861 at gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> here is the console text for enb:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ---  Software Radio Systems LTE eNodeB  ---
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Reading configuration file /etc/srslte/enb.conf...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Built in Release mode using commit c892ae56b on branch
>>>>>>>>>>>>>>>>> master.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> /home/lte/srsLTE/srsenb/src/enb_cfg_parser.cc.883: Force
>>>>>>>>>>>>>>>>> DL EARFCN for cell PCI=1 to 800
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Opening 1 channels in RF device=default with args=default
>>>>>>>>>>>>>>>>> Soapy has found device #0: addr=1d50:6108, driver=lime,
>>>>>>>>>>>>>>>>> label=LimeSDR-USB [USB 3.0] 90726074E263C, media=USB 3.0, module=FX3,
>>>>>>>>>>>>>>>>> name=LimeSDR-USB, serial=00090726074E263C,
>>>>>>>>>>>>>>>>> Selecting Soapy device: 0
>>>>>>>>>>>>>>>>> [INFO] Make connection: 'LimeSDR-USB [USB 3.0]
>>>>>>>>>>>>>>>>> 90726074E263C'
>>>>>>>>>>>>>>>>> [INFO] Reference clock 30.72 MHz
>>>>>>>>>>>>>>>>> [INFO] Device name: LimeSDR-USB
>>>>>>>>>>>>>>>>> [INFO] Reference: 30.72 MHz
>>>>>>>>>>>>>>>>> [INFO] LMS7002M calibration values caching Disable
>>>>>>>>>>>>>>>>> Setting up Rx stream with 1 channel(s)
>>>>>>>>>>>>>>>>> Setting up Tx stream with 1 channel(s)
>>>>>>>>>>>>>>>>> Available device sensors:
>>>>>>>>>>>>>>>>>  - clock_locked
>>>>>>>>>>>>>>>>>  - lms7_temp
>>>>>>>>>>>>>>>>> Available sensors for Rx channel 0:
>>>>>>>>>>>>>>>>>  - lo_locked
>>>>>>>>>>>>>>>>> [INFO] Tx calibration finished
>>>>>>>>>>>>>>>>> [INFO] Rx calibration finished
>>>>>>>>>>>>>>>>> State of gain elements for Rx channel 0 (AGC not
>>>>>>>>>>>>>>>>> supported):
>>>>>>>>>>>>>>>>>  - TIA: 9.00 dB
>>>>>>>>>>>>>>>>>  - LNA: 30.00 dB
>>>>>>>>>>>>>>>>>  - PGA: -4.00 dB
>>>>>>>>>>>>>>>>> State of gain elements for Tx channel 0 (AGC not
>>>>>>>>>>>>>>>>> supported):
>>>>>>>>>>>>>>>>>  - PAD: 45.00 dB
>>>>>>>>>>>>>>>>>  - IAMP: 0.00 dB
>>>>>>>>>>>>>>>>> Rx antenna set to LNAL
>>>>>>>>>>>>>>>>> Tx antenna set to BAND1
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ==== eNodeB started ===
>>>>>>>>>>>>>>>>> Type <t> to view trace
>>>>>>>>>>>>>>>>> Setting frequency: DL=1950.0 Mhz, UL=1870.0 MHz for
>>>>>>>>>>>>>>>>> cc_idx=0
>>>>>>>>>>>>>>>>> [WARNING] L
>>>>>>>>>>>>>>>>> [WARNING] L
>>>>>>>>>>>>>>>>> LRACH:  tti=9891, preamble=39, offset=0, temp_crnti=0x46
>>>>>>>>>>>>>>>>> RACH:  tti=4181, preamble=28, offset=0, temp_crnti=0x47
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x46.
>>>>>>>>>>>>>>>>> RACH:  tti=4851, preamble=22, offset=0, temp_crnti=0x48
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x48.
>>>>>>>>>>>>>>>>> RACH:  tti=5021, preamble=17, offset=0, temp_crnti=0x49
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x47.
>>>>>>>>>>>>>>>>> RACH:  tti=6681, preamble=16, offset=0, temp_crnti=0x4a
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x4a.
>>>>>>>>>>>>>>>>> RACH:  tti=6831, preamble=14, offset=0, temp_crnti=0x4b
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x49.
>>>>>>>>>>>>>>>>> RACH:  tti=8351, preamble=32, offset=0, temp_crnti=0x4c
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x4c.
>>>>>>>>>>>>>>>>> RACH:  tti=8501, preamble=20, offset=0, temp_crnti=0x4d
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x4b.
>>>>>>>>>>>>>>>>> RACH:  tti=9661, preamble=25, offset=0, temp_crnti=0x4e
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x4e.
>>>>>>>>>>>>>>>>> RACH:  tti=9831, preamble=16, offset=0, temp_crnti=0x4f
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x4d.
>>>>>>>>>>>>>>>>> RACH:  tti=601, preamble=40, offset=0, temp_crnti=0x50
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x50.
>>>>>>>>>>>>>>>>> RACH:  tti=751, preamble=1, offset=0, temp_crnti=0x51
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x4f.
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x51.
>>>>>>>>>>>>>>>>> RACH:  tti=2341, preamble=13, offset=0, temp_crnti=0x52
>>>>>>>>>>>>>>>>> RACH:  tti=2341, preamble=16, offset=5, temp_crnti=0x53
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x53.
>>>>>>>>>>>>>>>>> RACH:  tti=6911, preamble=31, offset=0, temp_crnti=0x54
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x52.
>>>>>>>>>>>>>>>>> RACH:  tti=7881, preamble=50, offset=0, temp_crnti=0x55
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x55.
>>>>>>>>>>>>>>>>> RACH:  tti=8051, preamble=29, offset=0, temp_crnti=0x56
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x54.
>>>>>>>>>>>>>>>>> RACH:  tti=9141, preamble=36, offset=0, temp_crnti=0x57
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x57.
>>>>>>>>>>>>>>>>> RACH:  tti=9311, preamble=37, offset=0, temp_crnti=0x58
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x56.
>>>>>>>>>>>>>>>>> RACH:  tti=651, preamble=17, offset=0, temp_crnti=0x59
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x59.
>>>>>>>>>>>>>>>>> RACH:  tti=781, preamble=42, offset=0, temp_crnti=0x5a
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x58.
>>>>>>>>>>>>>>>>> RACH:  tti=1251, preamble=25, offset=0, temp_crnti=0x5b
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x5a.
>>>>>>>>>>>>>>>>> RACH:  tti=2721, preamble=10, offset=0, temp_crnti=0x5c
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x5c.
>>>>>>>>>>>>>>>>> RACH:  tti=2891, preamble=29, offset=0, temp_crnti=0x5d
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x5b.
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x5d.
>>>>>>>>>>>>>>>>> RACH:  tti=3031, preamble=44, offset=0, temp_crnti=0x5e
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x5e.
>>>>>>>>>>>>>>>>> RACH:  tti=3271, preamble=24, offset=0, temp_crnti=0x5f
>>>>>>>>>>>>>>>>> RACH:  tti=7801, preamble=16, offset=0, temp_crnti=0x60
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x5f.
>>>>>>>>>>>>>>>>> RACH:  tti=8451, preamble=6, offset=0, temp_crnti=0x61
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x61.
>>>>>>>>>>>>>>>>> RACH:  tti=8621, preamble=47, offset=0, temp_crnti=0x62
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x60.
>>>>>>>>>>>>>>>>> RACH:  tti=9361, preamble=50, offset=0, temp_crnti=0x63
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x63.
>>>>>>>>>>>>>>>>> RACH:  tti=9531, preamble=49, offset=0, temp_crnti=0x64
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x62.
>>>>>>>>>>>>>>>>> RACH:  tti=121, preamble=27, offset=0, temp_crnti=0x65
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x65.
>>>>>>>>>>>>>>>>> RACH:  tti=291, preamble=1, offset=0, temp_crnti=0x66
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x64.
>>>>>>>>>>>>>>>>> RACH:  tti=1221, preamble=45, offset=0, temp_crnti=0x67
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x67.
>>>>>>>>>>>>>>>>> RACH:  tti=1371, preamble=35, offset=0, temp_crnti=0x68
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x66.
>>>>>>>>>>>>>>>>> libusb: error [udev_hotplug_event] ignoring udev action
>>>>>>>>>>>>>>>>> bind
>>>>>>>>>>>>>>>>> [WARNING] L
>>>>>>>>>>>>>>>>> libusb: error [udev_hotplug_event] ignoring udev action
>>>>>>>>>>>>>>>>> bind
>>>>>>>>>>>>>>>>> libusb: error [udev_hotplug_event] ignoring udev action
>>>>>>>>>>>>>>>>> bind
>>>>>>>>>>>>>>>>> RACH:  tti=8301, preamble=47, offset=0, temp_crnti=0x69
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x69.
>>>>>>>>>>>>>>>>> RACH:  tti=8401, preamble=22, offset=0, temp_crnti=0x6a
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x68.
>>>>>>>>>>>>>>>>> RACH:  tti=9701, preamble=25, offset=0, temp_crnti=0x6b
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x6b.
>>>>>>>>>>>>>>>>> RACH:  tti=9911, preamble=11, offset=29, temp_crnti=0x6c
>>>>>>>>>>>>>>>>> RACH:  tti=9911, preamble=19, offset=0, temp_crnti=0x6d
>>>>>>>>>>>>>>>>> RACH:  tti=9911, preamble=28, offset=15, temp_crnti=0x6e
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x6c.
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x6e.
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x6a.
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x6d.
>>>>>>>>>>>>>>>>> RACH:  tti=10111, preamble=43, offset=0, temp_crnti=0x6f
>>>>>>>>>>>>>>>>> RACH:  tti=831, preamble=43, offset=0, temp_crnti=0x70
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x6f.
>>>>>>>>>>>>>>>>> RACH:  tti=1331, preamble=35, offset=0, temp_crnti=0x71
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x70.
>>>>>>>>>>>>>>>>> RACH:  tti=2111, preamble=10, offset=0, temp_crnti=0x72
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x71.
>>>>>>>>>>>>>>>>> RACH:  tti=4951, preamble=2, offset=0, temp_crnti=0x73
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x72.
>>>>>>>>>>>>>>>>> RACH:  tti=5741, preamble=6, offset=0, temp_crnti=0x74
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x74.
>>>>>>>>>>>>>>>>> RACH:  tti=5871, preamble=22, offset=0, temp_crnti=0x75
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x73.
>>>>>>>>>>>>>>>>> RACH:  tti=7751, preamble=43, offset=0, temp_crnti=0x76
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x76.
>>>>>>>>>>>>>>>>> RACH:  tti=7921, preamble=8, offset=0, temp_crnti=0x77
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x75.
>>>>>>>>>>>>>>>>> RACH:  tti=9011, preamble=47, offset=0, temp_crnti=0x78
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x78.
>>>>>>>>>>>>>>>>> RACH:  tti=9201, preamble=29, offset=0, temp_crnti=0x79
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x77.
>>>>>>>>>>>>>>>>> RACH:  tti=3471, preamble=17, offset=0, temp_crnti=0x7a
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x79.
>>>>>>>>>>>>>>>>> RACH:  tti=8001, preamble=10, offset=0, temp_crnti=0x7b
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x7a.
>>>>>>>>>>>>>>>>> RACH:  tti=9211, preamble=2, offset=0, temp_crnti=0x7c
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x7c.
>>>>>>>>>>>>>>>>> RACH:  tti=9381, preamble=29, offset=0, temp_crnti=0x7d
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x7b.
>>>>>>>>>>>>>>>>> RACH:  tti=321, preamble=37, offset=0, temp_crnti=0x7e
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x7e.
>>>>>>>>>>>>>>>>> RACH:  tti=481, preamble=21, offset=5, temp_crnti=0x7f
>>>>>>>>>>>>>>>>> RACH:  tti=501, preamble=1, offset=0, temp_crnti=0x80
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x7f.
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x7d.
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x80.
>>>>>>>>>>>>>>>>> RACH:  tti=651, preamble=22, offset=0, temp_crnti=0x81
>>>>>>>>>>>>>>>>> RACH:  tti=2611, preamble=13, offset=0, temp_crnti=0x82
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x82.
>>>>>>>>>>>>>>>>> RACH:  tti=2781, preamble=37, offset=0, temp_crnti=0x83
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x81.
>>>>>>>>>>>>>>>>> RACH:  tti=7311, preamble=12, offset=0, temp_crnti=0x84
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x83.
>>>>>>>>>>>>>>>>> RACH:  tti=8341, preamble=43, offset=0, temp_crnti=0x85
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x85.
>>>>>>>>>>>>>>>>> RACH:  tti=8471, preamble=35, offset=0, temp_crnti=0x86
>>>>>>>>>>>>>>>>> Disconnecting rnti=0x84.
>>>>>>>>>>>>>>>>> User 0x86 connected
>>>>>>>>>>>>>>>>> SCTP Association Shutdown. Association: 0
>>>>>>>>>>>>>>>>> connect(): Connection refused
>>>>>>>>>>>>>>>>> Failed to initiate SCTP socket. Attempting reconnection in
>>>>>>>>>>>>>>>>> 10 seconds   <<<this is where i hit ctrl-c to kill the scan
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Wed, Jun 17, 2020 at 11:51 AM Francisco Paisana <
>>>>>>>>>>>>>>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Something seems wrong with your UL channel. The SNR
>>>>>>>>>>>>>>>>>> quickly drops to zero. Can you also send the enb console text?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Kind Regards,
>>>>>>>>>>>>>>>>>> Francisco
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Wed, Jun 17, 2020 at 3:32 PM Bennett Gogarty <
>>>>>>>>>>>>>>>>>> thetanu861 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Here are the logs for the epc and enb. I'm not using the
>>>>>>>>>>>>>>>>>>> srsue software, I have a Samsung S7 Edge connected the enb. Has this
>>>>>>>>>>>>>>>>>>> software been successfully tested against Samsung devices?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Wed, Jun 17, 2020 at 6:46 AM Francisco Paisana <
>>>>>>>>>>>>>>>>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hey Bennett,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Can you send the enb/epc/ue logs at info level?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Kind Regards,
>>>>>>>>>>>>>>>>>>>> Francisco
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Wed, Jun 17, 2020 at 11:16 AM Bennett Gogarty <
>>>>>>>>>>>>>>>>>>>> thetanu861 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hello All,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> I have a phone connected to srsENB and I pull an IP
>>>>>>>>>>>>>>>>>>>>> address. I can ping both the gateway and 8.8.8.8, but it is extremely slow.
>>>>>>>>>>>>>>>>>>>>> When I ping either the GW or DNS I will get about two responses in about 10
>>>>>>>>>>>>>>>>>>>>> minutes. Has anyone else out there experienced this issue? I am connected
>>>>>>>>>>>>>>>>>>>>> in with no issues, I just can't browse out to the internet due to the
>>>>>>>>>>>>>>>>>>>>> slowness. Any workarounds or other ideas I can try?
>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>> 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/20200706/c8ef6dfc/attachment.htm>

More information about the srsran-users mailing list