mmcli connectin with IPv4 works, question about keys

Aleksander Morgado aleksander at lanedo.com
Tue Aug 28 05:54:43 PDT 2012


>>
>>> Is there a possibility to force 3g-mode?
>>>
>>
>> It should be doable passing:
>>      "allowed-mode=3g"
> 
> Here comes an error:
> Error parsing connect string: "Invalid properties string, unexpected key
> "allowed-mode"
> 

That should have been "allowed-modes", not "allowed-mode"; my bad.

> 
> 
>>
>> 'allowed-modes' is also a list, so you can also pass:
>>      "allowed-modes='2g,3g,4g'"
>>
> 
> This does almost work, but only with one value.
> 

Another error in my side, it should have been:
  "allowed-modes=2g|3g|4g"

> 
> The switch between 2G and 4G works, but only at the second try.
> 
> hpmini:~ # mmcli --timeout=500 -m 0
> --simple-connect="apn=internet.telekom,allowed-modes='4g',ip-type=ipv4"
> --verbose
> [28 Aug 2012, 14:27:15] [Debug] Forcing request to be run asynchronously
> [28 Aug 2012, 14:27:15] [Debug] Assuming '0' is the modem index
> [28 Aug 2012, 14:27:15] [Debug] ModemManager process found at ':1.30'
> [28 Aug 2012, 14:27:15] [Debug] Modem found at
> '/org/freedesktop/ModemManager1/Modem/0'
> 
> [28 Aug 2012, 14:27:15] [Debug] Asynchronously connecting the modem...
> error: couldn't connect the modem:
> 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.CallFailed: QMI
> protocol error (14): 'CallFailed''
> hpmini:~ # mmcli --timeout=500 -m 0
> --simple-connect="apn=internet.telekom,allowed-modes='4g',ip-type=ipv4"
> --verbose
> [28 Aug 2012, 14:27:24] [Debug] Forcing request to be run asynchronously
> [28 Aug 2012, 14:27:24] [Debug] Assuming '0' is the modem index
> [28 Aug 2012, 14:27:24] [Debug] ModemManager process found at ':1.30'
> [28 Aug 2012, 14:27:24] [Debug] Modem found at
> '/org/freedesktop/ModemManager1/Modem/0'
> 
> [28 Aug 2012, 14:27:24] [Debug] Asynchronously connecting the modem...
> successfully connected the modem
> hpmini:~ #
> 
> 
> 
> The first try switches to the wanted mode.
> The second try makes the connection.
> 

Will take a look at that. We probably need to get confirmation that the
mode changed before going on to the next connection steps.


-- 
Aleksander


More information about the libqmi-devel mailing list