Problems with HP lt4112 Gobi 4G Module

[Harald Jung]

^DHCP:5316546d,f8ffffff,5116546d,5116546d,7e1e078b,7d1e078b,43200000,43200000


Am 18.02.2016 um 19:58 schrieb Dan Williams:
> On Thu, 2016-02-18 at 19:43 +0100, Harald Jung wrote:
>> Hi,
>>
>> the strange thing is I'm still able to obtain stuff by an dhcp
>> request,
>> so it is not "really" disconnected.
>>
>> qmicli -d /dev/cdc-wdm0 --wds-start-network=web.vodafone.de
>> --client-no-release-cid
>> [/dev/cdc-wdm0] Network started
>>           Packet data handle: '1138179280'
>> [/dev/cdc-wdm0] Client ID not released:
>>           Service: 'wds'
>>               CID: '5'
>> ThinClient,initial:root:~ $ qmicli -d /dev/cdc-wdm0
>> --wds-get-current-settings --client-no-release-cid --client-cid=5
>> error: couldn't get current settings: QMI protocol error (15):
>> 'OutOfCall'
>> [/dev/cdc-wdm0] Client ID not released:
>>           Service: 'wds'
>>               CID: '5'
>> ThinClient,initial:root:~ $ /usr/sbin/dhcpcd -B -K -L -A -G -c
>> /usr/libexec/nm-dhcp-helper -4 wwan0
>> wwan0: rebinding lease of 109.84.22.83
>> wwan0: leased 109.84.22.83 for 7200 seconds
>> wwan0: adding route to 109.84.22.80/29
> My original thought after reading your logs was that the device was
> just stupid and that it might work with DHCP.  I got side-tracked
> trying to bring up my ME906E (which your lt4112 is an OEM version of,
> though yours runs QMI and the stock ME906E does NDISDUP).
>
> But given that the device clearly still has NDISDUP commands lying
> around in its firmware, perhaps the lt4112 only likes DHCP?  I'd love
> to see the "AT^DHCP?" output from that device once it's connected, can
> you get that?  Even if you send it to the modem, it might get read by
> ModemManager and appear in the MM logs, FYI.
>
> Dan
>
>
>> Harald
>>
>> Am 18.02.2016 um 19:36 schrieb Bjørn Mork:
>>> Harald Jung <harald.jung at ecos.de> writes:
>>>
>>>> [18 Feb 2016, 19:35:12] [Debug] [/dev/cdc-wdm0] Received message
>>>> (translated)...
>>>>>>>>>> QMUX:
>>>>>>>>>>     length  = 33
>>>>>>>>>>     flags   = 0x80
>>>>>>>>>>     service = "wds"
>>>>>>>>>>     client  = 255
>>>>>>>>>> QMI:
>>>>>>>>>>     flags       = "indication"
>>>>>>>>>>     transaction = 0
>>>>>>>>>>     tlv_length  = 21
>>>>>>>>>>     message     = "Packet Service Status" (0x0022)
>>>>>>>>>> TLV:
>>>>>>>>>>     type       = "Connection Status" (0x01)
>>>>>>>>>>     length     = 2
>>>>>>>>>>     value      = 01:00
>>>>>>>>>>     translated = [ status = 'disconnected'
>>>> reconfiguration_required = 'no' ]
>>>>>>>>>> TLV:
>>>>>>>>>>     type       = "Call End Reason" (0x10)
>>>>>>>>>>     length     = 2
>>>>>>>>>>     value      = 02:00
>>>>>>>>>>     translated = generic-client-end
>>>>>>>>>> TLV:
>>>>>>>>>>     type       = "Verbose Call End Reason" (0x11)
>>>>>>>>>>     length     = 4
>>>>>>>>>>     value      = 03:00:D0:07
>>>>>>>>>>     translated = [ type = 'cm' reason = '2000' ]
>>>>>>>>>> TLV:
>>>>>>>>>>     type       = "IP Family" (0x12)
>>>>>>>>>>     length     = 1
>>>>>>>>>>     value      = 04
>>>>>>>>>>     translated = ipv4
>>> OK, this is interesting although I have no idea why it
>>> happens.  But you
>>> are disconnected for reason '2000', whatever that is.
>>>
>>>
>>> Bjørn
>> _______________________________________________
>> libqmi-devel mailing list
>> libqmi-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/libqmi-devel