Not getting IP Address after wds-start-network

[Markus Gothe]

You could as well use my derivate driver for raw IP only as well...

However switch the WDA format is to prefer, but recent Netgear stuff with Sprint branding have issues with the switch. Namely 341U and 770S.

//M
Den 7 aug 2015 1:12 fm skrev Kavula Suresh <kavulas at gmail.com>:
>
> Thanks! With patch script update, it's working fine as expected. 
>
> Thanks once again. 
>
> Regards,
>
> On Thu, Aug 6, 2015 at 4:45 PM, Aleksander Morgado <aleksander at aleksander.es> wrote:
>>
>> Hey,
>>
>> On Thu, Aug 6, 2015 at 10:50 PM, Kavula Suresh <kavulas at gmail.com> wrote:
>> > I have a problem with the Sierra MC7354 Modem and libqmi drivers. I can
>> > establish connection with qmicli commands. After connecting network, I don’t
>> > get ip from service provider (with dhclient wwan0) and disconnects network
>> > after 1 or 2 minutes. Here is the command summary used:
>> >
>> > # qmicli -d /dev/cdc-wdm0 --wds-start-network=VZWINTERNET
>> > --client-no-release-cid --wds-follow-network
>> > [/dev/cdc-wdm0] Network started
>> >         Packet data handle: '1137907944'
>> >
>> > Ctrl+C will stop the network
>> > [/dev/cdc-wdm0] Connection status: 'connected'
>> > [/dev/cdc-wdm0] Connection status: 'connected'
>> > [/dev/cdc-wdm0] Connection status: 'connected'
>> > [/dev/cdc-wdm0] Connection status: 'connected'
>> > [/dev/cdc-wdm0] Connection status: 'connected'
>> > [/dev/cdc-wdm0] Connection status: 'connected'
>> > [/dev/cdc-wdm0] Connection status: 'disconnected'
>> > [/dev/cdc-wdm0] Stopping after detecting disconnection
>> > Network cancelled... releasing resources
>> > error: couldn't stop network: QMI protocol error (26): 'NoEffect'
>> > [/dev/cdc-wdm0] Client ID not released:
>> >         Service: 'wds'
>> >             CID: '9'
>> >
>> >
>> >
>> > After issuing command:
>> >
>> > ifconfig -a
>> >
>> > wwan0     Link encap:Ethernet  HWaddr 3A:65:0F:F1:01:E3
>> >           inet6 addr: fe80::3865:fff:fef1:1e3/64 Scope:Link
>> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> >           TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
>> >           collisions:0 txqueuelen:1000
>> >           RX bytes:0 (0.0 B)  TX bytes:32124 (31.3 KiB)
>> >
>> > and
>> >
>> >     # dhclient -d -4 wwan0
>> > Internet Systems Consortium DHCP Client 4.1-ESV-R8
>> > Copyright 2004-2013 Internet Systems Consortium.
>> > All rights reserved.
>> > For info, please visit https://www.isc.org/software/dhcp/
>> >
>> > Listening on LPF/wwan0/3a:65:0f:f1:01:e3
>> > Sending on   LPF/wwan0/3a:65:0f:f1:01:e3
>> > Sending on   Socket/fallback
>> > DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 3
>> > DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 5
>> > DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 7
>> > DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 8
>> > DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 13
>> > DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 8
>> > DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 14
>> > DHCPDISCOVER on wwan0 to 255.255.255.255 port 67 interval 3
>> > No DHCPOFFERS received.
>> > No working leases in persistent database - sleeping.
>> >
>> > Any suggestions would be help to make wwan0 broadband connection in forever
>> > mode.
>> >
>>
>> Assuming you're not using libqmi git master, go apply this patch here
>> and retry ,please:
>>
>> http://cgit.freedesktop.org/libqmi/commit/?id=4a82bb9be84861e5098d1c1482b16f60b2b3e449
>>
>> The MC7354 shows up with 2 pairs of QMI+WWAN pairs; one of them is by
>> default set to raw-ip; the other one is set to 802.3.The kernel driver
>> expects it to be 802.3, so you'll need to either choose the QMI+WWAN
>> pair which is already in 802.3, or otherwise, unconditionally switch
>> to 802.3 before connecting (with that patch).
>>
>> Without more info that's what I would suggest to do for now.
>>
>> --
>> Aleksander
>> https://aleksander.es
>
>