Hey Dan and all, > > > > The main issue with this approach is that ModemManager would do a > > > > lot > > > > of tasks that were exclusively done by NetworkManager before, > > > > like > > > > IP > > > > addressing setup or IP routing setup. I'm sure we can instruct NM > > > > to > > > > play nicely with those being done by MM, but not sure how easy > > > > that > > > > would be. > > > > > > Alternatively pppd could be instructed to not actually configure IP > > > or > > > routes, but with the plug-in pass the IPCP negotiated data to NM > > > via > > > MM. Then the NM could either use those data if the interface is > > > configured for "auto" configuration or enforce connection IP > > > settings. > > > Not sure though what actually is less complicated here. > > > > Hi, > > > > I missed your email before sending mine. > > > > I agree with this suggestion. > > Yes, this approach has my vote. It is consistent with how other IP > handling in MM works where it asks the modem for the details and then > makes them available via D-Bus for NM or other connection managers to > use. >
While I work in the pppd integration inside MM, I would like to suggest we merge this commit right away in git master, and also backport it to 1.8 and 1.10, so that we avoid all issues with pppd and MM using the TTY at the same time: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/113 -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
