Re: Unable to get IPv4 over LTE

2016-01-19 Thread Vincent Bernat
❦ 19 janvier 2016 23:59 +0100, Aleksander Morgado  : > Would be interesting to see what ModemManager says in each of those > tries (--debug); and check which are the IP details given by the modem > for each case, before we even try to run the DHCP client. Could you > gather logs for both situatio

Re: Unable to get IPv4 over LTE

2016-01-19 Thread Dan Williams
On Tue, 2016-01-19 at 23:59 +0100, Aleksander Morgado wrote: > Hey Vincent! > > On Tue, Jan 19, 2016 at 10:08 PM, Vincent Bernat > wrote: > > I got an odd problem since some time. > > > > Bus 002 Device 045: ID 1199:a001 Sierra Wireless, Inc. > > ii modemmanager 1.4.12-1 amd64

Re: Unable to get IPv4 over LTE

2016-01-19 Thread Aleksander Morgado
Hey Vincent! On Tue, Jan 19, 2016 at 10:08 PM, Vincent Bernat wrote: > I got an odd problem since some time. > > Bus 002 Device 045: ID 1199:a001 Sierra Wireless, Inc. > ii modemmanager 1.4.12-1 amd64 D-Bus service for managing > modems > Linux zoro 4.3.0-1-amd64 #1 SMP Debian

Unable to get IPv4 over LTE

2016-01-19 Thread Vincent Bernat
Hey! I got an odd problem since some time. Bus 002 Device 045: ID 1199:a001 Sierra Wireless, Inc. ii modemmanager 1.4.12-1 amd64 D-Bus service for managing modems Linux zoro 4.3.0-1-amd64 #1 SMP Debian 4.3.3-5 (2016-01-04) x86_64 GNU/Linux When I am connected over LTE for the

Re: ModemManager using QMI doesnt always work in the first attemp.

2016-01-19 Thread Aleksander Morgado
On Tue, Jan 19, 2016 at 9:55 PM, c.lobr...@gmail.com wrote: > >> I have also noticed that ModemManager uses not documented AT+CFUN modes: >> >> root at ccimx6sbc:~# mmcli -m 0 --set-power-state-off >> ModemManager[791]: Modem powered off... may no longer be accessible >> successfully set new powe

Re: ModemManager using QMI doesnt always work in the first attemp.

2016-01-19 Thread c.lobr...@gmail.com
Hi José, Aleksander, my two cents here > I have also noticed that ModemManager uses not documented AT+CFUN modes: > > root at ccimx6sbc:~# mmcli -m 0 --set-power-state-off > ModemManager[791]: Modem powered off... may no longer be accessible > successfully set new power state in the modem >

Re: ModemManager using QMI doesnt always work in the first attemp.

2016-01-19 Thread Aleksander Morgado
Hey! On Tue, Jan 19, 2016 at 6:36 PM, José wrote: > Looking at > http://cgit.freedesktop.org/ModemManager/ModemManager/tree/plugins/telit/mm-plugin-telit.c?id=1.4.12 > seems like the Telit plugin only handles tty port, but I am using QMI > with the Telit LE910. Should it still be using the Telit

Re: ModemManager using QMI doesnt always work in the first attemp.

2016-01-19 Thread José
Looking at http://cgit.freedesktop.org/ModemManager/ModemManager/tree/plugins/telit/mm-plugin-telit.c?id=1.4.12 seems like the Telit plugin only handles tty port, but I am using QMI with the Telit LE910. Should it still be using the Telit plugin? The following lines appear at the log (in this ord

Re: ModemManager using QMI doesnt always work in the first attemp.

2016-01-19 Thread Aleksander Morgado
On Tue, Jan 19, 2016 at 4:51 PM, José wrote: > I have update to the last firmware (17.01.522 1 [Oct 16 2014 > 07:00:00]) and the issue is still reproducible. > > I am almost sure that the issue is related to power management. > > When the modem is in AT+CFUN=4, trying to enable it with ModemMana

Re: ModemManager using QMI doesnt always work in the first attemp.

2016-01-19 Thread José
I have update to the last firmware (17.01.522 1 [Oct 16 2014 07:00:00]) and the issue is still reproducible. I am almost sure that the issue is related to power management. When the modem is in AT+CFUN=4, trying to enable it with ModemManager (mmcli -m 0 -e) does not work. Trying to change the

Re: Trying to get MC7354 connected to Verizon data network

2016-01-19 Thread Bjørn Mork
Aleksander Morgado writes: > On Tue, Jan 19, 2016 at 11:51 AM, Bjørn Mork wrote: >>> On Mon, Jan 18, 2016 at 10:15 PM, Glenn Washburn >>> wrote: "curl -v --interface wwan0 http://www.google.com"; >>> >>> You're binding the request to the wwan interface, which I assume it's >>> because it is

Re: Trying to get MC7354 connected to Verizon data network

2016-01-19 Thread Aleksander Morgado
On Tue, Jan 19, 2016 at 11:51 AM, Bjørn Mork wrote: >> On Mon, Jan 18, 2016 at 10:15 PM, Glenn Washburn >> wrote: >>> "curl -v --interface wwan0 http://www.google.com"; >> >> You're binding the request to the wwan interface, which I assume it's >> because it isn't the default route. >> >> Try to

Re: Trying to get MC7354 connected to Verizon data network

2016-01-19 Thread Bjørn Mork
Aleksander Morgado writes: > On Mon, Jan 18, 2016 at 10:15 PM, Glenn Washburn > wrote: >> "curl -v --interface wwan0 http://www.google.com"; > > You're binding the request to the wwan interface, which I assume it's > because it isn't the default route. > > Try to disable the reverse path filteri

Re: ModemManager using QMI doesnt always work in the first attemp.

2016-01-19 Thread Aleksander Morgado
On 19/01/16 10:13, José wrote: > The problem only occurs if the LE910 was in low power mode (AT+CFUN=4) when > plugged to the embbeded device. Does ModemManager manage power state modes? > Should it automatically full enable the modem (AT+CFUN=1) when issuing > mmcli --simple-connect? > Yes, tha

Re: ModemManager using QMI doesnt always work in the first attemp.

2016-01-19 Thread José
The problem only occurs if the LE910 was in low power mode (AT+CFUN=4) when plugged to the embbeded device. Does ModemManager manage power state modes? Should it automatically full enable the modem (AT+CFUN=1) when issuing mmcli --simple-connect? I am going to test with a new firmware I have recei