[ANN] ModemManager 1.2-rc1

[Aleksander Morgado]

Hey,

> 
>> If you have modems around, please test them with this tagged version and
>> report problems before we release 1.2 in the following weeks (likely
>> around Dec 20th).
> 
> A short report: (with master of mm, libmbim, libqmi from 12.DEC2013)
> 
> It looks good to me. 
> 
> But I have some things. 
> 
> The MF821D (O2-surfstick) prefers ppp via /dev/ttyUSB2 instead of using wwan0.
> Where can I changed it?
> 

Do you have debug logs for that one? Unless it's an Icera-based ZTE
device, the device shouldn't try to use wwan0 for data connection, as
there is no ZTE-specific bearer object in the plugin implementing
net-based connections.


> mmcli -b 0
> 
> is a little bit confusing to me. 
> 
> One connection (K5006Z, qmi )says only: 
> 
> IPv6 configuration | method: 'dhcp'
> 

'dhcp' here means that you should run a DHCP client on the net interface
to gather IP setup. For the QMI-based devices, it is always 'dhcp' there
(currently, can be changed).


> Another connection (K5150 mbim) is much more verbose:
> 
> IPv6 configuration | method: 'static'
> 
> with address, prefix, gateway and DNS.
> 

For MBIM-based devices, IP configuration is always 'static', so once
connected we ask the modem using MBIM which is the IP configuration that
we should use in the net device. We expose that info in the bearer
object so that e.g. NetworkManager can grab it and apply it in the
interface. Originally MBIM devices also had 'dhcp' as QMI ones, but we
found several ones that didn't support it, so we just defaulted it to
'static' as all known ones seem to work ok.

> Is there a way to get the information independent of dhcp/static, because I 
> see the info in the logfile. (e.g. for DNS) in both cases.
> 

Yeah, for QMI devices we could change the default setup to also use
'static' instead of 'dhcp', as we actually query for the IP setup info
anyway to show in the logs.

> Strange things I observed: The modemmanager only works reliable  with kernel 
> 3.12.x.
> Under kernel 3.13rc3 / linux-next it gets timeouts via /dev/cdc-wdm0 with mbim 
> and with qmi.
> 

I'm in 3.12 myself, didn't try with 3.13 yet. Bjørn may now more?

-- 
Aleksander