qmi-network disconnected after 120sec if not receiving a DHCP Request?

[Benoît]

Thanks for the link.
I confirm I got the same problem no my Dell MC8805..
Too bad that we still need DHCP to make it work as btw your latest 
version of qmi-network/qmicli are very great (specifically with the FCC 
and 802-3 automatic test at the beginning where I needed to do it on my 
script now I erase theses lines :) plus the --wds-get-current-settings 
option.
The reason why I don't want to use DHCP is because my system has 
multiple NICs and I don't want it to mess with default gw added by DHCP..
many thanks

On 11/10/15 07:45, Aleksander Morgado wrote:
> On Tue, Nov 10, 2015 at 12:07 AM, Benoît <benoitne at gmail.com> wrote:
>> I think I remember seeing that it is a normal behavior that qmi-network will
>> be disconnected if no dhcp request is made before 120sec.
>> I have tried to manually add the IP thanks to the information provided by
>> the new option in Master branch ( --wds-get-current-settings) but it is not
>> like to work.
>>
>> So I am just wondering if there is a particular behavior where the data pane
>> is going to only be available if dhcp request / response are previously
>> made?
>> Then it would explain why in my configuration without DHCP and with manual
>> IP configuration it doesn't work.
> Yes, we've seen that already in some Huawei devices at least. This
> lengthy discussion in the ModemManager mailing list as an example:
> http://lists.freedesktop.org/archives/modemmanager-devel/2014-August/001423.html
>
> Basically, some modems require the DHCP step even if they expose the
> IP settings via QMI, which is why we're defaulting to DHCP always for
> QMI modems in ModemManager.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20151110/33f66721/attachment.html>