QMI disconnection errors detection in Netgear AC341U

Dan Williams dcbw at redhat.com
Tue Sep 5 21:10:26 UTC 2017

On Tue, 2017-09-05 at 22:26 +0200, Aleksander Morgado wrote:
> Hey,
> The Netgear AC341U is a QMI device that comes with autoconnect
> enabled (and disabling it doesn't look possible, firmware may even
> crash and power cycle itself). I suspect that due to autoconnect
> being enabled, the packet service indications aren't sent as we
> expect them, in particular to detect network initiated
> disconnections.

Instead, could we hook up eQMI_WDS_GET_MODEM_STATUS and the
eQMI_WDS_MODEM_IND indicator or something and watch
sWDSModemStatusReportIndication_Status to see if we're already
connected or when we get disconnected?  Maybe it sends that indication
instead of packet service status for the NDIS autoconnect or something.
 Worth a look perhaps.

It's just that we could get call failures from so many places and
checking them all seems icky...


> If we don't get reliable packet service indications reporting
> disconnections, we may end up with ModemManager saying the modem is
> connected while the WWAN interface isn't really usable. To avoid this
> situation, we hook up two new places where we can detect the
> disconnection reported: either in the GetCurrentSettings step during
> the connection attempt (seen a couple of times where this is the
> case), or otherwise in the periodic Statistics loading logic (much
> more frequent).
> Comments?
>   [PATCH 1/2] bearer-qmi: detect early disconnections when getting
> current settings
>   [PATCH 2/2] bearer-qmi: detect disconnections when loading stats
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

More information about the ModemManager-devel mailing list