Need help with a Netgear AirCard 314u

Dan Williams dcbw at redhat.com
Mon Aug 15 14:37:26 UTC 2016


On Mon, 2016-08-15 at 09:04 -0400, Neil Cherry wrote:
> On 08/15/2016 04:19 AM, Aleksander Morgado wrote:
> > 
> > On 15/08/16 03:01, Neil Cherry wrote:
> > > 
> > > Okay this was interesting ... I can now reach the modem (Netgear
> > > 341u)
> > > from my server (and browser). But I can't seem to ping anything
> > > via
> > > the wwan0 (other than the we server's address). So some more
> > > work.
> > > 
> > What do you mean you can reach the modem through your browser?
> http://sprintmodem/ (192.168.2.1)

Despite the thread title, I think you mean a Netgear 341u right?

This seems to be one of the devices that presents itself as a USB
ethernet device then, rather than a WWAN modem interface.  Yes, they do
often expose the control channels for use as a WWAN modem (AT commands,
QMI, etc) but their primary mode seems to be the plain USB ethernet
dongle mode.

Usually you wouldn't use ModemManager to control these, because they do
all the WWAN stuff internally.  It's possible that ModemManager and the
device are fighting over settings and such.

If you don't use ModemManager, but just run DHCP on the ethernet device
after plugging the device in, does that work?  What does the modem's
Web UI say about whether it's connected?

Dan

> > 
> > > 
> > > Here's what I did:
> > > 
> > > # Plugged in the modem
> > > mmcli -L
> > > # As root
> > > mmcli -m 0 -e
> > > qmi-network /dev/cdc-wdm0 start
> > > dhclient -d wwan0
> > Not sure why you mixed the qmi-network and mmcli calls here.
> I've been doing searches and found the commands used together. So I
> gave it a try. Right now this isn't working as well as I hoped but
> it has kind-of gotten me one step further.
> 
> > 
> > Can you run ModemManager with --debug and post what happens after
> > you
> > run this?:
> > 
> > $ mmcli -m 0 --simple-connect="apn=internet"
> > 
> > $ mmcli -b 0      // to show bearer info, to make sure DHCP is
> > needed
> > 
> > $ dhclient wwan0
> > 
> I think I'll have to, as I may have reached http://sprintmodem/ but
> it
> hasn't really connected (modem still says connecting to internet).
> 


More information about the ModemManager-devel mailing list