Re: Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?
- From: Ajay Garg <ajaygargnsit gmail com>
- To: Alex Ferm <aferm petropower com>
- Cc: networkmanager-list <networkmanager-list gnome org>
- Subject: Re: Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?
- Date: Thu, 11 Aug 2016 19:31:17 +0530
Hi Alex.
Right now, the modem is being used in Direct-IP mode (using both
"sierra" and "sierra_net" drivers).
Have posted a query https://lkml.org/lkml/2016/8/11/135, specifying
the details, and having some queries.
On Thu, Aug 11, 2016 at 6:45 PM, Alex Ferm <aferm petropower com> wrote:
From the specifications it looks like your modem has a QMI interface. I'm
surprised ModemManager isn't using that. When ModemManager connects to a QMI
modem it uses a proxy, which allows multiple applications to access the
interface.
Alex Ferm
PetroPower, LLC.
3003 E. 37th Street N.
Suite 100
Wichita, KS 67219
Phone: (316) 361-0222
Toll Free: (877) 265-6581
Fax: (316) 361-0967
On 08/10/2016 12:36 AM, Ajay Garg wrote:
I might point that if I comment the "respawn" option in
"/etc/init/modemmanager.conf" and then start the modem-manager binary
from command-line, the broadband connection gets disconnected as soon
as I exit the binary.
So, I guess the answer to my question is "no", but just want to confirm.
Also, if the answer is in fact "no", is there a way to change the answer?
On Wed, Aug 10, 2016 at 10:00 AM, Ajay Garg <ajaygargnsit gmail com>
wrote:
Any pointers, please?
On Tue, Aug 9, 2016 at 12:46 PM, Ajay Garg <ajaygargnsit gmail com>
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.
Thanks and Regards,
Ajay
--
Regards,
Ajay
_______________________________________________
networkmanager-list mailing list
networkmanager-list gnome org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
--
Regards,
Ajay
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]