Netgear 340u

[Bjørn Mork]

Noah Taber <noahtaber at gmail.com> writes:

> I will try the command later tonight.
>
> I'm not sure if this is clear, but the device I'm trying to make this work
> on is a raspberry pi, if that matters.  Do you think that will make a
> difference?

No, that won't make any difference.  The device config is presented by
the device firmware.  But if you have a Linux PC around, then
replicating the problem on that would be an easy and somewhat useful
test.  There *are* issues with the raspberry pi usb host controller
driver.  I don't think this should matter (you are obviously talking
just fine to the modem), but it wouldn't hurt to completely eliminate
the possibility.

Regarding the "missing" second config: All these modern Sierra devices
can be configured for a number of different device layouts, using 1 or 2
configurations. Such changes are non-volatile. I agree that it is
surprising to see such a new device without any MBIM configuration by
default, but this is really the choice of whoever you bought this device
from.  Maybe they didn't want Windows8 support?

Anyway, none of this should conflict with QMI support.  And are
definitely talking QMI to the modem.  The modem auto-connecting looks
like the most likely explanation so far, and your 
 "qmi-network /dev/cdc-wdm0 status"
test shows that it is in fact already connected.

So what we have to figure out is why it doesn't respond to DHCP. It
would have been interesting to see the output of a QMI_WDS "Get Current
Settings" request, but unfortunately that isn't implemented in the
qmicli yet...



Bjørn