<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">On 22/04/2020 15:07, Aleksander Morgado wrote: </div> <blockquote type="cite" cite="mid:CAAP7ucLUmQBy85_+xcw3Fo4gvxNSv84R2MFx8VacBct3bnHQNQ@mail.gmail.com"> <blockquote type="cite" style="color: #000000;"> <pre class="moz-quote-pre" wrap="">What's the best strategy to connect a modem as per user configuration when we "get" one visible in ModemManager? </pre> </blockquote> <pre class="moz-quote-pre" wrap="">Using NetworkManager? NM takes care of all that process, keeping the connection settings as NM profiles. Is this not working for you? </pre> </blockquote> My experience has been that you can delete settings from NM, but the modem will remember these settings and may continue to use them, resulting in call connection errors. e.g. Network Manager may request that the modem uses a particular configuration (e.g. APN / user / pass configuration), but the modem uses some other remembers settings instead. I think the NM model is that all the state is stored in NM (for managed devices). There is an implicit assumption in the NM design that the device being managed (a modem via MM in this case) is stateless, but in this case it isn't, and the violation of this assumption leads to incorrect behaviour. If the APIs allows this, MM could provide information to NM on the current modem configuration state, otherwise MM could remove all saved state from the modem. Tim. <pre class="moz-signature" cols="72">-- South East Open Source Solutions Limited Registered in England and Wales with company number 06134732. Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ VAT number: 900 6633 53 <a class="moz-txt-link-freetext" href="http://seoss.co.uk/">http://seoss.co.uk/</a> +44-(0)1273-808309 </pre> </body> </html>