Wp7610 : fail to get IP/connect

I am trying to connect the wp7610 to the Raspberry Pi 3 B+ board. So, i have installed the GobiNet and GobiSerial Drivers.
The driver is shown to be installed normally as shown below.
OD +IDN)
[ 2.992115] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[ 3.006996] systemd[1]: Detected architecture arm.
[ 3.021185] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.045652] smsc95xx v1.0.6
[ 3.059249] systemd[1]: Set hostname to .
[ 3.124508] random: systemd-gpt-aut: uninitialized urandom read (16 bytes read)
[ 3.136515] smsc95xx 1-1.1:1.0 eth0: register ‘smsc95xx’ at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:b9:1c:1d
[ 3.157687] uart-pl011 3f201000.serial: no DMA platform data
[ 3.251828] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[ 3.458209] systemd[1]: Reached target Swap.
[ 3.461815] usb 1-1.2: new high-speed USB device number 5 using dwc_otg
[ 3.480173] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 3.500781] systemd[1]: Listening on udev Control Socket.
[ 3.513971] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 3.532307] systemd[1]: Reached target Remote File Systems.
[ 3.545378] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 3.578366] systemd[1]: Listening on Journal Socket.
[ 3.607399] usb 1-1.2: config 1 has an invalid interface number: 16 but max is 6
[ 3.607410] usb 1-1.2: config 1 has an invalid interface number: 17 but max is 6
[ 3.607419] usb 1-1.2: config 1 has an invalid interface number: 17 but max is 6
[ 3.607429] usb 1-1.2: config 1 has an invalid interface number: 18 but max is 6
[ 3.607438] usb 1-1.2: config 1 has an invalid interface number: 18 but max is 6
[ 3.607449] usb 1-1.2: config 1 has an invalid interface number: 8 but max is 6
[ 3.607459] usb 1-1.2: config 1 has no interface number 1
[ 3.607467] usb 1-1.2: config 1 has no interface number 4
[ 3.607475] usb 1-1.2: config 1 has no interface number 5
[ 3.607483] usb 1-1.2: config 1 has no interface number 6
[ 3.615376] usb 1-1.2: New USB device found, idVendor=1199, idProduct=68c0, bcdDevice= 3.18
[ 3.742988] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.742997] usb 1-1.2: Product: Sierra Wireless WP7610
[ 3.743008] usb 1-1.2: Manufacturer: Sierra Wireless, Incorporated
[ 3.774124] usb 1-1.2: SerialNumber: ZT95110209121022
[ 3.838242] i2c /dev entries driver
[ 3.881800] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[ 4.045653] usb 1-1.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 4.045669] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4.045678] usb 1-1.3: Product: CP2102 USB to UART Bridge Controller
[ 4.045686] usb 1-1.3: Manufacturer: Silicon Labs
[ 4.045694] usb 1-1.3: SerialNumber: 0001
[ 4.141831] usb 1-1.4: new full-speed USB device number 7 using dwc_otg
[ 4.272493] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 4.281023] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 4.281041] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4.281051] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller
[ 4.281062] usb 1-1.4: Manufacturer: Silicon Labs
[ 4.281070] usb 1-1.4: SerialNumber: 0001
[ 4.380447] systemd-journald[94]: Received request to flush runtime journal from PID 1
[ 4.620680] usbcore: registered new interface driver usbserial_generic
[ 4.620751] usbserial: USB Serial support registered for generic
[ 4.627781] usbcore: registered new interface driver cp210x
[ 4.627857] usbserial: USB Serial support registered for cp210x
[ 4.628112] cp210x 1-1.3:1.0: cp210x converter detected
[ 4.640080] usb 1-1.3: cp210x converter now attached to ttyUSB0
[ 4.640358] cp210x 1-1.4:1.0: cp210x converter detected
[ 4.646037] usb 1-1.4: cp210x converter now attached to ttyUSB1
[ 4.693292] GobiNet: loading out-of-tree module taints kernel.
[ 4.709624] GobiNet: 2020-06-19/SWI_2.63
[ 4.710323] QMAP Disabled
[ 4.716098] GobiNet 1-1.2:1.8 eth1: register ‘GobiNet’ at usb-3f980000.usb-1.2, GobiNet Ethernet Device, a2:4e:e4:a2:41:08
[ 4.720309] USB Speed : USB 2.0
[ 4.720513] usbcore: registered new interface driver GobiNet
[ 4.729615] usbcore: registered new interface driver GobiSerial
[ 4.729700] usbserial: USB Serial support registered for GobiSerial
[ 4.732510] GobiSerial 1-1.2:1.0: GobiSerial converter detected
[ 4.735482] usb 1-1.2: GobiSerial converter now attached to ttyUSB2
[ 4.736046] GobiSerial 1-1.2:1.2: GobiSerial converter detected
[ 4.736404] usb 1-1.2: GobiSerial converter now attached to ttyUSB3
[ 4.744671] GobiSerial 1-1.2:1.3: GobiSerial converter detected
[ 4.745095] usb 1-1.2: GobiSerial converter now attached to ttyUSB4
[ 4.745277] GobiSerial: 2020-06-19/SWI_2.42:GobiSerial
[ 4.829530] usbcore: registered new interface driver snd-usb-audio
[ 5.216875] media: Linux media interface: v0.10
[ 5.229856] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[ 5.232851] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[ 5.232868] [vc_sm_connected_init]: start
[ 5.258298] videodev: Linux video capture interface: v2.00
[ 5.272996] [vc_sm_connected_init]: installed successfully
[ 5.296129] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 5.296136] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 5.306972] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 5.324900] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 5.358973] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 5.358992] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 5.364373] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 5.364390] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 5.381486] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 5.381501] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 6.142912] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 6.493172] smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
[ 6.493479] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 8.024625] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[ 8.026735] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 13.791102] random: crng init done
[ 13.791114] random: 7 urandom warning(s) missed due to ratelimiting
[ 20.161754] creating qcqmi0
[ 20.162041] RawIP mode
The modem has also been attached to the network normally and obtained an IP.

at
OK
at+CGPADDR
+CGPADDR: 1,10.252.89.85
+CGPADDR: 2,32.1.68.48.16.206.27.242.0.0.0.0.0.93.200.203
+CGPADDR: 3,0.0.0.0,0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0

OK

However, the network driver does not display the IP obtained by the modem.
root@unet:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.194 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::ba27:ebff:feb9:1c1d prefixlen 64 scopeid 0x20
ether b8:27:eb:b9:1c:1d txqueuelen 1000 (Ethernet)
RX packets 926 bytes 66906 (65.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 548 bytes 51744 (50.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth1: flags=4227<UP,BROADCAST,NOARP,MULTICAST> mtu 1500
ether a2:4e:e4:a2:41:08 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 4 bytes 156 (156.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 156 (156.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I want to have the modem read the IP received from the network. How can i do this?

@sugar

So as far as I can tell the unit has powered up, enumerated to the system successfully and attached to the network hence you can see the IP addresses in the cgpaddr command. What you have not done is triggered the user data session between the unit and the host system, if you send at!scact=1,1 then it should automatically come up (system dependent), if not then send a dhclient eth1 afterwards and you should see the interface populated.

Regards

Matt

Thank you for interesting.
At!scact=1,1 should always be done at every boot.
I confirmed that the Ip is read with the udhcpc -i eth1 command.
Thank you very much.