# WP7702 and IPV6 connection **URL:** \ **Category:** Uncategorized\ **Created:** [July 3, 2018, 5:58am UTC](https://forum.legato.io/t/wp7702-and-ipv6-connection/3396 "2018-07-03T05:58:48Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![davidc](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@davidc](https://forum.legato.io/u/davidc)\ **Post date:** [July 3, 2018, 5:58am UTC](https://forum.legato.io/t/wp7702-and-ipv6-connection/3396/1 "2018-07-03T05:58:48Z")
Hi, When I have the PDP context set to IPV4V6, when I run `cm data connect` my ISP (Telstra) issues the WP7702 both an IPV4 and an IPV6 address. I can then successfully ping various IPV6 addresses. However, if I try to ping (or do any other connection to) an IPV4 target, I always get “Network is unreachable” or other IPV4 timeout. `cm data` indicates that the device has sane IPV6 information (IP/Gateway/DNS). ifconfig indicates that there are sane IPV4 addresses for the local interfaces - bridge0/ecm0/rmnet\_data0 But there doesn’t appear to be a default route for IPV4 traffic. How do I _automatically_ have `cm data connect` establish a default route for IPV4 traffic when the ISP issues an IPV6 address? I don’t particularly care if the route is via the IPV4 address on rmnet\_data0, or if the route is via some other bridge mechanism. Thanks, Dave ---
**Author:** ![CoRfr](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/corfr/32/69_2.png) [@CoRfr](https://forum.legato.io/u/CoRfr)\ **Post date:** [July 3, 2018, 4:31pm UTC](https://forum.legato.io/t/wp7702-and-ipv6-connection/3396/2 "2018-07-03T16:31:32Z")
Hi @davidc, Which version of legato are you running? Some ipv4v6 issues with cm data connect have been resolved in the previous release I think. Note that you should be fine either way if you use the DCS, so le\_data\_Request API. Thanks ---
**Author:** ![davidc](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@davidc](https://forum.legato.io/u/davidc)\ **Post date:** [July 3, 2018, 11:17pm UTC](https://forum.legato.io/t/wp7702-and-ipv6-connection/3396/3 "2018-07-03T23:17:45Z")
Hi @CoRfr, I’m currently testing this on a mangOH Red with WP7702 and Legato 17.11.0. But it’s been my experience that even bringing up the connection from within Legato doesn’t sort out the IPV4 routing correctly. I’ll test the WP77 with the latest legato and see how I get on. But that won’t help me with the FX30 (WP8548/Legato 16.10.1) as it’s pinned to legato 16.10.1 and there are a number of telcos around the world that give IPV6 by default now. Thanks, Dave Even ---
**Author:** ![davidc](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@davidc](https://forum.legato.io/u/davidc)\ **Post date:** [July 4, 2018, 3:10am UTC](https://forum.legato.io/t/wp7702-and-ipv6-connection/3396/4 "2018-07-04T03:10:01Z")
Hi @CoRfr, I can confirm that the network stack is set up properly for dual stack operation when I installed legato 18.05.1 onto the WP7702. ‘ping [www.google.com](http://www.google.com)’ is via IPV4 ‘ping [ipv6.google.com](http://ipv6.google.com)’ is via IPV6 Now for the big question … how do I coerce an FX30 (WP8548/legato 16.10.1) to do the same? ciao, Dave ---
**Author:** ![CoRfr](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/corfr/32/69_2.png) [@CoRfr](https://forum.legato.io/u/CoRfr)\ **Post date:** [July 6, 2018, 4:43am UTC](https://forum.legato.io/t/wp7702-and-ipv6-connection/3396/5 "2018-07-06T04:43:51Z")
Difficult question, and not sure how that would be possible. Best way might be to backport ipv4v6 related fixes on top of 16.10.1. ---
**Author:** ![davidc](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@davidc](https://forum.legato.io/u/davidc)\ **Post date:** [July 8, 2018, 10:59pm UTC](https://forum.legato.io/t/wp7702-and-ipv6-connection/3396/6 "2018-07-08T22:59:13Z")
Hi. Thanks … that’s what I was afraid you’d say ☹ ciao, Dave