> From: Aleksander Morgado <aleksan...@aleksander.es> > Sent: Friday, March 08, 2019 2:01 PM > > I have mixed feelings about this patch :) in one side, it's not the > best way to do it, as a proper profile management API would be best, > but from the other side it's a quick way to get the issue resolved > until that API is developed; if ever! > @Dan Williams what do you think? should we think in integrating this > workaround until the profile management API is done? >
The patch would work for us. Do we need permission to use it? It's GPL? > > On Fri, Mar 8, 2019 at 11:40 AM Aleksander Morgado > <aleksan...@aleksander.es> wrote: > >> > >> Right now, you could manually create the PDP context with the settings > >> you want, and MM should re-use the already created context if the > >> settings requested match the existing ones. > >> I did try letting MM find the right PDP context this way, but the recommendation I got from Sierra Wireless was to leave the APN blank when connecting to CAT-M networks and allow the network to provide the APN name during network registration. Since PDP context #1 was also blank, MM tried that, which didn't work. Calling pppd directly using context #3 with a blank APN works fine. _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel