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