aboutsummaryrefslogtreecommitdiff
path: root/examples/modem-watcher-javascript/README
diff options
context:
space:
mode:
authorDan Williams <dcbw@redhat.com>2015-08-19 12:44:02 -0500
committerAleksander Morgado <aleksander@aleksander.es>2016-03-13 13:25:19 +0100
commita9b69d210d12acc458d2d8ba4e79554f818e8337 (patch)
tree0b838e7604d619c9778efc33afc4fdcb2cd4e67f /examples/modem-watcher-javascript/README
parent91d343520fec5c5905a4cc3ce898f75025f3f2a8 (diff)
huawei: use AT^DHCP response if available for NDISDUP-capable devices
For non-QMI/non-MBIM Huawei devices that use HiSense chipsets, the recommended way to create the connection is to use NDISDUP and either DHCP on the net interface, or the ^DHCP command. There are some reports of devices that connect successfully, but don't respond to DHCP requests on the interface. Try to get IP addressing info from the device via ^DHCP and fall back to telling clients to use actual DHCP if that fails. https://bugzilla.redhat.com/show_bug.cgi?id=1254886
Diffstat (limited to 'examples/modem-watcher-javascript/README')
0 files changed, 0 insertions, 0 deletions