SOLUTION to failed to get dhcp lease

The reason why “lease fail” is shown, is because dhcpc conflicts with udhcpc. Fixing this is simple; Add “denyinterfaces wwan0” to bottom of /etc/dhcpcd.conf. Then restart dhcpc “sudo systemctl restart dhcpcd”, followed by restarting qmi_reconnect “sudo systemctl restart qmi_reconnect” (or reboot).

@ensar, please add this part to the qmi setup script.

…Or if you want overkill, simply disable dhcpcd completely; “sudo systemctl stop dhcpcd; sudo systemctl disable dhcpcd”

3 Likes

Hi! This fixed my problem. Thank you! :slight_smile:

Can someone share their /etc/dhcpcd.conf? After trying this solution I’m still unable to get an ip address for wwan0, but I think I’m on the right track because this got me passed my typical error message. I made the mistake of following the “Using Raspberry Pi Base Shield as a Wi-Fi Hotspot” tutorial after realizing my QMI interface wasn’t set up properly. Thus I think doing the PPP Installer for Base HAT and Using Raspberry Pi Base HAT as a Wi-Fi Hotspot before getting my wwan0 interface working has caused my /etc/dhcpcd.conf file to change. Here is my dhcpcd.conf file:

# RaspAP ppp0 configuration
hostname
clientid
persistent
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option ntp_servers
require dhcp_server_identifier
slaac private
nohook lookup-hostname
interface ppp0
static ip_address=10.3.141.1/24
static domain_name_server=1.1.1.1 8.8.8.8
denyinterfaces wwan0

This fixed my issue. Thank you so much!

it looks correct. try putting denyinterfaces above your interface eth0/ppp

Thanks for this. It did fix my lease fail issue but I am now getting an issue with too few arguments. See below:

pi@raspberrypi:~/files/quectel-CM $ sudo ./quectel-CM -s NXTGENPHONE
[07-29_11:38:57:156] Quectel_QConnectManager_Linux_V1.5.9
[07-29_11:38:57:158] Find /sys/bus/usb/devices/1-1.4 idVendor=0x2c7c idProduct=0x125, bus=0x001, dev=0x005
[07-29_11:38:57:159] Auto find qmichannel = /dev/cdc-wdm0
[07-29_11:38:57:159] Auto find usbnet_adapter = wwan0
[07-29_11:38:57:159] netcard driver = qmi_wwan, driver version = 22-Aug-2005
[07-29_11:38:57:159] Modem works in QMI mode
[07-29_11:38:57:183] cdc_wdm_fd = 7
[07-29_11:38:57:280] Get clientWDS = 19
[07-29_11:38:57:312] Get clientDMS = 1
[07-29_11:38:57:345] Get clientNAS = 3
[07-29_11:38:57:377] Get clientUIM = 1
[07-29_11:38:57:408] Get clientWDA = 1
[07-29_11:38:57:440] requestBaseBandVersion EC25AFAR05A04M4G
[07-29_11:38:57:569] requestGetSIMStatus SIMStatus: SIM_READY
[07-29_11:38:57:569] requestSetProfile[1] NXTGENPHONE///0
[07-29_11:38:57:633] requestGetProfile[1] NXTGENPHONE///0
[07-29_11:38:57:665] requestRegistrationState2 MCC: 310, MNC: 410, PS: Attached, DataCap: LTE
[07-29_11:38:57:696] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[07-29_11:38:57:696] ifconfig wwan0 down
[07-29_11:38:57:704] ifconfig wwan0 0.0.0.0
[07-29_11:38:57:952] requestSetupDataCall WdsConnectionIPv4Handle: 0x87279650
[07-29_11:38:58:080] ifconfig wwan0 up
[07-29_11:38:58:086] busybox udhcpc -f -n -q -t 5 -i wwan0
udhcpc: started, v1.30.1
Too few arguments.
Too few arguments.
udhcpc: sending discover
udhcpc: sending select for 10.207.28.51
udhcpc: lease of 10.207.28.51 obtained, lease time 7200
Too few arguments.
Too few arguments.

Any recommendations on which arguments I am missing? I feel like I am REALLY close to finally getting this working so any help will be greatly appreciated.

I’m no expert, but I’ve read on another post that “Too few arguments” is NOT an error. It is in fact expected to be seen in our case.

p.s. You are close. Rerun “sudo ./quectel-CM -s NXTGENPHONE” and let it do it’s thing, then open another terminal window and try your “ping -I wwan0 8.8.8.8” command.

1 Like

Holy crap, it IS working. I did not realize that the script needed to continuously run. I did check the ping in a separate tab and have no packet loss. I then ran the browser and was able to connect. I am running at 18.3 Mbps down and 11.3 Mbps up. So freaking pumped right now.

2 Likes

what browser are you talking about?

Thank you so much, this solution works perfectly on the latest release of the driver and a fresh install of Raspbian!