# No ipv4 address

**URL:** https://forum.legato.io/t/no-ipv4-address/7013
**Category:** Uncategorized
**Created:** [May 6, 2026, 9:10pm UTC](https://forum.legato.io/t/no-ipv4-address/7013 "2026-05-06T21:10:33Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![jack.heaffey](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@jack.heaffey](https://forum.legato.io/u/jack.heaffey)
#### Post date: [May 6, 2026, 9:10pm UTC](https://forum.legato.io/t/no-ipv4-address/7013/1 "2026-05-06T21:10:33Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![jyijyi](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/jyijyi/32/822_2.png) [@jyijyi](https://forum.legato.io/u/jyijyi)
#### Post date: [May 7, 2026, 1:41am UTC](https://forum.legato.io/t/no-ipv4-address/7013/2 "2026-05-07T01:41:06Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![jack.heaffey](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@jack.heaffey](https://forum.legato.io/u/jack.heaffey)
#### Post date: [May 7, 2026, 11:59am UTC](https://forum.legato.io/t/no-ipv4-address/7013/3 "2026-05-07T11:59:02Z")

</div>

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

```auto
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.

---

<div class="post-metadata">

### Author: ![jyijyi](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/jyijyi/32/822_2.png) [@jyijyi](https://forum.legato.io/u/jyijyi)
#### Post date: [May 7, 2026, 1:20pm UTC](https://forum.legato.io/t/no-ipv4-address/7013/4 "2026-05-07T13:20:37Z")

</div>

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

---

<div class="post-metadata">

### Author: ![jack.heaffey](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@jack.heaffey](https://forum.legato.io/u/jack.heaffey)
#### Post date: [May 7, 2026, 2:12pm UTC](https://forum.legato.io/t/no-ipv4-address/7013/5 "2026-05-07T14:12:00Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![jyijyi](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/jyijyi/32/822_2.png) [@jyijyi](https://forum.legato.io/u/jyijyi)
#### Post date: [May 7, 2026, 2:20pm UTC](https://forum.legato.io/t/no-ipv4-address/7013/6 "2026-05-07T14:20:47Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![jack.heaffey](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@jack.heaffey](https://forum.legato.io/u/jack.heaffey)
#### Post date: [May 7, 2026, 2:44pm UTC](https://forum.legato.io/t/no-ipv4-address/7013/7 "2026-05-07T14:44:09Z")

</div>

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)

---

<div class="post-metadata">

### Author: ![jyijyi](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/jyijyi/32/822_2.png) [@jyijyi](https://forum.legato.io/u/jyijyi)
#### Post date: [May 7, 2026, 3:09pm UTC](https://forum.legato.io/t/no-ipv4-address/7013/8 "2026-05-07T15:09:32Z")

</div>

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](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

---

<div class="post-metadata">

### Author: ![jack.heaffey](https://avatars.discourse-cdn.com/v4/letter/j/ad7895/32.png) [@jack.heaffey](https://forum.legato.io/u/jack.heaffey)
#### Post date: [May 7, 2026, 8:42pm UTC](https://forum.legato.io/t/no-ipv4-address/7013/9 "2026-05-07T20:42:02Z")

</div>

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