[RFC] TTY port locked problems when using PPP
dcbw at redhat.com
Fri Jun 28 17:30:25 UTC 2019
On Thu, 2019-06-27 at 11:12 +0200, Thomas Haller wrote:
> On Thu, 2019-06-27 at 10:40 +0200, Piotr Figiel wrote:
> > Hi,
> > czw., 27 cze 2019 o 10:20 Aleksander Morgado
> > <aleksander at aleksander.es> napisał(a):
> > > 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.
> 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
More information about the ModemManager-devel