summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDan Williams <dcbw@redhat.com>2014-08-18 09:47:59 -0500
committerDan Williams <dcbw@redhat.com>2014-08-18 09:47:59 -0500
commit0c6f1ae6c4bae4b4d82d015f6940e0448749aee3 (patch)
tree4b0157dcce188cd1bc74554bc53732cf0bd7a63a
parentb03e1cfd582d433694ac9b4f13e9e2757da61348 (diff)
downloadModemManager-dcbw/qmi-always-dhcp.tar.gz
qmi: always use DHCP for IPv4 configuration instead of STATICdcbw/qmi-always-dhcp
Some newer modems (Huawei E1750, Sierra 73xx) provide what looks like legitimate static IPv4 configuration through the WDSGetCurrentSettings call, but when configured the interface does not pass traffic. Running DHCP on the same interface provides a slightly different IPv4 configuration but does allow traffic to pass. Since QMI was switched to static originally for consistency with IPv6 and for speed of IP configuration (since DHCP takes a bit of time), but not for any known problems with modems, let's switch back to DHCP until we have time to figure out what's actually going on.
-rw-r--r--src/mm-broadband-modem-qmi.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mm-broadband-modem-qmi.c b/src/mm-broadband-modem-qmi.c
index fa371fc26..277d43d41 100644
--- a/src/mm-broadband-modem-qmi.c
+++ b/src/mm-broadband-modem-qmi.c
@@ -318,7 +318,7 @@ modem_create_bearer (MMIfaceModem *self,
/* We just create a MMBearerQmi */
mm_dbg ("Creating QMI bearer in QMI modem");
- bearer = mm_bearer_qmi_new (MM_BROADBAND_MODEM_QMI (self), properties, FALSE);
+ bearer = mm_bearer_qmi_new (MM_BROADBAND_MODEM_QMI (self), properties, TRUE);
g_simple_async_result_set_op_res_gpointer (result, bearer, g_object_unref);
g_simple_async_result_complete_in_idle (result);
g_object_unref (result);