I’m having trouble getting network address for MC7455 module using DHCP client on linux device. We are using MBPL R24 and drivers that come with it. As a work around I query the address with SLQSGetRuntimeSettings and set that address to interface manually. So, network provides address to MC7455 modem, but for some reason DHCP client isn’t able to get it.
We used to have Gobi drivers for MC7455 modems and then there wasn’t any problems with DHCP client. Also, if I now put EM9190 modem to that same system it doesn’t have any issues with DHCP client. DHCP client is able to get the address that network has provided.
So, what could be wrong with MC7455? Linux version is 4.19.168 and MC7455 FW version is
SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
But on the other hand, same goes with EM9190 module. There is no raw_ip file for it either, and it is also configured to use mbim instead of rmnet. But still it works with DHCP client without any problems…
Well, that script does basically the same thing as my own link manager as a workaround for this dhcp problem. It queries address from modem and sets it to interface and It’s working fine. But I was just curious about why the dhcp client wouldn’t work in this case. It should on my opinion and it does when using for example EM9190 modem.
I don’t think that rmnet is an option for us. Using that creates a point to point interface and that turned out to be a problem for some third party SW that we are using.
ip link show wwan0
17: wwan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000