On Tue, 2016-02-09 at 19:24 -0500, Andrew Bibb wrote:
The file pointed to by OpenVPN.ConfigFile has no entry for
so I tried adding that line with it pointing /var and then /tmp
(reboot between) and no luck.
--tmp-dir is better placed in /tmp. Stopping the vpn service and killing
connman-vpnd should be enough.
ps axu | grep openvpn returns one line so it appears that the daemon
In connmanctl immediately after typing "connect" an error is returned:
Error /net/connman/service/SERVICE_NAME: Input/output error
Is connman-vpnd trying to ask input from you? Have a connmanctl running
with 'vpnagent on' to see if the user is prompted for something.
I was thinking it was a permissions error which is what led me to
mailing list posting. After trying the --tmp-dir option with no luck
I removed the single line:
CapabilityBoundingSet=CAP_KILL CAP_NET_ADMIN CAP_NET_BIND_SERVICE
If this worked, then VPNC started by connman-vpnd needs some extra
capability. For startes check that the VPNC daemon is capable of writing
into the temporary directory as it is one possible source of problems
since the capalities are now limited.
The ProtectHome and ProtectSystem lines I left in and that
of lines work. I can make a connection just as it used to.
It is very much sounding like it is not a Connman issue, but rather a
packaging issue. I can open a bug report on Arch. I also want to see
what they did between 1.31-1 and 1-31-2. I upgrade on a weekly basis
and completely missed the 1.31-1 release. It must not have been out
there for long.
The 1.31-2 does something funny when symlinking /etc/resolv.conf, it
basically drops the /run direcotory creation. But the previous version,
if installed, has already created the symlink from /etc/resolv.conf or
similar. I was unable to quickly figure out whether something else was
modified, I'm not familiar with Arch Linux packaging.