No ipv4 address

1

Hi,

I have a WP7610 connected to AT&T. There is an intermittent issue whereby after starting a data connection using le_data_Request, the cell module acquires an ipv6 address but not an ipv4 address. Once the cell module is in this state, I cannot get it to acquire an ipv4 address without rebooting it. Running “cm data disconnect” returns LE_FAULT. Running “cm radio off; cm radio on; cm data connect” returns LE_DUPLICATE.

2

what is the current setting of “cm data” now?

After reboot, if you use “cm data connect &” to establish data connection, is it OK to get IPV4 address?

3

When the issue occurs (i.e. the cell module has no IPv4 address), here is the output of “cm data”

root@swi-mdm9x28-wp:~# cm data
Index:                         1
APN:
PDP Type:                      IPV4V6
Connected:                     yes
Interface:                     rmnet_data0
Family[IPv6]:                  inet6
IP[IPv6]:                      2600:382:7712:1d99:cc4f:aee4:5f46:8a69
Gateway[IPv6]:                 2600:382:7712:1d99:f8d3:119:908d:8d8c
Dns1[IPv6]:                    fc00:a:a::400
Dns2[IPv6]:                    fc00:a:a::400
root@swi-mdm9x28-wp:~# cm data disconnect
Disconnecting ... failed
Thu May  7 11:56:23 UTC 2026 - Stop Failure: LE_FAULT
root@swi-mdm9x28-wp:~# cm data connect
Checking if device 'rmnet_data0' is up ... ok
Routing inet6 ... ok
Updating /etc/resolv.conf ... ok
root@swi-mdm9x28-wp:~# cm data
Index:                         1
APN:
PDP Type:                      IPV4V6
Connected:                     yes
Interface:                     rmnet_data0
Family[IPv6]:                  inet6
IP[IPv6]:                      2600:382:7712:1d99:18bb:254e:4cac:2136
Gateway[IPv6]:                 2600:382:7712:1d99:f8d3:119:908d:8d8c
Dns1[IPv6]:                    fc00:a:a::400
Dns2[IPv6]:                    fc00:a:a::400

After rebooting, running “cm data connect” does indeed result in an ipv4 address being successfully acquired.

4

how about setting IPV4 only by “cm data pdp ipv4”?

5

After running “cm data pdp ipv4”, the device still intermittently fails to get an IPv4 address. The only difference this time is that it doesn’t get an IPv6 address either.

6

then is it OK to get IPv4 after “cm radio off” and “cm radio on”?

BTW, are you using correct APN?

Lastly, which firmware are you using?

7

No, it cannot then acquire an IPv4 address after doing “cm radio off”, then “cm radio on” then “cm data connect”.

I haven’t explicitly set the APN, so the default AT&T APN is being used.

I’m using R16.1 and legato 19.11.02, which is the most recent versions that support the WP7610 (which was superseded by the WP7611)

8

does it help to try FW R17.1 which also supports WP7610?

https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-17,-d-,1/#sthash.nAyVrAK6.cwLBuzV6.dpbs

Please note that once you upgrade to R17.1, you cannot downgrade to older FW version

9

I wasn’t aware the R17.1 supported the WP7610. I’ll upgrade to R17.1 and see if the issue persists.