Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

[Ajay Garg]

Hi All.

We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's
MC8090 modem, and we have a requirement wherein we need to have access
to the modem-serial-port (from our user-application that is).

Right now, we see that /usr/sbin/ModemManager is always connected to
/dev/ttyUSB3 (which means we cannot connect to the port from our
application at the same time, or even if we can, received-data will be
at best inconsistent).


We are thinking of the following ::

* Initially, let nmcli and ModemManager do their work, and let them
bring the WWAN interface up.

* Once this happens, we permanently-down the ModemManager from our
application-binary, thereby freeing up /dev/ttyUSB3.

* Thereafter, we are free to connect to /dev/ttyUSB3 from our
application, thereby using features like SMS-notification (+CMTI),
signal-strength (+CSQ), etc.



Does our approach make sense?
We will be grateful to any help.


Thanks and Regards,
Ajay

Re: Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

[Greg KH]

On Tue, Aug 09, 2016 at 12:48:12PM +0530, Ajay Garg wrote:
> Hi All.
> 
> We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's
> MC8090 modem, and we have a requirement wherein we need to have access
> to the modem-serial-port (from our user-application that is).
> 
> Right now, we see that /usr/sbin/ModemManager is always connected to
> /dev/ttyUSB3 (which means we cannot connect to the port from our
> application at the same time, or even if we can, received-data will be
> at best inconsistent).
> 
> 
> We are thinking of the following ::
> 
> * Initially, let nmcli and ModemManager do their work, and let them
> bring the WWAN interface up.
> 
> * Once this happens, we permanently-down the ModemManager from our
> application-binary, thereby freeing up /dev/ttyUSB3.
> 
> * Thereafter, we are free to connect to /dev/ttyUSB3 from our
> application, thereby using features like SMS-notification (+CMTI),
> signal-strength (+CSQ), etc.
> 
> 
> 
> Does our approach make sense?
> We will be grateful to any help.

Why not ask the modem manager team about this?  The kernel doesn't care
what you do with the device links :)

thanks,

greg k-h

Re: Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

[Ajay Garg]

Ok Greg :)

On Tue, Aug 9, 2016 at 1:44 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Tue, Aug 09, 2016 at 12:48:12PM +0530, Ajay Garg wrote:
>> Hi All.
>>
>> We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's
>> MC8090 modem, and we have a requirement wherein we need to have access
>> to the modem-serial-port (from our user-application that is).
>>
>> Right now, we see that /usr/sbin/ModemManager is always connected to
>> /dev/ttyUSB3 (which means we cannot connect to the port from our
>> application at the same time, or even if we can, received-data will be
>> at best inconsistent).
>>
>>
>> We are thinking of the following ::
>>
>> * Initially, let nmcli and ModemManager do their work, and let them
>> bring the WWAN interface up.
>>
>> * Once this happens, we permanently-down the ModemManager from our
>> application-binary, thereby freeing up /dev/ttyUSB3.
>>
>> * Thereafter, we are free to connect to /dev/ttyUSB3 from our
>> application, thereby using features like SMS-notification (+CMTI),
>> signal-strength (+CSQ), etc.
>>
>>
>>
>> Does our approach make sense?
>> We will be grateful to any help.
>
> Why not ask the modem manager team about this?  The kernel doesn't care
> what you do with the device links :)
>
> thanks,
>
> greg k-h



-- 
Regards,
Ajay

Re: Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

[Pavel Machek]

Hi!

> > We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's
> > MC8090 modem, and we have a requirement wherein we need to have access
> > to the modem-serial-port (from our user-application that is).
> > 
> > Right now, we see that /usr/sbin/ModemManager is always connected to
> > /dev/ttyUSB3 (which means we cannot connect to the port from our
> > application at the same time, or even if we can, received-data will be
> > at best inconsistent).
> > 
> > 
> > We are thinking of the following ::
> > 
> > * Initially, let nmcli and ModemManager do their work, and let them
> > bring the WWAN interface up.
> > 
> > * Once this happens, we permanently-down the ModemManager from our
> > application-binary, thereby freeing up /dev/ttyUSB3.
> > 
> > * Thereafter, we are free to connect to /dev/ttyUSB3 from our
> > application, thereby using features like SMS-notification (+CMTI),
> > signal-strength (+CSQ), etc.
> > 
> > 
> > 
> > Does our approach make sense?
> > We will be grateful to any help.
> 
> Why not ask the modem manager team about this?  The kernel doesn't care
> what you do with the device links :)

Arguably, kernel is doing its job pretty badly when it comes to modems.

1) it does not hide differences between different modems (nokia modem is network
protocol, some modems are single tty, some modems are multiple ttys, different AT
command sets...)

2) it does not allow userland applications to share a GSM modem in a reasonable way.
Being able to read signal strength while PPP is connected would be nice, for example.

Anyway, when kernel fails to do its job, there's often userland daemon that can do it.

ofono seems to be the cannonical one there, and it seems to do the job rather well.

So... I guess the original author should take a look at ofono.

										Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html