Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: connmand[186]: Online check failed but running dhclient
manually fixes this issue (Sean Nyekj?r)
2. Re: connmand[186]: Online check failed but running dhclient
manually fixes this issue (Jonas Bonn)
----------------------------------------------------------------------
Message: 1
Date: Mon, 11 Dec 2017 07:37:35 +0100
From: Sean Nyekj?r <[email protected]>
To: Denis Kenzior <[email protected]>
Cc: Daniel Wagner <[email protected]>, "[email protected]"
<[email protected]>, Alexander Couzens <[email protected]>,
[email protected], [email protected]
Subject: Re: connmand[186]: Online check failed but running dhclient
manually fixes this issue
Message-ID:
<CAKv0xJwRtHoYUV-APSy=0cW1xVJRa64G3huH=tbbduwexqu...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi
Sorry if i'm reposting.
I'm also having this issue with the Quectel EC20 (and maybe EC21).
Any known fixes or workarounds i could try? Is the problem in connman or ofono?
/Sean
On 6 September 2017 at 17:40, Denis Kenzior <[email protected]> wrote:
> Hi Daniel,
>>>
>>>
>>> If this is true, then falling back to DHCP would seem to be required
>>> for many Qualcomm based devices. This seems to be a recently
>>> introduced 'bug' as older QMI devices did not need this workaround.
>>
>>
>> Do you think we should try to figure out which Qualcomm device is
>> misbehaving or should the feature just be reverted?
>
>
> It would seem that this only affects devices introduced in the last several
> years. The QMI code is from 2012, and the devices Marcel tested this with
> worked fine.
>
> Perhaps we should have plugins/udevng.c maintain a database of all the
> 'dhcp-required' devices and set this property accordingly. Running DHCP
> takes time, so if it can be avoided, you get online a bit faster...
>
>>
>> The other option is to add some fallback mechanism in ConnMan and print
>> a fat warning into the log. But I don't this idea.
>>
>
> Sounds like a least preferred option to me as well.
>
> Regards,
> -Denis
>
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
------------------------------
Message: 2
Date: Mon, 11 Dec 2017 07:51:50 +0100
From: Jonas Bonn <[email protected]>
To: Sean Nyekj?r <[email protected]>, Denis Kenzior <[email protected]>
Cc: "[email protected]" <[email protected]>, Alexander Couzens
<[email protected]>, Daniel Wagner <[email protected]>, [email protected],
[email protected]
Subject: Re: connmand[186]: Online check failed but running dhclient
manually fixes this issue
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 12/11/2017 07:37 AM, Sean Nyekj?r wrote:
> Hi
> Sorry if i'm reposting.
>
> I'm also having this issue with the Quectel EC20 (and maybe EC21).
The EC21 is "raw ip" only so shouldn't be affected by this.? I've got
one and I've never seen this issue in any case.
/Jonas
>
> Any known fixes or workarounds i could try? Is the problem in connman or
> ofono?
>
> /Sean
>
> On 6 September 2017 at 17:40, Denis Kenzior <[email protected]> wrote:
>> Hi Daniel,
>>>>
>>>> If this is true, then falling back to DHCP would seem to be required
>>>> for many Qualcomm based devices. This seems to be a recently
>>>> introduced 'bug' as older QMI devices did not need this workaround.
>>>
>>> Do you think we should try to figure out which Qualcomm device is
>>> misbehaving or should the feature just be reverted?
>>
>> It would seem that this only affects devices introduced in the last several
>> years. The QMI code is from 2012, and the devices Marcel tested this with
>> worked fine.
>>
>> Perhaps we should have plugins/udevng.c maintain a database of all the
>> 'dhcp-required' devices and set this property accordingly. Running DHCP
>> takes time, so if it can be avoided, you get online a bit faster...
>>
>>> The other option is to add some fallback mechanism in ConnMan and print
>>> a fat warning into the log. But I don't this idea.
>>>
>> Sounds like a least preferred option to me as well.
>>
>> Regards,
>> -Denis
>>
>> _______________________________________________
>> connman mailing list
>> [email protected]
>> https://lists.01.org/mailman/listinfo/connman
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 26, Issue 11
***************************************
