On Thu, Dec 22, 2016 at 10:10 AM, Aleksander Morgado <[email protected]> wrote: > So now we have to decide how to handle this in the "connection status > checks" we do. Right now the checks return either: connected, > disconnected or error. In the case of error we do nothing, just log > it, but maybe we should trigger a disconnection right away as well? Or > just handle those errors in the checker method itself and return > "disconnected" without error? > > If we decide that the generic plugin should treat some errors as fatal > (i.e. report disconnected after the error) and some not (just log the > error message), we'd need to decide which error is which. E.g. of > non-fatal errors could be a modem that doesn't support the specific > command being used to check connectivity (e.g. while other devices of > the same vendor do), or also the errors we currently get when trying > to check connection status on a modem with one single AT port (as > there's no free port to run the AT command during connection). > > What do you guys think we should do?
I've created a new bugreport to track this issue, which really applies to all modems, not just Cinterion: https://bugs.freedesktop.org/show_bug.cgi?id=99273 -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
