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. DBus connection to VPN in 1.39 (Andrew Bibb)


----------------------------------------------------------------------

Date: Sat, 27 Feb 2021 08:58:30 -0500
From: Andrew Bibb <[email protected]>
Subject: DBus connection to VPN in 1.39
To: [email protected]
Message-ID:  <[email protected]
        prd13.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed

I've run across a problem that I think is DBus related in version 1.39.  
I can provision a VPN service without issue. I can also manually connect 
and disconnect from the newly provisioned service without issue using 
the Services Connect() and Services Disconnect() methods. When I then 
try to use the Services SetProperty(AutoConnect) method on the VPN 
service the following error is returned "Message recipient disconnected 
from message bus without replying".  Trying with connmanctl config 
--autoconnect results in the same error.  This used to work so to check 
I downgraded Connman from 1.39 to 1.38 and after doing that I can toggle 
AutoConnect for VPN on and off without issue using the Services 
SetProperty(AutoConnect) method.

This is on an Arch Linux system so the thing I don't know is if it is 
Arch related or Connman related.  If this is something at the Connman 
end I'll do what I can to help.  I really don't know C, but I'll try.

Thank you
Andrew Bibb

------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]


------------------------------

End of connman Digest, Vol 64, Issue 15
***************************************

Reply via email to