Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-14 Thread Thomas Schäfer 
Am Samstag, 14. Januar 2017, 01:16:07 schrieb Martin MOKREJŠ:
>   I think NM could save some effort by first checking for
> /proc/sys/net/ipv6/conf/ttyUSB0, and only after that proceed with more
> detailed checks. Second, does ttyUSB0 support IPv6 at all? It does same for
> tun0 and tun1 interfaces. I just do not have IPv6 enabled in kernel, at
> all.


Please don't do to much at once. 

/dev/ttyUSB0 is *no* IP-Interface, it is just a serial interface, it will 
never appear at /proc/sys/net/ipv?/*

/dev/ttyUSB was/is used by older modems for ppp

newer modems use /dev/ttyUSBX only for controlling/monitoring 

ppp0 is an ip-Interface.

Regards,
Thomas


PS: Thanks for investigating IPv6-things, but I think with this modem and an 
bad ISP you have no chance. (based on the informations you already collected)

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

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-14 Thread Aleksander Morgado 
On Sat, Jan 14, 2017 at 1:16 AM, Martin MOKREJŠ  wrote:
>   Anyway, there are a few lines about the cdc-wdm0 but does not seem to be 
> much verbose. A few AT commands failed but on the ttyUSB1.

Yeah, no AT command was correctly replied in the cdc-wdm interface so
we couldn't use it :/

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

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-13 Thread Aleksander Morgado 
On Fri, Jan 13, 2017 at 10:12 PM, Martin MOKREJŠ  wrote:
>   thank you Alexander for clarification, I infer there is something wrong 
> with my cdc-wdm then. Isn't there anything interesting in the NM debug logs I 
> sent to the list already?

This is the only interesting thing I found:

Jan 12 12:18:07 kolb615b ModemManager[7104]:   Creating modem
with plugin 'Huawei' and '4' ports
Jan 12 12:18:07 kolb615b ModemManager[7104]:   Could not grab
port (usbmisc/cdc-wdm0): 'Cannot add port 'usbmisc/cdc-wdm0',
unsupported'

Could you send the full ModemManager debug logs when the modem is
plugged in? I guess we'll just see AT commands timing out during the
probing of cdc-wdm0, but who knows.

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

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-13 Thread Martin MOKREJŠ 
Hi ,
  thank you Alexander for clarification, I infer there is something wrong with 
my cdc-wdm then. Isn't there anything interesting in the NM debug logs I sent 
to the list already?

  I returned from win7 now. I can confirm Win7 use Mobile broadband network 
card #9, using driver ew_wwanecm.sys, Huawei 1.11.2013, version 1.0.10.0. The 
modem is switched into the non-sub-storage mode, like in Linux (USB ID: 
0x12d1:0x1506). It uses the wwan0 interface based on the same MAC address: 
00:1e:10:1f:00:00.

  T-Mobile.cz did not provide my DHCP queries with IPv6 answers, only IPv4 
values were obtained.
Martin
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-13 Thread Martin MOKREJŠ 
Re-sending, with attachments.

Hi Thomas,

>>> This device should use the wwan-device by huawei_cdc_ncm.
>>
>> I am glad to hear that as well, but can you tell me if ModemManager
>> realizes that wwan0 was renamed by OpenRC to wwp0s29u1u2i2 ? Does
>> that interfere anyhow?
>>
> 
> As Aleksander already mentioned this is an earlier step.
> 
> [  129.872093] usb 2-4: new high-speed USB device number 3 using
> ehci-pci
> 
> [  130.021780] usb 2-4: New USB device found, idVendor=12d1,
> idProduct=14fe
> 
> [  130.021791] usb 2-4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> 
> [  130.021797] usb 2-4: Product: HUAWEI_MOBILE
> 
> 
> [  130.021803] usb 2-4: Manufacturer: HUAWEI_MOBILE
> 
> 
> [  130.021809] usb 2-4: SerialNumber: 0123456789ABCDEF
> 
> 
> [  130.694224] usb-storage 2-4:1.0: USB Mass Storage device detected
> [  130.699161] scsi host4: usb-storage 2-4:1.0
> [  130.699625] usbcore: registered new interface driver usb-storage
> [  130.702706] usbcore: registered new interface driver uas
> [  131.503661] usb 2-4: USB disconnect, device number 3
> [  132.204080] usb 2-4: new high-speed USB device number 4 using ehci-pci
> [  132.353537] usb 2-4: New USB device found, idVendor=12d1, idProduct=1506
> [  132.353546] usb 2-4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [  132.353552] usb 2-4: Product: HUAWEI_MOBILE
> [  132.353558] usb 2-4: Manufacturer: HUAWEI_MOBILE
> [  132.388055] usb-storage 2-4:1.3: USB Mass Storage device detected
> [  132.393422] scsi host4: usb-storage 2-4:1.3
> [  132.394744] usb-storage 2-4:1.4: USB Mass Storage device detected
> [  132.399369] scsi host5: usb-storage 2-4:1.4
> [  133.034249] usbcore: registered new interface driver usbserial
> [  133.034322] usbcore: registered new interface driver usbserial_generic

I have only 

CONFIG_USB_SERIAL=y
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_SIMPLE is not set
CONFIG_USB_SERIAL_WWAN=m
CONFIG_USB_SERIAL_OPTION=m

# lsmod
Module  Size  Used by
ppp_deflate 3938  0
bsd_comp5226  0
ppp_async   6915  1
ppp_generic24159  7 ppp_async,bsd_comp,ppp_deflate
slhc5235  1 ppp_generic
option 42576  2
usb_wwan7919  1 option
...
uas13205  0
usb_storage52299  2 uas,ums_realtek
#

> [  133.034381] usbserial: USB Serial support registered for generic
> [  133.074616] usbcore: registered new interface driver option
> [  133.075481] usbcore: registered new interface driver cdc_ncm
> [  133.077831] usbserial: USB Serial support registered for GSM modem
> (1-port)
> [  133.078199] option 2-4:1.0: GSM modem (1-port) converter detected
> [  133.080959] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB0
> [  133.081091] option 2-4:1.1: GSM modem (1-port) converter detected
> [  133.086826] usbcore: registered new interface driver cdc_wdm
> [  133.088603] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB1
> [  133.158799] huawei_cdc_ncm 2-4:1.2: MAC-Address: 00:1e:10:1f:00:00
> [  133.158809] huawei_cdc_ncm 2-4:1.2: setting rx_max = 16384
> [  133.164445] huawei_cdc_ncm 2-4:1.2: NDP will be placed at end of
> frame for this device.
> [  133.165544] huawei_cdc_ncm 2-4:1.2: cdc-wdm0: USB WDM device
> [  133.166389] huawei_cdc_ncm 2-4:1.2 wwan0: register 'huawei_cdc_ncm'
> at usb-:00:1d.7-4, Huawei CDC NCM device, 00:1e:10:1f:00:00
> [  133.166545] usbcore: registered new interface driver huawei_cdc_ncm
> [  133.181321] huawei_cdc_ncm 2-4:1.2 wwp0s29f7u4i2: renamed from wwan0
> [  133.420876] scsi 4:0:0:0: CD-ROMHUAWEI   Mass Storage
> 2.31 PQ: 0 ANSI: 2
> [  133.425589] scsi 4:0:0:0: Attached scsi generic sg1 type 5
> [  133.426253] scsi 5:0:0:0: Direct-Access HUAWEI   TF CARD Storage
> 2.31 PQ: 0 ANSI: 2
> [  133.432118] sd 5:0:0:0: Attached scsi generic sg2 type 0
> [  133.435881] sd 5:0:0:0: [sdb] Attached SCSI removable disk
> [  133.468859] sr 4:0:0:0: [sr0] scsi-1 drive
> [  133.468867] cdrom: Uniform CD-ROM driver Revision: 3.20

Well today the modem was also switched by usb_modeswitch automatically. Looks 
sometimes it works, sometimes not.

   50.634264] usb 2-1.2: new high-speed USB device number 5 using ehci-pci
[   50.786230] usb 2-1.2: New USB device found, idVendor=12d1, idProduct=14fe
[   50.786237] usb 2-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[   50.786242] usb 2-1.2: Product: HUAWEI_MOBILE
[   50.786245] usb 2-1.2: Manufacturer: HUAWEI_MOBILE
[   50.786248] usb 2-1.2: SerialNumber: 0123456789ABCDEF
[   50.821657] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[   50.821737] scsi host6: usb-storage 2-1.2:1.0
[   51.839751] scsi 6:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
[   51.843589] sr 6:0:0:0: [sr1] scsi-1 drive
[   51.843892] sr 6:0:0:0: Attached scsi CD-ROM sr1
[   51.844042] sr 6:0:0:0: Attached scsi generic sg2 type 5
[   51.845797]

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-13 Thread Martin MOKREJŠ 
Hi Thomas,

>>> This device should use the wwan-device by huawei_cdc_ncm.
>>
>> I am glad to hear that as well, but can you tell me if ModemManager
>> realizes that wwan0 was renamed by OpenRC to wwp0s29u1u2i2 ? Does
>> that interfere anyhow?
>>
> 
> As Aleksander already mentioned this is an earlier step.
> 
> [  129.872093] usb 2-4: new high-speed USB device number 3 using
> ehci-pci
> 
> [  130.021780] usb 2-4: New USB device found, idVendor=12d1,
> idProduct=14fe
> 
> [  130.021791] usb 2-4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> 
> [  130.021797] usb 2-4: Product: HUAWEI_MOBILE
> 
> 
> [  130.021803] usb 2-4: Manufacturer: HUAWEI_MOBILE
> 
> 
> [  130.021809] usb 2-4: SerialNumber: 0123456789ABCDEF
> 
> 
> [  130.694224] usb-storage 2-4:1.0: USB Mass Storage device detected
> [  130.699161] scsi host4: usb-storage 2-4:1.0
> [  130.699625] usbcore: registered new interface driver usb-storage
> [  130.702706] usbcore: registered new interface driver uas
> [  131.503661] usb 2-4: USB disconnect, device number 3
> [  132.204080] usb 2-4: new high-speed USB device number 4 using ehci-pci
> [  132.353537] usb 2-4: New USB device found, idVendor=12d1, idProduct=1506
> [  132.353546] usb 2-4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [  132.353552] usb 2-4: Product: HUAWEI_MOBILE
> [  132.353558] usb 2-4: Manufacturer: HUAWEI_MOBILE
> [  132.388055] usb-storage 2-4:1.3: USB Mass Storage device detected
> [  132.393422] scsi host4: usb-storage 2-4:1.3
> [  132.394744] usb-storage 2-4:1.4: USB Mass Storage device detected
> [  132.399369] scsi host5: usb-storage 2-4:1.4
> [  133.034249] usbcore: registered new interface driver usbserial
> [  133.034322] usbcore: registered new interface driver usbserial_generic

I have only 

CONFIG_USB_SERIAL=y
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_SIMPLE is not set
CONFIG_USB_SERIAL_WWAN=m
CONFIG_USB_SERIAL_OPTION=m

# lsmod
Module  Size  Used by
ppp_deflate 3938  0
bsd_comp5226  0
ppp_async   6915  1
ppp_generic24159  7 ppp_async,bsd_comp,ppp_deflate
slhc5235  1 ppp_generic
option 42576  2
usb_wwan7919  1 option
...
uas13205  0
usb_storage52299  2 uas,ums_realtek
#

> [  133.034381] usbserial: USB Serial support registered for generic
> [  133.074616] usbcore: registered new interface driver option
> [  133.075481] usbcore: registered new interface driver cdc_ncm
> [  133.077831] usbserial: USB Serial support registered for GSM modem
> (1-port)
> [  133.078199] option 2-4:1.0: GSM modem (1-port) converter detected
> [  133.080959] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB0
> [  133.081091] option 2-4:1.1: GSM modem (1-port) converter detected
> [  133.086826] usbcore: registered new interface driver cdc_wdm
> [  133.088603] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB1
> [  133.158799] huawei_cdc_ncm 2-4:1.2: MAC-Address: 00:1e:10:1f:00:00
> [  133.158809] huawei_cdc_ncm 2-4:1.2: setting rx_max = 16384
> [  133.164445] huawei_cdc_ncm 2-4:1.2: NDP will be placed at end of
> frame for this device.
> [  133.165544] huawei_cdc_ncm 2-4:1.2: cdc-wdm0: USB WDM device
> [  133.166389] huawei_cdc_ncm 2-4:1.2 wwan0: register 'huawei_cdc_ncm'
> at usb-:00:1d.7-4, Huawei CDC NCM device, 00:1e:10:1f:00:00
> [  133.166545] usbcore: registered new interface driver huawei_cdc_ncm
> [  133.181321] huawei_cdc_ncm 2-4:1.2 wwp0s29f7u4i2: renamed from wwan0
> [  133.420876] scsi 4:0:0:0: CD-ROMHUAWEI   Mass Storage
> 2.31 PQ: 0 ANSI: 2
> [  133.425589] scsi 4:0:0:0: Attached scsi generic sg1 type 5
> [  133.426253] scsi 5:0:0:0: Direct-Access HUAWEI   TF CARD Storage
> 2.31 PQ: 0 ANSI: 2
> [  133.432118] sd 5:0:0:0: Attached scsi generic sg2 type 0
> [  133.435881] sd 5:0:0:0: [sdb] Attached SCSI removable disk
> [  133.468859] sr 4:0:0:0: [sr0] scsi-1 drive
> [  133.468867] cdrom: Uniform CD-ROM driver Revision: 3.20

Well today the modem was also switched by usb_modeswitch automatically. Looks 
sometimes it works, sometimes not.

   50.634264] usb 2-1.2: new high-speed USB device number 5 using ehci-pci
[   50.786230] usb 2-1.2: New USB device found, idVendor=12d1, idProduct=14fe
[   50.786237] usb 2-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[   50.786242] usb 2-1.2: Product: HUAWEI_MOBILE
[   50.786245] usb 2-1.2: Manufacturer: HUAWEI_MOBILE
[   50.786248] usb 2-1.2: SerialNumber: 0123456789ABCDEF
[   50.821657] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[   50.821737] scsi host6: usb-storage 2-1.2:1.0
[   51.839751] scsi 6:0:0:0: CD-ROMHUAWEI   Mass Storage 2.31 
PQ: 0 ANSI: 2
[   51.843589] sr 6:0:0:0: [sr1] scsi-1 drive
[   51.843892] sr 6:0:0:0: Attached scsi CD-ROM sr1
[   51.844042] sr 6:0:0:0: Attached scsi generic sg2 type 5
[   51.845797] scsi 6:0:0:1: Direct-Access

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-13 Thread Thomas Schäfer 
Am 12.01.2017 um 23:52 schrieb Martin MOKREJŠ:
> Hi Thomas,
> 
> Thomas Schäfer wrote:
>> Hi,
>> 
>> I am a little bit surprised that the modem uses the ppp-interface
>> in your case. When I read your logfiles right, then you have a
>> device which is sold under the name "Speedsick LTE V" in Germany.
> 
> How do you achieve non-PPP option in nm-applet? Whenever I select
> "Mobile broadband" there are these option driver-based and PPP-based
> fields. Should I use "Ethernet" instead?


This was already answered by Aleksander. Independent of the applet there
are only some lines in nm-connection-profile:

[connection]
id=tm46auto
uuid=e1cc7077-4d5b-43cd-8bdc-4659d68228fc
type=gsm
autoconnect=false
permissions=
secondaries=

[gsm]
apn=internet.telekom
number=*99#
password-flags=4
pin-flags=4
username=tm

[ipv4]
dns-search=
method=auto

[ipv6]
dns-search=
method=auto



> 
>> 
>> This device should use the wwan-device by huawei_cdc_ncm.
> 
> I am glad to hear that as well, but can you tell me if ModemManager
> realizes that wwan0 was renamed by OpenRC to wwp0s29u1u2i2 ? Does
> that interfere anyhow?
> 

As Aleksander already mentioned this is an earlier step.

[  129.872093] usb 2-4: new high-speed USB device number 3 using
ehci-pci

[  130.021780] usb 2-4: New USB device found, idVendor=12d1,
idProduct=14fe

[  130.021791] usb 2-4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3

[  130.021797] usb 2-4: Product: HUAWEI_MOBILE


[  130.021803] usb 2-4: Manufacturer: HUAWEI_MOBILE


[  130.021809] usb 2-4: SerialNumber: 0123456789ABCDEF


[  130.694224] usb-storage 2-4:1.0: USB Mass Storage device detected
[  130.699161] scsi host4: usb-storage 2-4:1.0
[  130.699625] usbcore: registered new interface driver usb-storage
[  130.702706] usbcore: registered new interface driver uas
[  131.503661] usb 2-4: USB disconnect, device number 3
[  132.204080] usb 2-4: new high-speed USB device number 4 using ehci-pci
[  132.353537] usb 2-4: New USB device found, idVendor=12d1, idProduct=1506
[  132.353546] usb 2-4: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[  132.353552] usb 2-4: Product: HUAWEI_MOBILE
[  132.353558] usb 2-4: Manufacturer: HUAWEI_MOBILE
[  132.388055] usb-storage 2-4:1.3: USB Mass Storage device detected
[  132.393422] scsi host4: usb-storage 2-4:1.3
[  132.394744] usb-storage 2-4:1.4: USB Mass Storage device detected
[  132.399369] scsi host5: usb-storage 2-4:1.4
[  133.034249] usbcore: registered new interface driver usbserial
[  133.034322] usbcore: registered new interface driver usbserial_generic
[  133.034381] usbserial: USB Serial support registered for generic
[  133.074616] usbcore: registered new interface driver option
[  133.075481] usbcore: registered new interface driver cdc_ncm
[  133.077831] usbserial: USB Serial support registered for GSM modem
(1-port)
[  133.078199] option 2-4:1.0: GSM modem (1-port) converter detected
[  133.080959] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB0
[  133.081091] option 2-4:1.1: GSM modem (1-port) converter detected
[  133.086826] usbcore: registered new interface driver cdc_wdm
[  133.088603] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB1
[  133.158799] huawei_cdc_ncm 2-4:1.2: MAC-Address: 00:1e:10:1f:00:00
[  133.158809] huawei_cdc_ncm 2-4:1.2: setting rx_max = 16384
[  133.164445] huawei_cdc_ncm 2-4:1.2: NDP will be placed at end of
frame for this device.
[  133.165544] huawei_cdc_ncm 2-4:1.2: cdc-wdm0: USB WDM device
[  133.166389] huawei_cdc_ncm 2-4:1.2 wwan0: register 'huawei_cdc_ncm'
at usb-:00:1d.7-4, Huawei CDC NCM device, 00:1e:10:1f:00:00
[  133.166545] usbcore: registered new interface driver huawei_cdc_ncm
[  133.181321] huawei_cdc_ncm 2-4:1.2 wwp0s29f7u4i2: renamed from wwan0
[  133.420876] scsi 4:0:0:0: CD-ROMHUAWEI   Mass Storage
2.31 PQ: 0 ANSI: 2
[  133.425589] scsi 4:0:0:0: Attached scsi generic sg1 type 5
[  133.426253] scsi 5:0:0:0: Direct-Access HUAWEI   TF CARD Storage
2.31 PQ: 0 ANSI: 2
[  133.432118] sd 5:0:0:0: Attached scsi generic sg2 type 0
[  133.435881] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[  133.468859] sr 4:0:0:0: [sr0] scsi-1 drive
[  133.468867] cdrom: Uniform CD-ROM driver Revision: 3.20




> Can you tell if ModemManager should run "usb_modeswitch -J -v 0x12d1
> -p 0x14fe" automagically (I have v.2.4.0 of usb_modeswitch")?
> 

I use also 2.4.0. But in my case it has its udev-rules for switching
automatically.


> I have compiled:

Ok, I use a standard kernel from opensuse at the moment.
Linux hpmini 4.9.2-1.g2d3c294-default #1 SMP PREEMPT Mon Jan 9 09:22:07
UTC 2017 (2d3c294) x86_64 x86_64 x86_64 GNU/Linux

I can provide the config, if you need it to compare. Here it would make
the mail to big.




> 
> 
>> 
>> Do have a chance to compare the behavour of your modem under
>> windows?
> 
> I can reboot to win7, but which window values I should screen-grab
> for you?

No screenshot. I want only to know if windows uses "network card" or

Re: ModemManager-1.6.2: does not work with Huawei E3372h-153

2017-01-13 Thread Martin MOKREJŠ 
Hi Aleksander,

Aleksander Morgado wrote:
> Hey Martin,
> 
> On Thu, Jan 12, 2017 at 9:46 PM, Martin MOKREJŠ  wrote:
>> I propose improving mmcli manpage. The EXAMPLES section should start with:
>> 1. how shall one figure out where is any modem seen
>> 2. how to read the status, shown "registered" and later "connected" states.
>> 3. although it seems it is not relevant to mmcli, a hint where to go next to 
>> get use of the "connected" modem would be very helpful.
>>
> 
> Any patch to increase documentation is totally welcome; even if they
> may not be perfect from the beginning, at least we would start the
> ball rolling to improve the docs.

I understand but I can only contribute by testing raising up ideas.

> 
>>
>> Aleksander Morgado wrote:
>>> On Thu, Jan 12, 2017 at 3:49 PM, Martin MOKREJŠ  wrote:
 # mmcli  --connect -m /org/freedesktop/ModemManager1/Modem/0
 error: no bearer was specified
>>>
>>> --connect is a bearer action, you need to pass a bearer object path,
>>> not a modem object path.
>>
>> I think "mmcli --help" could show some hints in the bearer section, like 
>> --create-bearer="apn=internet.t-mobile.xx"
>>
> 
> I don't like that as users may think the hints are the only allowed
> parameters... What we should do is make sure we keep the manpage up to

I understand but provided everybody trying to use a modem device under Linux 
saw a few times words APN and "internet.t-mobile.xx" it makes them familiar 
with this command.

> date, which I don't think is currently the case, it was written a
> looong time ago :)
> 
>>>
 # mmcli  --list-bearers -m /org/freedesktop/ModemManager1/Modem/0

 No bearers were found
>>>
>>> Ok, so you would first need to create a bearer with
>>> --create-bearer="key=value,..." in one of the modems.
>>>
>>> E.g.
>>>
>>> mmcli -m 0 --create-bearer="apn=internet"
>>
>> Yeah, but I again had to rescan my devices and only then I was able to use a 
>> modem. And it appeared at different index pos. Again, the EXAMPLES section 
>> could be improved so that a user can use it as a real step-by-step manual to 
>> get connected (to have a network device with an IP!).
> 
> Yep, agree, it would be good to have such a sequence in the EXAMPLES section.
> 
>>
>>>
>>> See:
>>> https://www.freedesktop.org/software/ModemManager/api/latest/gdbus-org.freedesktop.ModemManager1.Modem.html#gdbus-method-org-freedesktop-ModemManager1-Modem.CreateBearer
>>>
 # mmcli  --bearer -m /org/freedesktop/ModemManager1/Modem/0
 error: invalid path or index string specified: '-m'
>>>
>>> --bearer expects a bearer path or index (help says "--bearer=[PATH|INDEX]")
>>>
 # mmcli  --bearer
 error: no actions specified
>>>
>>> Same thing, --bearer expects a bearer path or index (help says
>>> "--bearer=[PATH|INDEX]")
>>>
 # mmcli  -b
 error: no actions specified
>>>
>>> Same thing, --bearer expects a bearer path or index (help says
>>> "--bearer=[PATH|INDEX]")
>>>
 # mmcli  -b -m /org/freedesktop/ModemManager1/Modem/0
 error: invalid path or index string specified: '-m'
>>>
>>> Same thing, --bearer expects a bearer path or index (help says
>>> "--bearer=[PATH|INDEX]")
>>
>>
>> How about mmcli being more friendly and output after the error message a 
>> list of my modems?
>>
> 
> Truth be told, I think there are more critical things to include in
> mmcli, like a machine-friendly output of the results that may be used
> easier in scripts. I know people that parse the output of mmcli
> commands in shell scripts (me included) and that is totally not
> ideal...
> 
>> # mmcli -L
>>
>> Found 1 modems:
>> /org/freedesktop/ModemManager1/Modem/2 [huawei] E3372
>>
>> #
>>
>> From "experience" I now know it is at index 2. Don't expect users are that 
>> smart when doing first steps. ;-)
>>
> 
> The index isn't fixed. The index just happens to be the number of

I know it moved because I exchanged my E3131s with E3372h-153, but still had to 
figure out what index version I should use. ;)

> modems detected since the startup of ModemManager; if you unplug and
> replug the modem the index will change. If you want to have a "name"
> for a modem that doesn't change e.g. across reboots, you can tag the
> USB port where the modem is available with a label that may be used
> later on instead of the modem index; e.g. "mmcli -m USB1" or so. See:
> https://sigquit.wordpress.com/2016/10/06/naming-devices-in-modemmanager/

Good to know. Does the "mmcli -m 0" command show the label anywhere? Does 
nm-applet create and use it automatically? Yeah, there was some scroll-down 
option to use the connection setting for "Any device" or "HUAWEI MOBILE 
DEVICE". Seemed too unspecific in both cases, but I rather stayed with the 
default "HUAWEI MOBILE DEVICE". I assume this was maybe a place where I could 
have specified the "label" (ehm, an existing label, right?). But was there an 
option to specify the label for the device in previous

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-13 Thread Martin MOKREJŠ 
Hi Aleksander,

Aleksander Morgado wrote:
> Hey,
> 
>>>
>>> I am a little bit surprised that the modem uses the ppp-interface in your
>>> case. When I read your logfiles right, then you have a device which is sold
>>> under the name "Speedsick LTE V" in Germany.

https://www.alza.cz/huawei-e3372h-d4474721.htm?catid=18851781

Inside there is a sticker label Huawei E3372h-153. On the paper box was just 
E3372h I think.

>>
>> How do you achieve non-PPP option in nm-applet? Whenever I select "Mobile 
>> broadband" there are these option driver-based and PPP-based fields. Should 
>> I use "Ethernet" instead?
>>
> 
> This is transparent to the user; the user doesn't know whether the
> connection will be through PPP or a WWAN network interface. The
> PPP-based fields are always there, but they won't apply if the
> connection goes through a WWAN network interface. This is not ideal,
> but right now there's no way for NM to know the type of interface that
> will be used for the connection later on; only when it has been
> already established.

Great. It you would find a find to tell users through nm-applet that they 
should not panic, it would be comfortable. Also, the Setup wizard of "Add new 
connection" could show some hints along the "Mobile broadband" versus 
"Ethernet" items. So I infer is correctly picked up the "Mobile broadband" item 
and in an ideal word, MM should have used the huawei_cdc_ncm-enabled port of my 
system.

> 
>>>
>>> This device should use the wwan-device by huawei_cdc_ncm.
>>
>> I am glad to hear that as well, but can you tell me if ModemManager realizes 
>> that wwan0 was renamed by OpenRC to wwp0s29u1u2i2 ? Does that interfere 
>> anyhow?
>>
> 
> That won't interfere no, as long as the network interface renaming
> rules are run before MM's own udev rules.
> 
>> Can you tell if ModemManager should run "usb_modeswitch -J -v 0x12d1 -p 
>> 0x14fe" automagically (I have v.2.4.0 of usb_modeswitch")?
>>
> 
> ModemManager doesn't run any usb_modeswitch command itself.
> usb_modeswitch is usually run way before the MM rules are applied.

OK, I will need to study the error message about non-existing hwdb.bin of my 
dmesg. usb_modeswitch is being run for my other modem E3131 so I should check 
whether the E3372h-153 is already recognized or not yet.

> 
>>>
>>> I know three different kinds of this device
>>>
>>> E3372 hilink-mode (cdc_ether) direct from huawei
>>> E3372 - Telekom - huawei_cdc_ncm
>>> K5160 - Vodafone -mbim/cdc_ether
>>>
>>> In no case a fallback to ppp should be needed.
>>
>> That is what I also thought, especially because Alexander asked me in the 
>> beginning of the thread if I have the CDC_NCM or CDC_NCM_HUAWEI enabled.
>>
> 
> Does the list of ports in the "mmcli -m [N]" output show any "cdc-wdm" port?

Aha, another case for the EXAMPLES in the manual page. ;-)

# mmcli -m 0

/org/freedesktop/ModemManager1/Modem/0 (device id 
'8535cb325128fbfaf101bd4f13c94eb41c4fb88b')
  -
  Hardware |   manufacturer: 'huawei'
   |  model: 'E3372'
   |   revision: '21.200.07.00.55'
   |  supported: 'gsm-umts'
   |current: 'gsm-umts'
   |   equipment id: ''
  -
  System   | device: 
'/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2'
   |drivers: 'option1, huawei_cdc_ncm'
   | plugin: 'Huawei'
   |   primary port: 'ttyUSB0'
   |  ports: 'ttyUSB0 (at), ttyUSB1 (at), wwp0s29u1u2i2 (net)'
  -
  Numbers  |   own : 'unknown'
  -
  Status   |   lock: 'none'
   | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 
(10)'
   |  state: 'connected'
   |power state: 'on'
   |access tech: 'lte'
   | signal quality: '41' (recent)
  -
  Modes|  supported: 'allowed: 2g; preferred: none
   |  allowed: 3g; preferred: none
   |  allowed: 4g; preferred: none
   |  allowed: 2g, 3g, 4g; preferred: none'
   |current: 'allowed: 2g, 3g, 4g; preferred: none'
  -
  Bands|  supported: 'unknown'
   |current: 'unknown'
  -
  IP   |  supported: 'ipv4'
  -
  3GPP |   imei: 'xx'
   |  enabled locks: 'none'
   |operator id: '23001'
   |  operator name: 'T-Mobile CZ'
   |   subscription: 'unknown'
   |   registration: 'home'
  -
  SIM  |   path: '/org/freedesktop/ModemManager1/SIM/0'

  -
  Bearers  |  paths: '/org/freedesktop/ModemManager1/Bearer/0'

#


Why is the driver called option1 instead of just option?

# grep OPTION

Re: ModemManager-1.6.2: does not work with Huawei E3372h-153

2017-01-13 Thread Aleksander Morgado 
Hey Martin,

On Thu, Jan 12, 2017 at 9:46 PM, Martin MOKREJŠ  wrote:
> I propose improving mmcli manpage. The EXAMPLES section should start with:
> 1. how shall one figure out where is any modem seen
> 2. how to read the status, shown "registered" and later "connected" states.
> 3. although it seems it is not relevant to mmcli, a hint where to go next to 
> get use of the "connected" modem would be very helpful.
>

Any patch to increase documentation is totally welcome; even if they
may not be perfect from the beginning, at least we would start the
ball rolling to improve the docs.

>
> Aleksander Morgado wrote:
>> On Thu, Jan 12, 2017 at 3:49 PM, Martin MOKREJŠ  wrote:
>>> # mmcli  --connect -m /org/freedesktop/ModemManager1/Modem/0
>>> error: no bearer was specified
>>
>> --connect is a bearer action, you need to pass a bearer object path,
>> not a modem object path.
>
> I think "mmcli --help" could show some hints in the bearer section, like 
> --create-bearer="apn=internet.t-mobile.xx"
>

I don't like that as users may think the hints are the only allowed
parameters... What we should do is make sure we keep the manpage up to
date, which I don't think is currently the case, it was written a
looong time ago :)

>>
>>> # mmcli  --list-bearers -m /org/freedesktop/ModemManager1/Modem/0
>>>
>>> No bearers were found
>>
>> Ok, so you would first need to create a bearer with
>> --create-bearer="key=value,..." in one of the modems.
>>
>> E.g.
>>
>> mmcli -m 0 --create-bearer="apn=internet"
>
> Yeah, but I again had to rescan my devices and only then I was able to use a 
> modem. And it appeared at different index pos. Again, the EXAMPLES section 
> could be improved so that a user can use it as a real step-by-step manual to 
> get connected (to have a network device with an IP!).

Yep, agree, it would be good to have such a sequence in the EXAMPLES section.

>
>>
>> See:
>> https://www.freedesktop.org/software/ModemManager/api/latest/gdbus-org.freedesktop.ModemManager1.Modem.html#gdbus-method-org-freedesktop-ModemManager1-Modem.CreateBearer
>>
>>> # mmcli  --bearer -m /org/freedesktop/ModemManager1/Modem/0
>>> error: invalid path or index string specified: '-m'
>>
>> --bearer expects a bearer path or index (help says "--bearer=[PATH|INDEX]")
>>
>>> # mmcli  --bearer
>>> error: no actions specified
>>
>> Same thing, --bearer expects a bearer path or index (help says
>> "--bearer=[PATH|INDEX]")
>>
>>> # mmcli  -b
>>> error: no actions specified
>>
>> Same thing, --bearer expects a bearer path or index (help says
>> "--bearer=[PATH|INDEX]")
>>
>>> # mmcli  -b -m /org/freedesktop/ModemManager1/Modem/0
>>> error: invalid path or index string specified: '-m'
>>
>> Same thing, --bearer expects a bearer path or index (help says
>> "--bearer=[PATH|INDEX]")
>
>
> How about mmcli being more friendly and output after the error message a list 
> of my modems?
>

Truth be told, I think there are more critical things to include in
mmcli, like a machine-friendly output of the results that may be used
easier in scripts. I know people that parse the output of mmcli
commands in shell scripts (me included) and that is totally not
ideal...

> # mmcli -L
>
> Found 1 modems:
> /org/freedesktop/ModemManager1/Modem/2 [huawei] E3372
>
> #
>
> From "experience" I now know it is at index 2. Don't expect users are that 
> smart when doing first steps. ;-)
>

The index isn't fixed. The index just happens to be the number of
modems detected since the startup of ModemManager; if you unplug and
replug the modem the index will change. If you want to have a "name"
for a modem that doesn't change e.g. across reboots, you can tag the
USB port where the modem is available with a label that may be used
later on instead of the modem index; e.g. "mmcli -m USB1" or so. See:
https://sigquit.wordpress.com/2016/10/06/naming-devices-in-modemmanager/

>>
>>>
>>>
>>> # mmcli  --set-power-state-on -m /org/freedesktop/ModemManager1/Modem/0
>>> error: couldn't set new power state in the modem: 
>>> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.WrongState: Cannot 
>>> set power state: not in disabled state'
>>
>> Your modem is already registered, so it is already in "on" power state.
>
> If one doesn't know what are all the options, it is hard to find what needs 
> to be done in what order. The help text could say how the power-related 
> options relate to "--enable", "--disable". For example, "not applicable when 
> connected/enabled/whatever".
>

Help text in --help doesn't allow too many explanations. Such things
should be included in either the mmcli manpage or directly in the
ModemManager gtk-doc documentation published in the website.

>>
>>>
>>> The mmcli --help-all are too cryptic to me. I failed to find a way to 
>>> really get the device connected. There should be some typical examples at 
>>> the end of --help-all output. Even figuring out I need to specify "-m 
>>>

Re: ModemManager-1.6.2: does not work with Huawei E3372h ??? -153

2017-01-13 Thread Aleksander Morgado 
Hey,

>>
>> I am a little bit surprised that the modem uses the ppp-interface in your
>> case. When I read your logfiles right, then you have a device which is sold
>> under the name "Speedsick LTE V" in Germany.
>
> How do you achieve non-PPP option in nm-applet? Whenever I select "Mobile 
> broadband" there are these option driver-based and PPP-based fields. Should I 
> use "Ethernet" instead?
>

This is transparent to the user; the user doesn't know whether the
connection will be through PPP or a WWAN network interface. The
PPP-based fields are always there, but they won't apply if the
connection goes through a WWAN network interface. This is not ideal,
but right now there's no way for NM to know the type of interface that
will be used for the connection later on; only when it has been
already established.

>>
>> This device should use the wwan-device by huawei_cdc_ncm.
>
> I am glad to hear that as well, but can you tell me if ModemManager realizes 
> that wwan0 was renamed by OpenRC to wwp0s29u1u2i2 ? Does that interfere 
> anyhow?
>

That won't interfere no, as long as the network interface renaming
rules are run before MM's own udev rules.

> Can you tell if ModemManager should run "usb_modeswitch -J -v 0x12d1 -p 
> 0x14fe" automagically (I have v.2.4.0 of usb_modeswitch")?
>

ModemManager doesn't run any usb_modeswitch command itself.
usb_modeswitch is usually run way before the MM rules are applied.

>>
>> I know three different kinds of this device
>>
>> E3372 hilink-mode (cdc_ether) direct from huawei
>> E3372 - Telekom - huawei_cdc_ncm
>> K5160 - Vodafone -mbim/cdc_ether
>>
>> In no case a fallback to ppp should be needed.
>
> That is what I also thought, especially because Alexander asked me in the 
> beginning of the thread if I have the CDC_NCM or CDC_NCM_HUAWEI enabled.
>

Does the list of ports in the "mmcli -m [N]" output show any "cdc-wdm" port?

> I have compiled:
>
> # grep CONFIG_USB_NET_ /usr/src/linux-4.9.2/.config
> CONFIG_USB_NET_DRIVERS=y
> # CONFIG_USB_NET_AX8817X is not set
> # CONFIG_USB_NET_AX88179_178A is not set
> CONFIG_USB_NET_CDCETHER=m
> # CONFIG_USB_NET_CDC_EEM is not set
> CONFIG_USB_NET_CDC_NCM=y
> CONFIG_USB_NET_HUAWEI_CDC_NCM=y
> CONFIG_USB_NET_CDC_MBIM=y
> # CONFIG_USB_NET_DM9601 is not set
> # CONFIG_USB_NET_SR9700 is not set
> # CONFIG_USB_NET_SR9800 is not set
> # CONFIG_USB_NET_SMSC75XX is not set
> # CONFIG_USB_NET_SMSC95XX is not set
> # CONFIG_USB_NET_GL620A is not set
> CONFIG_USB_NET_NET1080=m
> CONFIG_USB_NET_PLUSB=m
> # CONFIG_USB_NET_MCS7830 is not set
> CONFIG_USB_NET_RNDIS_HOST=m
> CONFIG_USB_NET_CDC_SUBSET=m
> # CONFIG_USB_NET_ZAURUS is not set
> # CONFIG_USB_NET_CX82310_ETH is not set
> # CONFIG_USB_NET_KALMIA is not set
> CONFIG_USB_NET_QMI_WWAN=m
> # CONFIG_USB_NET_INT51X1 is not set
> # CONFIG_USB_NET_CH9200 is not set
> # CONFIG_USB_NET_RNDIS_WLAN is not set
>

Ok, huawei-cdc-ncm is enabled.

But how about the cdc-wdm driver (CONFIG_USB_WDM)?

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

Re: ModemManager-1.6.2: does not work with Huawei E3372h-153

2017-01-12 Thread Martin MOKREJŠ 
I forgot to add what I see in Connection information from nm-applet:

Interface: GSM (ttyUSB0)
Driver: huawei_cdc_ncm, option1

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

Re: ModemManager-1.6.2: does not work with Huawei E3372h-153

2017-01-12 Thread Martin MOKREJŠ 
Hi Alexander,
  thank you for you help.

  I propose improving mmcli manpage. The EXAMPLES section should start with:
1. how shall one figure out where is any modem seen
2. how to read the status, shown "registered" and later "connected" states.
3. although it seems it is not relevant to mmcli, a hint where to go next to 
get use of the "connected" modem would be very helpful.


Aleksander Morgado wrote:
> On Thu, Jan 12, 2017 at 3:49 PM, Martin MOKREJŠ  wrote:
>> # mmcli  --connect -m /org/freedesktop/ModemManager1/Modem/0
>> error: no bearer was specified
> 
> --connect is a bearer action, you need to pass a bearer object path,
> not a modem object path.

I think "mmcli --help" could show some hints in the bearer section, like 
--create-bearer="apn=internet.t-mobile.xx"

> 
>> # mmcli  --list-bearers -m /org/freedesktop/ModemManager1/Modem/0
>>
>> No bearers were found
> 
> Ok, so you would first need to create a bearer with
> --create-bearer="key=value,..." in one of the modems.
> 
> E.g.
> 
> mmcli -m 0 --create-bearer="apn=internet"

Yeah, but I again had to rescan my devices and only then I was able to use a 
modem. And it appeared at different index pos. Again, the EXAMPLES section 
could be improved so that a user can use it as a real step-by-step manual to 
get connected (to have a network device with an IP!).

> 
> See:
> https://www.freedesktop.org/software/ModemManager/api/latest/gdbus-org.freedesktop.ModemManager1.Modem.html#gdbus-method-org-freedesktop-ModemManager1-Modem.CreateBearer
> 
>> # mmcli  --bearer -m /org/freedesktop/ModemManager1/Modem/0
>> error: invalid path or index string specified: '-m'
> 
> --bearer expects a bearer path or index (help says "--bearer=[PATH|INDEX]")
> 
>> # mmcli  --bearer
>> error: no actions specified
> 
> Same thing, --bearer expects a bearer path or index (help says
> "--bearer=[PATH|INDEX]")
> 
>> # mmcli  -b
>> error: no actions specified
> 
> Same thing, --bearer expects a bearer path or index (help says
> "--bearer=[PATH|INDEX]")
> 
>> # mmcli  -b -m /org/freedesktop/ModemManager1/Modem/0
>> error: invalid path or index string specified: '-m'
> 
> Same thing, --bearer expects a bearer path or index (help says
> "--bearer=[PATH|INDEX]")


How about mmcli being more friendly and output after the error message a list 
of my modems?

# mmcli -L

Found 1 modems:
/org/freedesktop/ModemManager1/Modem/2 [huawei] E3372

#

>From "experience" I now know it is at index 2. Don't expect users are that 
>smart when doing first steps. ;-)

> 
>>
>>
>> # mmcli  --set-power-state-on -m /org/freedesktop/ModemManager1/Modem/0
>> error: couldn't set new power state in the modem: 
>> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.WrongState: Cannot set 
>> power state: not in disabled state'
> 
> Your modem is already registered, so it is already in "on" power state.

If one doesn't know what are all the options, it is hard to find what needs to 
be done in what order. The help text could say how the power-related options 
relate to "--enable", "--disable". For example, "not applicable when 
connected/enabled/whatever".

> 
>>
>> The mmcli --help-all are too cryptic to me. I failed to find a way to really 
>> get the device connected. There should be some typical examples at the end 
>> of --help-all output. Even figuring out I need to specify "-m 
>> /org/freedesktop/ModemManager1/Modem/0" took me a long while. Why sometimes 
>> it is rejected as a wrong argument I do not know (shown above).
> 
> For launching a connection you can use the "manual" way of creating
> the bearer object and then --connect; OR, easier, just
> "--simple-connect" in the modem object. E.g.:
> 
> mmcli -m 0 --simple-connect="apn=internet"

And the "simple" seemed like a provisional solution, probably only a partial 
"something". So what is "full" connect then?

> 
> See 
> https://www.freedesktop.org/software/ModemManager/api/latest/gdbus-org.freedesktop.ModemManager1.Modem.Simple.html#gdbus-method-org-freedesktop-ModemManager1-Modem-Simple.Connect

So I had:
# mmcli  --simple-status -m 2

/org/freedesktop/ModemManager1/Modem/2
  -
  Status |  state: 'connected'
 | signal quality: '38' (recent)
 |  bands: 'unknown'
 |access tech: 'lte'
  -
  3GPP   |   registration: 'home'
 |  operator code: '23001'
 |  operator name: 'T-Mobile CZ'
 |   subscription: 'unknown'

#

# nmcli connection show
NAME   UUID  TYPE
DEVICE
tun0   14534bb3-8213-4a8f-b545-b1ce85475a73  tun  tun0
tun1   fd0515be-3f98-4d09-95e3-3fc132370578  tun  tun1
HuaweiE3131a6f9b700-5930-4dd9-a0aa-a808acb67c2c  gsm  --
HuaweiE3372h-153   7834078b-e76e-4825-b987-b460eed422ea  gsm  --
VPN connection 1   7db7b1fa-7aac-43b5-bbe7-dc3eebd84dc7  vpn  --
eduroam

Re: ModemManager-1.6.2: does not work with Huawei E3372h-153

2017-01-12 Thread Aleksander Morgado 
On Thu, Jan 12, 2017 at 3:49 PM, Martin MOKREJŠ  wrote:
> # mmcli  --connect -m /org/freedesktop/ModemManager1/Modem/0
> error: no bearer was specified

--connect is a bearer action, you need to pass a bearer object path,
not a modem object path.

> # mmcli  --list-bearers -m /org/freedesktop/ModemManager1/Modem/0
>
> No bearers were found

Ok, so you would first need to create a bearer with
--create-bearer="key=value,..." in one of the modems.

E.g.

mmcli -m 0 --create-bearer="apn=internet"

See:
https://www.freedesktop.org/software/ModemManager/api/latest/gdbus-org.freedesktop.ModemManager1.Modem.html#gdbus-method-org-freedesktop-ModemManager1-Modem.CreateBearer

> # mmcli  --bearer -m /org/freedesktop/ModemManager1/Modem/0
> error: invalid path or index string specified: '-m'

--bearer expects a bearer path or index (help says "--bearer=[PATH|INDEX]")

> # mmcli  --bearer
> error: no actions specified

Same thing, --bearer expects a bearer path or index (help says
"--bearer=[PATH|INDEX]")

> # mmcli  -b
> error: no actions specified

Same thing, --bearer expects a bearer path or index (help says
"--bearer=[PATH|INDEX]")

> # mmcli  -b -m /org/freedesktop/ModemManager1/Modem/0
> error: invalid path or index string specified: '-m'

Same thing, --bearer expects a bearer path or index (help says
"--bearer=[PATH|INDEX]")

>
>
> # mmcli  --set-power-state-on -m /org/freedesktop/ModemManager1/Modem/0
> error: couldn't set new power state in the modem: 
> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.WrongState: Cannot set 
> power state: not in disabled state'

Your modem is already registered, so it is already in "on" power state.

>
> The mmcli --help-all are too cryptic to me. I failed to find a way to really 
> get the device connected. There should be some typical examples at the end of 
> --help-all output. Even figuring out I need to specify "-m 
> /org/freedesktop/ModemManager1/Modem/0" took me a long while. Why sometimes 
> it is rejected as a wrong argument I do not know (shown above).

For launching a connection you can use the "manual" way of creating
the bearer object and then --connect; OR, easier, just
"--simple-connect" in the modem object. E.g.:

mmcli -m 0 --simple-connect="apn=internet"

See 
https://www.freedesktop.org/software/ModemManager/api/latest/gdbus-org.freedesktop.ModemManager1.Modem.Simple.html#gdbus-method-org-freedesktop-ModemManager1-Modem-Simple.Connect

Cheers!

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