modemmanager compile problem

[Aleksander Morgado]

>>
>>> Oops; strange that I didn't get that. Different gcc versions I guess.
>>> Should be fixed now.
>>
>> Yup, just successfully tested "mmcli --simple-connect", and it worked
>> fine.
>>
>> One note though:  I see that you set TLV 0x19 in the "Start Network"
>> message: 
>>
>>
>> ModemManager[15003]: [/dev/cdc-wdm0] Sending message...
>> <<<<<< QMUX:
>> <<<<<<   length  = 26
>> <<<<<<   flags   = 0x00
>> <<<<<<   service = "wds"
>> <<<<<<   client  = 3
>> <<<<<< QMI:
>> <<<<<<   flags       = "none"
>> <<<<<<   transaction = 3
>> <<<<<<   tlv_length  = 14
>> <<<<<<   message     = "Start Network" (0x0020)
>> <<<<<< TLV:
>> <<<<<<   type       = "IP Family Preference" (0x19)
>> <<<<<<   length     = 1
>> <<<<<<   value      = 04
>> <<<<<<   translated = 4
>> <<<<<< TLV:
>> <<<<<<   type       = "APN" (0x14)
>> <<<<<<   length     = 7
>> <<<<<<   value      = 74:65:6C:65:6E:6F:72
>> <<<<<<   translated = telenor
>> ModemManager[15003]: KEY: 03:00:03:01:00:00:00:00
>> ModemManager[15003]:   Service: 01
>> ModemManager[15003]:   Client ID: 03
>> ModemManager[15003]:   Transaction ID: 03:00
>>
>>
>>
>> We've had mixed results with that earlier.  It seems that the preferred
>> method (as snooped by Dan in Windows with the Pantech UML290, and
>> verified to work in Linux) is to leave TLV 0x19 unset, and instead set a
>> new default family prior to each connect.  This is the only way we've
>> been able to establish dual stack connections.  Using TLV 0x19 did not
>> work.  Might be a firmware bug, but we need to handle it anyway I
>> believe...
>>
>> And dual stack connections complicates things somewhat more, as you have
>> to do at least 4 successful QMI requests to get a single dual stack
>> session connected:
>>
>>  1) WDS "Set the client IP family preference" (0x004D): IPv6
>>  2) WDS "Start Network": dual stack APN
>>  3) WDS "Set the client IP family preference" (0x004D): IPv4
>>  4) WDS "Start Network": dual stack APN
> 
> I forgot an important issue here:  You won't be able to do this using
> the same WDS client ID.  You need to allocate one for IPv4 and one for
> IPv6, complicating the dual stack case even more.
> 


Gah... that's bad. I'll need to change a bit MMPortQmi to handle that.
Thanks for the hint.

-- 
Aleksander