libqmi-glib

[Aleksander Morgado]

Hey hey,

> 
>> Anyway, today I noticed more features added.  Unfortunately one of them
>> is not going to work: You allow the client to exit after starting a
>> connection, releasing the WDS client ID.  That's not supported.  You
>> have to keep the client ID while the connection is up. Once the client
>> ID is released, the connection goes down.
> 
> And then I noticed the --client-no-release-cid option.  I'm more than a
> bit slow.
> 

Yes, that's the option to avoid releasing the CID when qmicli exits;
then you can use --client-cid=X to recover it the next time you call qmicli.

> That will make it work. Probably best to bundle it with --wds-start-network, 
> but then again I guess this is a test utility for people supposed to
> know what they're doing.
> 

If you run --wds-start-network WITH --wds-follow-network; the program
will keep running with the connection open until you do Ctrl+C. In that
way, you don't need to play with --client-no-release-cid, --client-cid
and --wds-stop-network, as that is done for you automatically.

If you still want the qmicli to exit, while keeping the CID unreleased
and all that, try to use the new `qmi-network' script, where you can just:
  $> qmi-network /dev/cdc-wdm0 start
  $> qmi-network /dev/cdc-wdm0 status
  $> qmi-network /dev/cdc-wdm0 stop

That  will keep the packet data handle and CID in a state file under
/tmp; quite similar to what you did in your script. Note that that
script is still quite untested, I wrote it last Friday.

One last thing; if you ever get the 'exhausted client IDs' error, you
can just run qmicli with --device-open-sync, which will run the SYNC
request as a step while opening the QmiDevice.

Cheers!

-- 
Aleksander