dhclient failed on MC7354
dailijin
dailijin126 at 126.com
Thu Apr 6 09:52:12 UTC 2017
Hi Alekander,
I also encountered this issue when use MC7304 modem, the reason is same with what you mentioned. when execute command "tvu-qmicli -d /dev/cdc-wdm3 --wda-set-data-format=802-3" always fail, so always get IP via dhclient fail.
If I reset the modem by manual, the modem maybe can work normally.
Below is the log when set data format fail. how do I directly solve this issue without reset modem? my libqmi version is 1.10.2
tvupack TVUTransporter # tvu-qmicli -d /dev/cdc-wdm3 --wda-set-data-format=802-3 -v
error: couldn't create client for the 'wda' service: QMI protocol error (3): 'Internal'
[06 Apr 2017, 09:38:09] [Debug] [/dev/cdc-wdm3] Opening device with flags 'none'...
[06 Apr 2017, 09:38:09] [Debug] QMI Device at '/dev/cdc-wdm3' ready
[06 Apr 2017, 09:38:09] [Debug] [/dev/cdc-wdm3] Assuming service 'wda' is supported...
[06 Apr 2017, 09:38:09] [Debug] [/dev/cdc-wdm3] Allocating new client ID...
[06 Apr 2017, 09:38:09] [Debug] [/dev/cdc-wdm3] Sent message...
<<<<<< RAW:
<<<<<< length = 16
<<<<<< data = 01:0F:00:00:00:00:00:01:22:00:04:00:01:01:00:1A
[06 Apr 2017, 09:38:09] [Debug] [/dev/cdc-wdm3] Sent message (translated)...
<<<<<< QMUX:
<<<<<< length = 15
<<<<<< flags = 0x00
<<<<<< service = "ctl"
<<<<<< client = 0
<<<<<< QMI:
<<<<<< flags = "none"
<<<<<< transaction = 1
<<<<<< tlv_length = 4
<<<<<< message = "Allocate CID" (0x0022)
<<<<<< TLV:
<<<<<< type = "Service" (0x01)
<<<<<< length = 1
<<<<<< value = 1A
<<<<<< translated = wda
[06 Apr 2017, 09:38:09] [Debug] [/dev/cdc-wdm3] Received message...
>>>>>> RAW:
>>>>>> length = 19
>>>>>> data = 01:12:00:80:00:00:01:01:22:00:07:00:02:04:00:01:00:03:00
[06 Apr 2017, 09:38:09] [Debug] [/dev/cdc-wdm3] Received message (translated)...
>>>>>> QMUX:
>>>>>> length = 18
>>>>>> flags = 0x80
>>>>>> service = "ctl"
>>>>>> client = 0
>>>>>> QMI:
>>>>>> flags = "response"
>>>>>> transaction = 1
>>>>>> tlv_length = 7
>>>>>> message = "Allocate CID" (0x0022)
>>>>>> TLV:
>>>>>> type = "Result" (0x02)
>>>>>> length = 4
>>>>>> value = 01:00:03:00
--
Best Regards,
Dai,Lijin
At 2017-02-08 16:31:25, "Aleksander Morgado" <aleksander at aleksander.es> wrote:
>On Wed, Feb 8, 2017 at 3:26 AM, Chen, Jing <Jing.Chen at spirent.com> wrote:
>> After wds-start-network succeeded, there is no response to DHCPDISCOVER
>> message. I am using Ubuntu 16.04 (Linux kernel 4.8). Do I miss any package?
>> Any suggestion? Thanks!
>>
>>
>>
>> root at osU1404:/dev#
>>
>> root at osU1404:/dev#
>>
>> root at osU1404:/dev# qmicli -d /dev/cdc-wdm0 --wds-start-network=nxtgenphone
>> --client-no-release-cid
>>
>> [/dev/cdc-wdm0] Network started
>>
>> Packet data handle: '1137832088'
>>
>> [/dev/cdc-wdm0] Client ID not released:
>>
>> Service: 'wds'
>>
>> CID: '9'
>>
>> root at osU1404:/dev# ifconfig wwan0 up
>>
>> root at osU1404:/dev# dhclient -v -4 wwan0
>>
>> Internet Systems Consortium DHCP Client 4.2.4
>>
>> Copyright 2004-2012 Internet Systems Consortium.
>>
>> All rights reserved.
>>
>> For info, please visit https://www.isc.org/software/dhcp/
>>
>>
>>
>> Listening on LPF/wwan0/3a:c9:95:91:8f:c7
>>
>> Sending on LPF/wwan0/3a:c9:95:91:8f:c7
>>
>> Sending on Socket/fallback
>>
>> DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 3 (xid=0x4060cae4)
>>
>> DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 8 (xid=0x4060cae4)
>>
>> ^C
>>
>> root at osU1404:/dev#
>
>Is the LLP for the wwan set as 802.3?
>
>i.e. did you explicity run:
>$ qmicli -d /dev/cdc-wdm0 --wda-set-data-format="802-3"
>
>You can check that with:
>$ qmicli -d /dev/cdc-wdm0 --wda-get-data-format
>
>If the interface is not in 802.3 mode, dhclient doesn't know yet how
>to manage the raw-ip network interface.
>
>--
>Aleksander
>https://aleksander.es
>_______________________________________________
>libqmi-devel mailing list
>libqmi-devel at lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/libqmi-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20170406/c3bad222/attachment.html>
More information about the libqmi-devel
mailing list