Evaluating EG912U-GL on PH-7 core board in the USA
Module was rebooting every few minutes until I reflashed it with BETA0002 firmware from the QuecDevZone website.
Now,
With Verizon and 1nce sims, it is assigned a valid network address, reports it is activated and registered, but dhcp to the module via ECM or RNDIS fails. In the case of 1nce, I know the IP address I should be assigned. So, I know the modem is getting this from the network provider.
I’ve tried under Windows 10 and 3 different flavors of Linux.
The SIMs I’m testing work in other modems.
What is most likely wrong?
Is there something like a PING command I can run as an AT command to verify I have connectivity from the modem, even if it will not properly respond to DHCP?
Well, part of my problem was the need for the Quectel specific
AT+QNETDEVCTL
command. [I’ve never before seen an ECM or RNDIS modem that required a special command to enable its DHCP server or to “Connect th network adapter”. Why does this command exist? If the PDP context is enabled and attached, what more has to happen? ]
So, I’ve got the the DHCP server giving out what clearly are unroutable (192.168.x.y) addresses although NAT is not enabled.
Not surprisingly, there’s no network connectivity from the private address. So,
I tried enabling NAT for cid 1, but, still, no network connectivity.