[srslte-users] Trouble connecting commersial UE (and some basic questions..)

Pedro Alvarez pedro.alvarez at softwareradiosystems.com
Thu Apr 23 17:00:58 UTC 2020


It seems like your dongle is requesting IPv6 connectivity, but srsEPC
does not support that at the moment.
The UE then gets stuck sending PDN connectivity requests just for the
IPv6 networks.

Can you access the APN settings in the dongle? And in the APN Protocol
select IPv4, instead of IPv4v6?

On Thu, Apr 23, 2020 at 4:38 PM Gunnar Kulbotten <gkulbotten at gmail.com> wrote:
>
> Thanks!
> Here is the epc.pcap file.
>
> tor. 23. apr. 2020 kl. 17:18 skrev Pedro Alvarez <pedro.alvarez at softwareradiosystems.com>:
>>
>> Can you share the epc.pcap please?
>> It might still be an APN issue, it would be nice to see the actual
>> messages going around.
>>
>> On Thu, Apr 23, 2020 at 12:31 PM Gunnar Kulbotten <gkulbotten at gmail.com> wrote:
>> >
>> > I got a small step closer to get this working today! One problem is that my Quectel LTE modem won`t register to the srsLTE network. It is connected to a windows-pc. The modem gets ip 172.16.0.2 from the srsLTE-network. I put this address as gateway in the windows-pc network properties, and 17.16.0.10 as ip-address. This actually worked for little while, and I could ping the enodeb/epc-pc from the windows-pc! Then the status in windows chenged to "Disconnected", and the connection was lost. It reappeared for a short while, and was lost again.
>> >
>> > I got a new error message from the srsepc terminal window:
>> >
>> > UL NAS: Received Attach Complete
>> > Unpacked Attached Complete Message. IMSI 1012345678912
>> > Unpacked Activate Default EPS Bearer message. EPS Bearer id 5
>> > Received GTP-C PDU. Message type: GTPC_MSG_TYPE_MODIFY_BEARER_REQUEST
>> > 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
>> > And a lot more of these...
>> >
>> > I found this information from  the thread "NAS integrity error": "
>> >
>> > Seems like the UE is initially requesting the "oai.ipv4" APN. You can
>> > see this in the ESM information response message in the PCAP. Only
>> > after the attach is complete it requests the PDN connectivity to the
>> > "srsapn" PDN."
>> >
>> > I thought maybe my problem was the same, but I can`t find any ESM information response message
>> > in  my epc.pcap-file?
>> >
>> > From the beginning of epc.log:
>> >
>> > Built in Release mode using commit d045213f on branch master.
>> >
>> > ---  Software Radio Systems EPC log ---
>> >
>> > 10:18:59.364245 [HSS ] [I] Opened DB file: /etc/srslte/user_db.csv
>> > 10:18:59.364388 [HSS ] [I] HSS Initialized. DB file /etc/srslte/user_db.csv, MCC: 61441, MNC: 65281
>> > 10:18:59.390979 [S1AP] [I] S1-MME Initializing
>> > 10:18:59.391230 [S1AP] [I] S1AP Initialized
>> > 10:18:59.391250 [MME GTPC] [I] Initializing MME S11 interface.
>> > 10:18:59.391272 [MME GTPC] [I] MME S11 Initialized
>> > 10:18:59.391302 [MME GTPC] [I] MME GTP-C Initialized
>> > 10:18:59.391313 [S1AP] [I] MME Initialized. MCC: 0xf001, MNC: 0xff01
>> >
>> > Is the MCC and MNC correct? Elsewhere they are 001 and 01?
>> >
>> > _______________________________________________
>> > 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