[RFC] TTY port locked problems when using PPP

Thomas Haller thaller at redhat.com
Thu Jun 27 09:10:20 UTC 2019

On Thu, 2019-06-27 at 10:20 +0200, Aleksander Morgado wrote:
> > 
> 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.


Configuring IP addresses and routes must be done by NetworkManager.

NetworkManager has settings like ipv4.route-table, ipv4.route-metric,
and ipv4.ignore-auto-routes. ModemManager does not know whta
NetworkManager plans to do with these settings (and making that all
configuable seems high effort while the wrong approach).

NetworkManager would also remove such routes that it is not aware of
during `nmcli device reapply`.

ModemManager already reports IP configuration back to NetworkManager.
It should just continue to do so.

This does not mean that ModemManager should not run pppd. It sounds
like a good idea to me. But ModemManager should just report the IP
addressing back -- at least configurably/optionally when NetworkManager
is involved.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20190627/49c3234e/attachment.sig>

More information about the ModemManager-devel mailing list