Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe 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: [PATCH] pptp: Cancel queued VPN agent msg when disconnected
(Jussi Laakkonen)
2. Re: [PATCH] pptp: Cancel queued VPN agent msg when disconnected
(Daniel Wagner)
3. Re: problem changing wired connection from dhcp -> manual
([email protected])
4. Re: problem changing wired connection from dhcp -> manual
([email protected])
5. Re: Insights on connmand -d (JH)
6. Re: Insights on connmand -d (JH)
----------------------------------------------------------------------
Date: Mon, 21 Oct 2019 13:38:04 +0300
From: Jussi Laakkonen <[email protected]>
Subject: Re: [PATCH] pptp: Cancel queued VPN agent msg when
disconnected
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Daniel,
On 10/21/19 10:08 AM, Daniel Wagner wrote:
> On Fri, Oct 11, 2019 at 04:52:35PM +0300, Jussi Laakkonen wrote:
>> Queued VPN agent messages must be canceled if the plugin timeouts
>> without starting the process. This fixes the issue of having multiple
>> VPN agent queries stacked on another in such scenario, where PPTP is
>> awaiting for user input.
>
> Patch applied.
>
Great, but I'm not seeing this patch in the tree yet. The OpenConnect
content is, though.
Also, the new mailing list software seemed to have missed this reply as
well
(https://lists.01.org/hyperkitty/list/[email protected]/thread/RCSWYKBT4MGNAHEJIFNEZIVCB64IT3DU/).
Some other replies that I've received seem to be omitted from there as
well. Does it filter the content based on "To:" and ignores all "Cc:"?
Cheers,
Jussi
------------------------------
Date: Mon, 21 Oct 2019 15:51:32 +0200
From: Daniel Wagner <[email protected]>
Subject: Re: [PATCH] pptp: Cancel queued VPN agent msg when
disconnected
To: Jussi Laakkonen <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Jussi,
On 21.10.19 12:38, Jussi Laakkonen wrote:
> Hi Daniel,
>
> On 10/21/19 10:08 AM, Daniel Wagner wrote:
>> On Fri, Oct 11, 2019 at 04:52:35PM +0300, Jussi Laakkonen wrote:
>>> Queued VPN agent messages must be canceled if the plugin timeouts
>>> without starting the process. This fixes the issue of having multiple
>>> VPN agent queries stacked on another in such scenario, where PPTP is
>>> awaiting for user input.
>>
>> Patch applied.
>>
>
> Great, but I'm not seeing this patch in the tree yet. The OpenConnect
> content is, though.
Ooops, forgot to push. Should be there now.
> Also, the new mailing list software seemed to have missed this reply as
> well
> (https://lists.01.org/hyperkitty/list/[email protected]/thread/RCSWYKBT4MGNAHEJIFNEZIVCB64IT3DU/).
>
> Some other replies that I've received seem to be omitted from there as
> well. Does it filter the content based on "To:" and ignores all "Cc:"?
Didn't realize the mailing list was migrated. Unfortunately, I don't
have admin access and I can't login with my old account. Grrr, I try to
figure out what's happening.
Thanks,
Daniel
------------------------------
Date: Mon, 21 Oct 2019 15:09:44 -0000
From: [email protected]
Subject: Re: problem changing wired connection from dhcp -> manual
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
I apologize. I mis-typed. That should have read 1.37. So it's in the current
version.
------------------------------
Date: Mon, 21 Oct 2019 15:17:45 -0000
From: [email protected]
Subject: Re: problem changing wired connection from dhcp -> manual
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
I apologize for mis-typing. It should have said connman version 1.37, not
1.27. So the problem is in the current version. Again I apologize for the
confusion.
Tom
------------------------------
Date: Tue, 22 Oct 2019 10:02:19 +1100
From: JH <[email protected]>
Subject: Re: Insights on connmand -d
To: David Weidenkopf <[email protected]>
Cc: Daniel Wagner <[email protected]>, connman <[email protected]>
Message-ID:
<CAA=hcWQ7aZNP=Y6n+Lm4dDhBCkhPFCH0b_qj6p=-yFKEOVVM=g...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi David,
How did you edit the service file to add -d? Also, how could you added
-d to service file in Yocto recipe?
I could not start connman after added -d
# vi /lib/systemd/system/connman.service
ExecStart=/usr/sbin/connmand -n -d
Job for connman.service failed because the control process exited with
error code.
See "systemctl status connman.service" and "journalctl -xe" for details.
Thank you.
Kind regards
On 10/22/19, David Weidenkopf <[email protected]> wrote:
> Hi,
>
> We use a yocto build as well. I routinely edit the service file to add -d to
How did you edit the service file to add -d? Also, how could you added
-d to service file in Yocto recipe?
I could not start connman after added -d
# vi /lib/systemd/system/connman.service
ExecStart=/usr/sbin/connmand -n -d
Job for connman.service failed because the control process exited with
error code.
See "systemctl status connman.service" and "journalctl -xe" for details.
> increase logging. We don't use LTE, just WiFi.
I am using both WiFi and LTE, both could not come up in systemd
service, i could only bring them up run the connmand -d manually.
> Can you confirm exactly the steps you are trying and the expected result?
Is it the right way to edit connman.service above?
Thanks David.
> David
> ________________________________________
> From: JH [[email protected]]
> Sent: Monday, October 21, 2019 2:41 AM
> To: David Weidenkopf
> Cc: Daniel Wagner; connman
> Subject: Re: Insights on connmand -d
>
> Hi Daniel and David,
>
> The connman was built by Yocto recipe, automatically launched by
> systemd service set up by the Yocto connman recipe.
>
> Any suggestion how to fix that issue or any workarounds? The connman
> is installed in an embedded device, currently I use the debug port to
> access the device and to stop systemd connman and to run command -d
> manually, it is not feasible to do it when a device is installed
> remotely.
>
> Thank you.
>
> Kind regards,
>
> - jh
>
>
>
> On 10/2/19, JH <[email protected]> wrote:
>> On 10/2/19, David Weidenkopf <[email protected]> wrote:
>>> What user are you running connmand -d as? What user is the service
>>> running
>>> as when you launch using systemctl?
>>
>> Running root in connmand -d and root for systemctl for connman.service
>> in imx6 platform.
>>
>> Thanks David.
>>
>>>
>>> ________________________________________
>>> From: JH [[email protected]]
>>> Sent: Monday, September 30, 2019 6:49 PM
>>> To: Daniel Wagner
>>> Cc: connman
>>> Subject: Re: Insights on connmand -d
>>>
>>> Hi Daniel,
>>>
>>> On 10/1/19, Daniel Wagner <[email protected]> wrote:
>>>> Hi,
>>>>
>>>> On 9/30/19 12:51 AM, JH wrote:
>>>>> Could anyone give some insights on what connmand -d differs to
>>>>> connmand -n running by systemctl? From reading the documentation, my
>>>>> understanding is it should be identical except increasing debug level
>>>>> to printing out more debug messages, but the systemd service connmand
>>>>> -n incapable of bringing my LTE modem up makes my wandering what I
>>>>> could get wrong here, could the connman -n service messages be blocked
>>>>> by journal logs? Appreciate anyone helps to fix it,
>>>>
>>>> Yes the behavior of ConnMan doesn't change with or without '-d'. It
>>>> executes the exact same code. It's more like enabling a fancy function
>>>> tracer.
>>>
>>> That completed puzzled me, the LTE modem could not be up until I run
>>> systemctl stop connman and connmand -d. It is the latest version 1.36.
>>>
>>>
>>>> I don't know if journald blocks if the logging store gets full or not.
>>>> But you could try to increase the log buffer for testing. Just to rule
>>>> out this problem.
>>>
>>> Changed journald log buffer size, it did not help. Any suggestion how
>>> to debug and fix it?
>>>
>>> Thank you Daniel.
>>>
>>> Kind regards,
>>> _______________________________________________
>>> connman mailing list -- [email protected]
>>> To unsubscribe send an email to [email protected]
>>> This e-mail and any files transmitted with it are the property of
>>> Arthrex,
>>> Inc. and/or its affiliates, are confidential, and are intended solely
>>> for
>>> the use of the individual or entity to whom this e-mail is addressed. If
>>> you
>>> are not one of the named recipient(s) or otherwise have reason to
>>> believe
>>> that you have received this message in error, please notify the sender
>>> at
>>> 239-643-5553 and delete this message immediately from your computer. Any
>>> other use, retention, dissemination forwarding, printing or copying of
>>> this
>>> e-mail is strictly prohibited. Please note that any views or opinions
>>> presented in this email are solely those of the author and do not
>>> necessarily represent those of the company. Finally, while Arthrex uses
>>> virus protection, the recipient should check this email and any
>>> attachments
>>> for the presence of viruses. The company accepts no liability for any
>>> damage
>>> caused by any virus transmitted by this email.
>>>
>>
> This e-mail and any files transmitted with it are the property of Arthrex,
> Inc. and/or its affiliates, are confidential, and are intended solely for
> the use of the individual or entity to whom this e-mail is addressed. If you
> are not one of the named recipient(s) or otherwise have reason to believe
> that you have received this message in error, please notify the sender at
> 239-643-5553 and delete this message immediately from your computer. Any
> other use, retention, dissemination forwarding, printing or copying of this
> e-mail is strictly prohibited. Please note that any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of the company. Finally, while Arthrex uses
> virus protection, the recipient should check this email and any attachments
> for the presence of viruses. The company accepts no liability for any damage
> caused by any virus transmitted by this email.
>
------------------------------
Date: Tue, 22 Oct 2019 10:39:55 +1100
From: JH <[email protected]>
Subject: Re: Insights on connmand -d
To: David Weidenkopf <[email protected]>
Cc: Daniel Wagner <[email protected]>, connman <[email protected]>
Message-ID:
<CAA=hcwrqetyrumtxpkurtg0cazmyk+ynrcmu5uatevzmhz7...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
My apology, that was not exactly right, please ignore my previous email.
I tried to edit ExecStart=/usr/sbin/connmand -n -d, it was running
fine, but still could not bring networks up, the
ExecStart=/usr/sbin/connmand -d did not work obviously that was not
right.
So it is not just increase the debug level which could bring all
networks up, it was running the connmand -d in a terminal shell
command line that could bring all networks up.
It is really puzzled, why running commond -d in a terminate shell
command line works, but could not work with systemd service? missing
some environment setup?
Thank you.
- jh
On 10/22/19, JH <[email protected]> wrote:
> Hi David,
>
> How did you edit the service file to add -d? Also, how could you added
> -d to service file in Yocto recipe?
>
> I could not start connman after added -d
>
> # vi /lib/systemd/system/connman.service
> ExecStart=/usr/sbin/connmand -n -d
>
> Job for connman.service failed because the control process exited with
> error code.
> See "systemctl status connman.service" and "journalctl -xe" for details.
>
> Thank you.
>
> Kind regards
> On 10/22/19, David Weidenkopf <[email protected]> wrote:
>> Hi,
>>
>> We use a yocto build as well. I routinely edit the service file to add -d
>> to
> How did you edit the service file to add -d? Also, how could you added
> -d to service file in Yocto recipe?
>
> I could not start connman after added -d
>
> # vi /lib/systemd/system/connman.service
> ExecStart=/usr/sbin/connmand -n -d
>
> Job for connman.service failed because the control process exited with
> error code.
> See "systemctl status connman.service" and "journalctl -xe" for details.
>
>> increase logging. We don't use LTE, just WiFi.
>
> I am using both WiFi and LTE, both could not come up in systemd
> service, i could only bring them up run the connmand -d manually.
>
>> Can you confirm exactly the steps you are trying and the expected result?
>
> Is it the right way to edit connman.service above?
>
> Thanks David.
>
>> David
>> ________________________________________
>> From: JH [[email protected]]
>> Sent: Monday, October 21, 2019 2:41 AM
>> To: David Weidenkopf
>> Cc: Daniel Wagner; connman
>> Subject: Re: Insights on connmand -d
>>
>> Hi Daniel and David,
>>
>> The connman was built by Yocto recipe, automatically launched by
>> systemd service set up by the Yocto connman recipe.
>>
>> Any suggestion how to fix that issue or any workarounds? The connman
>> is installed in an embedded device, currently I use the debug port to
>> access the device and to stop systemd connman and to run command -d
>> manually, it is not feasible to do it when a device is installed
>> remotely.
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - jh
>>
>>
>>
>> On 10/2/19, JH <[email protected]> wrote:
>>> On 10/2/19, David Weidenkopf <[email protected]> wrote:
>>>> What user are you running connmand -d as? What user is the service
>>>> running
>>>> as when you launch using systemctl?
>>>
>>> Running root in connmand -d and root for systemctl for connman.service
>>> in imx6 platform.
>>>
>>> Thanks David.
>>>
>>>>
>>>> ________________________________________
>>>> From: JH [[email protected]]
>>>> Sent: Monday, September 30, 2019 6:49 PM
>>>> To: Daniel Wagner
>>>> Cc: connman
>>>> Subject: Re: Insights on connmand -d
>>>>
>>>> Hi Daniel,
>>>>
>>>> On 10/1/19, Daniel Wagner <[email protected]> wrote:
>>>>> Hi,
>>>>>
>>>>> On 9/30/19 12:51 AM, JH wrote:
>>>>>> Could anyone give some insights on what connmand -d differs to
>>>>>> connmand -n running by systemctl? From reading the documentation, my
>>>>>> understanding is it should be identical except increasing debug level
>>>>>> to printing out more debug messages, but the systemd service connmand
>>>>>> -n incapable of bringing my LTE modem up makes my wandering what I
>>>>>> could get wrong here, could the connman -n service messages be
>>>>>> blocked
>>>>>> by journal logs? Appreciate anyone helps to fix it,
>>>>>
>>>>> Yes the behavior of ConnMan doesn't change with or without '-d'. It
>>>>> executes the exact same code. It's more like enabling a fancy function
>>>>> tracer.
>>>>
>>>> That completed puzzled me, the LTE modem could not be up until I run
>>>> systemctl stop connman and connmand -d. It is the latest version 1.36.
>>>>
>>>>
>>>>> I don't know if journald blocks if the logging store gets full or not.
>>>>> But you could try to increase the log buffer for testing. Just to rule
>>>>> out this problem.
>>>>
>>>> Changed journald log buffer size, it did not help. Any suggestion how
>>>> to debug and fix it?
>>>>
>>>> Thank you Daniel.
>>>>
>>>> Kind regards,
>>>> _______________________________________________
>>>> connman mailing list -- [email protected]
>>>> To unsubscribe send an email to [email protected]
>>>> This e-mail and any files transmitted with it are the property of
>>>> Arthrex,
>>>> Inc. and/or its affiliates, are confidential, and are intended solely
>>>> for
>>>> the use of the individual or entity to whom this e-mail is addressed.
>>>> If
>>>> you
>>>> are not one of the named recipient(s) or otherwise have reason to
>>>> believe
>>>> that you have received this message in error, please notify the sender
>>>> at
>>>> 239-643-5553 and delete this message immediately from your computer.
>>>> Any
>>>> other use, retention, dissemination forwarding, printing or copying of
>>>> this
>>>> e-mail is strictly prohibited. Please note that any views or opinions
>>>> presented in this email are solely those of the author and do not
>>>> necessarily represent those of the company. Finally, while Arthrex uses
>>>> virus protection, the recipient should check this email and any
>>>> attachments
>>>> for the presence of viruses. The company accepts no liability for any
>>>> damage
>>>> caused by any virus transmitted by this email.
>>>>
>>>
>> This e-mail and any files transmitted with it are the property of
>> Arthrex,
>> Inc. and/or its affiliates, are confidential, and are intended solely for
>> the use of the individual or entity to whom this e-mail is addressed. If
>> you
>> are not one of the named recipient(s) or otherwise have reason to believe
>> that you have received this message in error, please notify the sender at
>> 239-643-5553 and delete this message immediately from your computer. Any
>> other use, retention, dissemination forwarding, printing or copying of
>> this
>> e-mail is strictly prohibited. Please note that any views or opinions
>> presented in this email are solely those of the author and do not
>> necessarily represent those of the company. Finally, while Arthrex uses
>> virus protection, the recipient should check this email and any
>> attachments
>> for the presence of viruses. The company accepts no liability for any
>> damage
>> caused by any virus transmitted by this email.
>>
>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 48, Issue 28
***************************************
