Re: Configure a connection for a gsm with dynamic ttyACMx

Le 26. 05. 15 15:28, Dan Williams a écrit :
On Tue, 2015-05-26 at 08:34 +0200, Thomas Haller wrote:

Just leave "connection.interface-name" unspecified, for example via:

    $ nmcli connection modify NAME connection.interface-name ""
It's important to note that this is the ModemManager *control port*,
which can be a TTY, a cdc-wdm, etc.

One thing we want to do, but haven't done yet, is to add a way to lock
the connection to the device ID and/or the SIM ID (IMSI), which should
often be more useful than the control port itself.

Hi Dan,

My application is a network of embedded systems where each system can have an internal or an external SIM card. For this kind of use the device ID or IMSI will not help as there will be different on each system and I want a unique configuration file that work on all systems. An other proposition could be to let's tag the devices from the udev rules and allow both ModemManager and NetworkManager use the tag to refer to the device. One advantage of this proposition is that it allow to use this tag differently, for example ModemManager could be configured to override the tag with the device ID and/or IMSI to fit your proposed use case.

While doing my experiment, I used udev rules that created specific symbolic links for the modem regardless of this actual ttyACMx. If ModemManager could have a way to be configured to use the specific symbolic links, then NetworkManager would have see a fixed device name. This is also an acceptable way for me to solve the problem.

Jean-Christian de Rivaz

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]