Home Page Forums Raspberry Pi Shields "sending discover…. no lease, failing"

This topic contains 8 replies, has 5 voices, and was last updated by  gokul_gj 1 month ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #38218

    veoeluz04
    Participant

    Hello,

    I was hoping that someone would be able to point me in the right direction. I followed the directions here:

    https://sixfab.com/qmi-interface-with-3g-4g-lte-base-shield-v2/

    I felt like everything went really rather well, up until the point of actually making the connection. I purchased a data-only plan from Tmobile, and am using that sim card they gave me. The base shield appears to be powered and functioning as expected (except for not connecting).

    I’m using a raspberry Pi zero w. The parts I ordered from Sixfab are:

    Quectel EC25 Mini PCle 4G/LTE Module – EC25-A × 1
    LTE Main & Diversity Dual u.FL Antenna – 100mm × 1
    Raspberry Pi 3G-4G/LTE Base Shield V2 – with short header × 1

    The install worked a treat, but when i try to run sudo ./quectel-CM -s fast.t-mobile.com, the below result happens. Is there something I missed? The only thing I can think is that it warns that “No resolv.conf for interface wwan0.udhcpc”, but i didn’t see any instructions in the walkthrough to set that file up.

    after running it, it will just continuously spout “requestregistrationstate2”, until i hit ctrl-C to cancel it. I also noticed that when i make the attempt, after I cancel it, it also makes my wifi interface no longer recognized by the pi and I have to reboot. I’ve also tried disabling the wifi before running the below command.

    Any thoughts? Thank you, I appreciate any help!

    [email protected]:~/files/quectel-CM $ cd ~/files/quectel-CM/
    [email protected]:~/files/quectel-CM $ sudo ./quectel-CM -s fast.t-mobile.com
    [05-24_18:20:34:981] WCDMA&LTE_QConnectManager_Linux&Android_V1.1.45
    [05-24_18:20:34:984] ./quectel-CM profile[1] = fast.t-mobile.com///0, pincode = (null)
    [05-24_18:20:34:988] Find /sys/bus/usb/devices/1-1.4 idVendor=2c7c idProduct=0125
    [05-24_18:20:34:989] Find /sys/bus/usb/devices/1-1.4:1.4/net/wwan0
    [05-24_18:20:34:990] Find usbnet_adapter = wwan0
    [05-24_18:20:34:991] Find /sys/bus/usb/devices/1-1.4:1.4/usbmisc/cdc-wdm0
    [05-24_18:20:34:992] Find qmichannel = /dev/cdc-wdm0
    [05-24_18:20:35:081] cdc_wdm_fd = 7
    [05-24_18:20:35:179] Get clientWDS = 19
    [05-24_18:20:35:211] Get clientDMS = 1
    [05-24_18:20:35:243] Get clientNAS = 3
    [05-24_18:20:35:275] Get clientUIM = 1
    [05-24_18:20:35:307] Get clientWDA = 1
    [05-24_18:20:35:339] requestBaseBandVersion EC25AFAR05A04M4G
    [05-24_18:20:35:468] requestGetSIMStatus SIMStatus: SIM_READY
    [05-24_18:20:35:468] requestSetProfile[1] fast.t-mobile.com///0
    [05-24_18:20:35:532] requestGetProfile[1] fast.t-mobile.com///0
    [05-24_18:20:35:564] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
    [05-24_18:20:35:595] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
    [05-24_18:20:35:660] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
    [05-24_18:20:35:723] requestSetupDataCall WdsConnectionIPv4Handle: 0x871febf0
    [05-24_18:20:35:787] requestQueryDataCall IPv4ConnectionStatus: CONNECTED
    [05-24_18:20:35:819] ifconfig wwan0 up
    [05-24_18:20:35:882] busybox udhcpc -f -n -q -t 5 -i wwan0
    [05-24_18:20:35:948] udhcpc (v1.22.1) started
    No resolv.conf for interface wwan0.udhcpc
    [05-24_18:20:36:205] Sending discover…
    [05-24_18:20:39:209] Sending discover…
    [05-24_18:20:42:214] Sending discover…
    [05-24_18:20:45:217] Sending discover…
    [05-24_18:20:48:222] Sending discover…
    [05-24_18:20:51:288] No lease, failing
    [05-24_18:22:00:268] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
    [05-24_18:22:23:309] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
    [05-24_18:22:43:789] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
    [05-24_18:23:56:780] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
    [05-24_18:24:13:420] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
    [05-24_18:24:53:100] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
    [05-24_18:25:50:700] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE

    #38225

    veoeluz04
    Participant

    Update, I tried running through the PPP connection instructions and successfully connected, and get an ok speed, but I understand the QMI interface is supposed to offer better speeds, so I’m still interested to know if there’s a solution to my above problem.

    Thanks!

    #38250

    Saeed
    Moderator

    Hi,

    We are working on QMI interface for newer Kernel or Raspbian. OInce completed we will update it soon.

    #51266

    carlo.camporesi
    Participant

    Hello,
    I am having the same issue reported above. My configuration is similar but I am currently running Raspbian with kernel version 4.19.66 (latest version after the apt upgrade). Is there any update on a possible fix and/or docs on how to fix it?
    Connecting using the PPP modem works fine as reported above.
    Thanks again!
    -C

    #52834

    srkpally
    Participant

    Has anyone got the whole setup working with AT&T sim cards? I tried both PPP and QMI, none of them worked.

    #54419

    gokul_gj
    Participant

    Hi,

    I too face same issue as reported above. My configuration is similar but I am currently running Raspbian with kernel version 4.19.66 (latest version after the apt upgrade). Is there any update on a possible fix and/or docs on how to fix it?
    Connecting using the PPP modem works fine as reported above.

    Best Regards,
    Gokulan

    #55745

    Saeed
    Moderator

    Which Raspberry pi are you using?

    1. Before installation do you have done sudo apt update && sudo apt upgrade?

    2. Do you have updated rpi using sudo rpi-update ?

    After the update is completed please reboot then install the QMI.

    #56149

    gokul_gj
    Participant

    Hello Saeed,

    I am using Raspberry pi 4, I follwed the procedure as per the link, which was working before and after upgrade of
    https://sixfab.com/qmi-interface-with-3g-4g-lte-base-shield-v2/

    the logs are as below

    [email protected]:~/files/quectel-CM $ sudo ./quectel-CM -s internet
    [10-17_11:50:36:508] WCDMA&LTE_QConnectManager_Linux&Android_V1.1.45
    [10-17_11:50:36:509] ./quectel-CM profile[1] = internet///0, pincode = (null)
    [10-17_11:50:36:510] Find /sys/bus/usb/devices/1-1.3 idVendor=2c7c idProduct=0125
    [10-17_11:50:36:510] Find /sys/bus/usb/devices/1-1.3:1.4/net/wwan0
    [10-17_11:50:36:510] Find usbnet_adapter = wwan0
    [10-17_11:50:36:510] Find /sys/bus/usb/devices/1-1.3:1.4/usbmisc/cdc-wdm0
    [10-17_11:50:36:510] Find qmichannel = /dev/cdc-wdm0
    [10-17_11:50:36:538] cdc_wdm_fd = 7
    [10-17_11:50:36:636] Get clientWDS = 20
    [10-17_11:50:36:668] Get clientDMS = 1
    [10-17_11:50:36:700] Get clientNAS = 4
    [10-17_11:50:36:732] Get clientUIM = 1
    [10-17_11:50:36:764] Get clientWDA = 1
    [10-17_11:50:36:796] requestBaseBandVersion EC25EFAR06A04M4G
    [10-17_11:50:36:925] requestGetSIMStatus SIMStatus: SIM_READY
    [10-17_11:50:36:925] requestSetProfile[1] internet///0
    [10-17_11:50:36:989] requestGetProfile[1] internet///0
    [10-17_11:50:37:021] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:50:37:053] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
    [10-17_11:50:37:117] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:50:37:149] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:50:42:205] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:50:42:236] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:50:47:292] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:50:47:324] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:50:52:381] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:50:52:412] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:50:57:470] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:50:57:501] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:51:02:558] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:51:02:589] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:51:07:647] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:51:07:677] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:51:12:734] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:51:12:766] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:51:17:823] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:51:17:854] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:51:22:912] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:51:22:943] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
    [10-17_11:51:22:943] requestSetOperatingMode(1)
    [10-17_11:51:22:974] requestSetOperatingMode(0)
    [10-17_11:51:23:359] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
    [10-17_11:51:24:032] requestRegistrationState2 MCC: 404, MNC: 86, PS: Detached, DataCap: UNKNOW
    [10-17_11:51:24:575] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:51:24:703] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:51:24:734] requestSetupDataCall WdsConnectionIPv4Handle: 0x87221030
    [10-17_11:51:24:799] requestRegistrationState2 MCC: 404, MNC: 86, PS: Attached, DataCap: LTE
    [10-17_11:51:24:832] requestQueryDataCall IPv4ConnectionStatus: CONNECTED
    [10-17_11:51:24:895] ifconfig wwan0 up
    [10-17_11:51:24:902] busybox udhcpc -f -n -q -t 5 -i wwan0
    udhcpc: started, v1.30.1
    No resolv.conf for interface wwan0.udhcpc
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: no lease, failing

    Best REgards,
    Gokulan

    #56407

    gokul_gj
    Participant

    Hello Saeed,

    The issue got resolved..
    I tried to reload the raspberry os on my raspberry pi 4 device,
    Removed the Raspberry Pi 4G/LTE Shield Kit before os reload.
    The update & upgrade.
    Then followed the instruction https://sixfab.com/qmi-interface-with-3g-4g-lte-base-shield-v2/

    Now it starts wotkink…
    But the script needs to be intrupted as it does not stop after gaining IP address from dhcp.. of wwan0 port.”sudo ./quectel-CM -s internet”
    it says “too many arguments” and stops there , then I need to break the script and the ip address also get removed, then i ran “Auto Connect on reboot” scripts and rebooted .
    After reboot am able to get the IP address from 4G provide on wwan0 port and able to access internet.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.