CHROMIUM: modemmanager-next: Allow MBIM bearer to access IPv4 address when requested IP type is IPv6
On T-mobile network when we request for IPv6 (only),
to support roaming, the network responds back with both IPv4 and IPv6 address.
MM does not pass on the IPv4 address to shill,
which internally causes shill to connect/disconnect from the network making the connection unusable.
This change basically passes the IPv4 config to shill if it's present.
BUG=b:183029202, b:162701578
TEST=emerge-hatch modemmanager-next && cros deploy && Check if we have
network access && run cellular_Identifiers.tmobile,
cellular_SafetyDance.tmobile
Change-Id: Ifa2b92f8af9b3854c4c1dbf130178bb738d45bc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/modemmanager-next/+/2802712
Reviewed-by: Andrew Lassalle <andrewlassalle@chromium.org>
Reviewed-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Hugo Benichi <hugobenichi@google.com>
Commit-Queue: Madhav . <madhavadas@google.com>
Tested-by: Madhav . <madhavadas@google.com>
1 file changed
