Re: Getting MC7455 static-ip to work

[Bjørn Mork]

Dan Williams  writes:
> On Mon, 2018-03-05 at 17:56 +0100, Aleksander Morgado wrote:
>> > > 
>> > > Was the wwan0 interface down while you executed simple-connect?
>> > 
>> > wwan0 being up is the most likely cause.  But seeing the debug logs
>> > to
>> > confirm this would be good.
>> > 
>> > I started thinking about solving this in the driver, but ended up
>> > falling back to the original decision: The interface must be
>> > down.  This
>> > is the way it is.  You should respond to any error when attempting
>> > to
>> > write to the sysfs file.
>> 
>> Should we bring the interface down ourselves in MM when trying to
>> write to the sysfs file?
>
> Yeah, set_expected_data_format() should check if the interface is up
> and then take it down, set the data format, and bring it back up.
>
> This would kill a data connection if somebody ran "qmicli --set-
> expected-data-format=xxx" while the connection was active, but then
> they shouldn't do that...

Exactly.  There is no way you can make the device work both before and
after a data format change, so maintaining a connection while switching
format makes no sense.


Bjørn
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Getting MC7455 static-ip to work

[Dan Williams]

On Mon, 2018-03-05 at 17:56 +0100, Aleksander Morgado wrote:
> > > 
> > > Was the wwan0 interface down while you executed simple-connect?
> > 
> > wwan0 being up is the most likely cause.  But seeing the debug logs
> > to
> > confirm this would be good.
> > 
> > I started thinking about solving this in the driver, but ended up
> > falling back to the original decision: The interface must be
> > down.  This
> > is the way it is.  You should respond to any error when attempting
> > to
> > write to the sysfs file.
> 
> Should we bring the interface down ourselves in MM when trying to
> write to the sysfs file?

Yeah, set_expected_data_format() should check if the interface is up
and then take it down, set the data format, and bring it back up.

This would kill a data connection if somebody ran "qmicli --set-
expected-data-format=xxx" while the connection was active, but then
they shouldn't do that...

Dan
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Getting MC7455 static-ip to work

[Aleksander Morgado]

>>
>> Was the wwan0 interface down while you executed simple-connect?
>
> wwan0 being up is the most likely cause.  But seeing the debug logs to
> confirm this would be good.
>
> I started thinking about solving this in the driver, but ended up
> falling back to the original decision: The interface must be down.  This
> is the way it is.  You should respond to any error when attempting to
> write to the sysfs file.

Should we bring the interface down ourselves in MM when trying to
write to the sysfs file?

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Getting MC7455 static-ip to work

[Bjørn Mork]

Aleksander Morgado  writes:
> On Mon, Mar 5, 2018 at 2:55 AM, Steven P  wrote:
>> $ pacman -Qi libqmi libmbim linux modemmanager | grep -B 1 Version
>> Name: libqmi
>> Version : 1.20.0-1
>> --
>> Name: libmbim
>> Version : 1.16.0-1
>> --
>> Name: linux
>> Version : 4.15.6-1
>> --
>> Name: modemmanager
>> Version : 1.8rc1+6+g0f377f94-1
>>
>
> Oh, well, yes, that is like the latest of the latest :)
>
>> I did see an occasional error in dmesg about that interface that happened 
>> when I executed simple-connect - however during one of my tests I made sure 
>> that wwan0 was brought down when I made the connection and the error didn't 
>> occur. If this sounds related, let me know and I'll see if I can reproduce 
>> it (not at my laptop atm, just happened to have the above info in my notes)
>>
>
> Any chance you can get us some ModemManager debug logs while
> reproducing the issue? See:
> https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
>
> Really would like to see why it couldn't switch the wwan to raw-ip in
> the kernel.
>
> Was the wwan0 interface down while you executed simple-connect?

wwan0 being up is the most likely cause.  But seeing the debug logs to
confirm this would be good.

I started thinking about solving this in the driver, but ended up
falling back to the original decision: The interface must be down.  This
is the way it is.  You should respond to any error when attempting to
write to the sysfs file.



Bjørn
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Setting up 4G in D-Link DWM-222 (was Re: 4G USB dongles known to work on Linux)

[Aleksander Morgado]

Hey,

On Mon, Mar 5, 2018 at 12:03 AM, Henrique Ferreiro
 wrote:
> Thanks everybody for all answers. I checked the dd-wrt wiki page and finally
> went for the D-Link DWM-222 (there weren't much more options to buy from
> local retailers).
>
> I have a few questions regarding ModemManager after testing this modem for a
> while. I managed to connect almost with no manual intervention but 4G
> doesn't seem to work.
>
> First thing, to test 4G I had to use "mmcli -m 0
> --set-current-capabilities=lte" and realise it wouldn't connect. Is there
> any other way to check 4G status? "nmcli c" displayed the connection type as
> "gsm", but I would expect connection errors in ModemManager's journal or
> some way to do this using "mmcli".
>
> Second, can you help debug why I cannot setup 4G in this particular modem?
>

The "gsm" connection type name in NetworkManager is misleading. We use
"gsm" to refer to all 3GPP connection types (e.g. GSM, GPRS, EDGE,
UMTS, HSPA, LTE...).
What is the output of "mmcli -m 0" when you have the modem connected?
You shouldn't have needed to --set-current-capabilities.

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Getting MC7455 static-ip to work

[Aleksander Morgado]

Hey,

On Mon, Mar 5, 2018 at 2:55 AM, Steven P  wrote:
> $ pacman -Qi libqmi libmbim linux modemmanager | grep -B 1 Version
> Name: libqmi
> Version : 1.20.0-1
> --
> Name: libmbim
> Version : 1.16.0-1
> --
> Name: linux
> Version : 4.15.6-1
> --
> Name: modemmanager
> Version : 1.8rc1+6+g0f377f94-1
>

Oh, well, yes, that is like the latest of the latest :)

> I did see an occasional error in dmesg about that interface that happened 
> when I executed simple-connect - however during one of my tests I made sure 
> that wwan0 was brought down when I made the connection and the error didn't 
> occur. If this sounds related, let me know and I'll see if I can reproduce it 
> (not at my laptop atm, just happened to have the above info in my notes)
>

Any chance you can get us some ModemManager debug logs while
reproducing the issue? See:
https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/

Really would like to see why it couldn't switch the wwan to raw-ip in
the kernel.

Was the wwan0 interface down while you executed simple-connect?

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel