connman removes FallbackNameservers at startup
Hello, I noticed an issue with FallbackNameservers. When connman starts on system boot it tries to connect to name servers that are specified in FallbackNameservers. But NIC is usually not ready by that moment and connman removes name servers with message: Failed to connect to server 8.8.8.8 So when I run ./list-services script I do not see Nameservers that was specified. -- Regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: openvpn: client ip doesn't change
Hello, What about this issue? Has anyone started to work on it already? Seems to be important for those who use VPN with dynamic IP address assignment. I was investigating the code to fix this issue by myself but not quite understand how everything is working. What I found is that the problem is in VPN plugin for connman. Connman simply doesn't update IP address when reconnects to VPN. Could you provide the log output with 'connman-vpnd -n -d' for this? Here client gets IP 10.10.10.149 and after server restart its IP is changing to 10.10.10.129 but ifconfig says it's still 10.10.10.149. After this any VPN resource becomes unavailable. Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:do_connect() conn 0x1c0a450 provider 0x1c13080 Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:__vpn_provider_connect() provider 0x1c13080 Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/plugins/vpn.c:vpn_connect() data (nil) state 0 Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_ref_debug() 0x1c13080 ref 2 by vpn/plugins/vpn.c:378:vpn_connect() Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_set_index() index 4 provider 0x1c13080 Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-ipconfig.c:__vpn_ipconfig_create() index 4 Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-ipconfig.c:__vpn_ipconfig_create() ipconfig 0x1c0d110 Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-ipconfig.c:create_ipv6config() index 4 Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-ipconfig.c:create_ipv6config() ipconfig 0x1c0a9b0 Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_create() Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_create() task 0x1c0aa10 Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_set_notify() task 0x1c0aa10 Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key Host Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key Host Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_add_argument() task 0x1c0aa10 arg --remote Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.CACert Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.Cert Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.Key Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.MTU Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.NSCertType Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.Proto Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.Port Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.AuthUserPass Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.AskPass Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.AuthNoCache Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.TLSRemote Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.Cipher Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.Auth Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.CompLZO Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.RemoteCertTls Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.ConfigFile Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_add_argument() task 0x1c0aa10 arg --config Jun 21 01:44:33 testpc connman-vpnd[355]: vpn/vpn-provider.c:vpn_provider_get_string() provider 0x1c13080 key OpenVPN.ConfigFile Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_add_argument() task 0x1c0aa10 arg --syslog Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_add_argument() task 0x1c0aa10 arg --script-security Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_add_argument() task 0x1c0aa10 arg --up Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_add_argument() task 0x1c0aa10 arg --up-restart Jun 21 01:44:33 testpc connman-vpnd[355]: src/task.c:connman_task_add_argument() task 0x1c0aa10
Re: openvpn: client ip doesn't change
2014-05-21 15:43 GMT+03:00 Jukka Rissanen jukka.rissa...@linux.intel.com: On ke, 2014-05-21 at 10:16 +0300, Patrik Flykt wrote: On Wed, 2014-05-21 at 00:29 +0300, Yevhen Kyriukha wrote: It is a config for openvpn (/etc/openvpn). Openvpn is configured on ubuntu *without* connman. You can create simple server config and put ifconfig-pool-persist ipp.txt option to it. It will be enough for testing. This file is not read when openvpn is started by connman-vpnd. See doc/vpn-config-format.txt to see if there already is an option you can use. There is a OpenVPN.ConfigFile option available that can pass an OpenVPN configuration file via connman-vpnd to OpenVPN client process. Unfortunately it is not currently documented in vpn-config-format.txt file. Cheers, Jukka openvpn is started automatically by init script on my Ubuntu server. It is started on separate machine (without connman). I placed config file for my VPN server at /etc/openvpn, so openvpn will run it automatically. -- Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: openvpn: client ip doesn't change
Steps to reproduce: 1) In openvpn server config add ifconfig-pool-persist ipp.txt option. When a VPN program, such as openvpn, is started by connman-vpnd, all possible options are either given on the command line or written to a temporary config file supplied to the VPN program. What config file in which location did you configure in 1) above? It is a config for openvpn (/etc/openvpn). Openvpn is configured on ubuntu *without* connman. You can create simple server config and put ifconfig-pool-persist ipp.txt option to it. It will be enough for testing. 2) Create ipp.txt file and define recommended IP for the client in a following way: myclient,10.10.10.23 3) Start VPN server. 3) Establish VPN connection on client (using connman and connman-vpn). 4) Stop VPN server. Was 10.10.10.23 the default address the server would have assigned anyway? How about using 10.10.10.44 already at this step to see if it is a problem in any of the connects or just the reconnect in 6) ? It doesn't matter. Problem persists. I have around of 50 clients connected using connman so I tested this issue well. P.S.: Please, add author to CC when answering emails. -- Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
openvpn: client ip doesn't change
There is an issue when openvpn server restarts while client is been connected to it: client doesn't update its VPN IP address. Steps to reproduce: 1) In openvpn server config add ifconfig-pool-persist ipp.txt option. 2) Create ipp.txt file and define recommended IP for the client in a following way: myclient,10.10.10.23 3) Start VPN server. 3) Establish VPN connection on client (using connman and connman-vpn). 4) Stop VPN server. 5) Change IP for client in ipp.txt file: myclient,10.10.10.44 6) Start VPN server. 7) Wait for VPN connection is established on client and check IP of vpn interface. Expected results: Interface gets new IP 10.10.10.44. Actual results: Interface using old IP 10.10.10.23. This is a serious issue as user can't access VPN network without restarting VPN client. -- Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
VPN: name resolution doesn't work
My VPN server pushes DNS information for name resolution inside VPN network. I noticed that vpn name resolution was broken in latest connman (76cb209b071b521b7230deb63227516c015976b3). -- Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: VPN: name resolution doesn't work
2014-03-02 18:40 GMT+02:00 Yevhen Kyriukha kirg...@gmail.com: My VPN server pushes DNS information for name resolution inside VPN network. I noticed that vpn name resolution was broken in latest connman (76cb209b071b521b7230deb63227516c015976b3). -- Best regards, Yevhen I forgot to mention that I'm using split routing. Seems that following commit is an issue: dnsproxy: Enable added DNS servers only for the default service 2ca6fb481767d6657b43b531f51bf9ecbee986f4 -- Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
VPN nameserver issue
Hi, I have VPN connection with specified nameservers by VPN server (dhcp-option DNS). Also I have split routing for VPN connection. When connection is established name-to-ip resolution for VPN hosts works fine, but some time later when I ping host by its FQDN I see that wrong (public network) IP is used. list-services tells me that I have nameserver for VPN network but seems that it's not used. Restarting connman solves the problem. Is there any priority of nameservers in connman? Can failures of accessing to some nameservers change priority of using nameservers? -- Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: Domain name not appended to the server name
When trying the access some servers that belong to my domain, without the domain name appended to the server name, I cannot reach them. I get the same issue while been connected to VPN network. I can ping host's FQDN, but get an error while trying to ping only host name. Seems that something has been broken in the latest version of connman. -- Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Connman doesn't update localtime while setting timezone
Hi! I've set TimezoneUpdates property to manual and changed time zone with setting Timezone property. After that I expect that local time will be changed also, but it doesn't. date command shows old UTC time. I have all proper timezone info in /usr/share/zoneinfo and noticed that /etc/localtime points to a proper timezone. Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: AutoConnect of VPN
Hi! I created new VPN connection and set AutoConnect property of VPN service to true. Without establishing VPN connection I rebooted PC. On next reboot I expected that VPN connection would be established automatically but it didn't. Note that you must have a autoconnectable bearer service also available and connected before the VPN connect over it. I have ethernet connection if I understand you correctly. And AutoConnect property of it is set to true. I checked AutoConnect property of VPN connection and it had been changed to false Seems that AutoConnect property affects on connections that are established successfully. Is this right? Sounds like a bug to me. I'd like to post a bug in bug tracker but have no access to JIRA. Can you check this behavior with VPN autoconnect on your side. I think that it would be better if connman tried to connect to VPN despite the last connected state. Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: VPN Issue
2013/10/25 Jukka Rissanen jukka.rissa...@linux.intel.com Hi Yevhen, On 23.10.2013 13:29, Yevhen Kyriukha wrote: Hi! Can anyone of developers tell the current development status of this issue and some estimates on its fix: https://01.org/jira/browse/CM-**620 https://01.org/jira/browse/CM-620 I investigated this more and with current openvpn client this cannot be done with redirect-gateway option. The reason is that when OpenVPN server pushes the option to OpenVPN client, the client does not pass this option to ConnMan via environment variables. So end result is that ConnMan will not know this option and cannot act accordingly. The only solution is that the openvpn client needs to add the redirect-gateway flag value to envinronment variables when it calls the route-up script. I have a patch (attached to the bug) to ConnMan that should work if the environment variable is there. Best regards, Yevhen -- Cheers, Jukka Hi Jukka, Thanks for your status report! Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
VPN Issue
Hi! Can anyone of developers tell the current development status of this issue and some estimates on its fix: https://01.org/jira/browse/CM-620 Best regards, Yevhen ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: Connman VPN: Do not replace default route
2013/2/4 Jukka Rissanen jukka.rissa...@linux.intel.com:
Hi,
On 03.02.2013 19:11, Yevhen Kyriukha wrote:
2013/2/3 Jukka Rissanen jukka.rissa...@gmail.com:
Hi,
On 2 February 2013 15:02, Yevhen Kyriukha kirg...@gmail.com wrote:
My VPN server already push information about routes like:
server 10.10.10.0 255.255.255.0
and
push route 10.10.10.0 255.255.255.0 vpn_gateway
If I use openvpn without connman the behavior is correct (routes are
replaced only if I push redirect-gateway from the server).
This sounds like a bug.
Can you do following:
- start vpnd with connman-vpnd -n -d and direct the output to a file
- start test/monitor-vpn and direct the output to a file
- connect to your vpn (you should see server pushed routes in debug
output and also in monitor output)
- after successful connection run test/vpn-get to see if we are really
missing the ServerRoutes
Cheers,
Jukka
Ok, I did these steps and here's what I got:
When I run connman-vpnd -n -d program closes immediately (you can
find output in connman-vpn.log file that is attached). Is it
correct? Seems that system activates connman-vpnd by dbus.
The log says
No VPN configurations found, quitting.
Meaning that you do not have any VPN configurations around. Did you remove
all your VPN configurations from disk or are you running with read only
filesystem for /var/lib/connman?
In output of 'monitor-vpn' I see the following line:
ServerRoutes = [[{ ProtocolFamily=4 Netmask=255.255.255.0
Network=10.10.10.0 Gateway=10.10.10.81 }][{ ProtocolFamily=4
Netmask=255.255.255.0 Network=10.10.10.0 Gateway=10.10.10.81 }]]
And output of 'vpn-get' contains following:
ServerRoutes = [[{ ProtocolFamily=4 Netmask=255.255.255.0
Network=10.10.10.0 Gateway=10.10.10.81 }][{ ProtocolFamily=4
Netmask=255.255.255.0 Network=10.10.10.0 Gateway=10.10.10.81 }]]
This looks correct.
But 'route -n' gives me the same picture that I was talking before
(vpn is a default route iface).
This is expected as you have not moved the services yet.
If the /var/lib/connman is non-existent, then you will have weird problems
anyway.
Cheers,
Jukka
Hi!
The log says
No VPN configurations found, quitting.
Meaning that you do not have any VPN configurations around. Did you remove
all your VPN configurations from disk or are you running with read only
filesystem for /var/lib/connman?
I was writing about that problem on connman mailing list.
I have /var/lib/connman folder and it doesn't disappear after reboot.
I checked 'mount' and there was no /var or /var/lib directory mounted
as read only file system partition.
This problem appears when I restart connman-vpn and connman services
with previously *connected* (active) VPN connection. I'm not rebooting
PC! So all settings exist.
So this is the second problem.
The first one was overriding default route.
You said that if server push some info about routes connman-vpn won't
replace default route.
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
Re: Connman VPN: Do not replace default route
2013/2/3 Jukka Rissanen jukka.rissa...@gmail.com:
Hi,
On 2 February 2013 15:02, Yevhen Kyriukha kirg...@gmail.com wrote:
My VPN server already push information about routes like:
server 10.10.10.0 255.255.255.0
and
push route 10.10.10.0 255.255.255.0 vpn_gateway
If I use openvpn without connman the behavior is correct (routes are
replaced only if I push redirect-gateway from the server).
This sounds like a bug.
Can you do following:
- start vpnd with connman-vpnd -n -d and direct the output to a file
- start test/monitor-vpn and direct the output to a file
- connect to your vpn (you should see server pushed routes in debug
output and also in monitor output)
- after successful connection run test/vpn-get to see if we are really
missing the ServerRoutes
Cheers,
Jukka
Ok, I did these steps and here's what I got:
When I run connman-vpnd -n -d program closes immediately (you can
find output in connman-vpn.log file that is attached). Is it
correct? Seems that system activates connman-vpnd by dbus.
In output of 'monitor-vpn' I see the following line:
ServerRoutes = [[{ ProtocolFamily=4 Netmask=255.255.255.0
Network=10.10.10.0 Gateway=10.10.10.81 }][{ ProtocolFamily=4
Netmask=255.255.255.0 Network=10.10.10.0 Gateway=10.10.10.81 }]]
And output of 'vpn-get' contains following:
ServerRoutes = [[{ ProtocolFamily=4 Netmask=255.255.255.0
Network=10.10.10.0 Gateway=10.10.10.81 }][{ ProtocolFamily=4
Netmask=255.255.255.0 Network=10.10.10.0 Gateway=10.10.10.81 }]]
But 'route -n' gives me the same picture that I was talking before
(vpn is a default route iface).
connman-vpn.log
Description: Binary data
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
Re: Connman VPN: Do not replace default route
2013/2/2 Jukka Rissanen jukka.rissa...@gmail.com: Hi, On 1 February 2013 22:28, Yevhen Kyriukha kirg...@gmail.com wrote: I've tried 'service-move-before' but hadn't got any changes in routing table. If you want that default route is not routed via VPN, then connman needs to know which routes you want to route via VPN connection. This route information can come automatically from VPN server, or user can define the routes manually. The user settable property is called UserRoutes (see doc/vpn-connection-api.txt for details). If the route information is not known, the service-move-before cannot actually change the ordering as you have noticed. Cheers, Jukka I'm using OpenVPN, just in case. I think that if VPN server doesn't send push redirect-gateway to clients connman shouldn't replace default routes. My VPN server already push information about routes like: server 10.10.10.0 255.255.255.0 and push route 10.10.10.0 255.255.255.0 vpn_gateway If I use openvpn without connman the behavior is correct (routes are replaced only if I push redirect-gateway from the server). ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
RE: Connman VPN: Do not replace default route
Hi! How can I configure connman-vpn to leave my default route? I want that connman append VPN route so I can access my VPN network and have all other traffic go through default route. You can use connman test script service-move-before to move the service to the first one. The first service gets the default route. I've tried 'service-move-before' but hadn't got any changes in routing table. I have ethernet connection and I want to establish VPN connection. After VPN connection is established, I run 'service-move-before ethernet_service_path vpn_service_path' but 'route -n' command gives me the same result as before executing 'service-move-before' script. Is there any option besides executing 'service-move-before' to tell connman simply not to override default routes? ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Connman VPN: dhcp-option is ignored
Hi! My VPN server sends dhcp-option with name server and domain information. But connman-vpn seems to ignore them. I can't use domain names of my VPN network. Does connman-vpn support these features? Thanks! ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
RE: Can't connect to VPN
Hi! On Mon, 14 Jan 2013 00:58:03 +, Zheng, Jeff wrote: I can connect to openvpn server in my environment (and commit c388d1a) by: 1. Make sure the cert files ready 2. connect-provider openvpn openvpn 192.168.2.1 mydomain /openvpn/ca.crt /openvpn/client1.crt /openvpn/client1.key After that, I can do operations on service vpn_192_168_2_1_mydomain using test-connman utility. I could not make autoconnect work, but I think I can connect it in a startup script. connect-provider seems to create connection each time you call it and connection lives during your active session. You can restart connman-vpn service and your connection will become unusable. The problem is that when you already have created connection you can't use it after reboot, you need to create new one (with the same parameters). Maybe I just don't understand the behavior of connman-vpn daemon, but I thought that it has to use already created connection. I thought that I don't need to rerun any script like connect-provider after my VPN connection was customized. And autoconnect at boot time is the second problem. -- Best regards, Yevhen ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Can't connect to VPN
Hi! Could anyone help me with configuring VPN, I can't get it work. I'm using connman v1.10. I created settings for my VPN connection in /var/lib/connman directory. I want connman to bring VPN connection automatically at boot time. But connman-vpn daemon doesn't see config files: when I run vpn-get script to get available VPN services I see No VPN configurations found, quitting in syslog. P.S.: I'm using '--localstatedir=/var' option for configure. I checked /var/lib/connman after reboot and settings are there (they aren't created in tmpfs). There is a /var/lib/connman/provider_vpnhost_ua_ directory and it has settings file with following content: [vpnhost_ua_] Name=MyVpn Type=openvpn Host=vpnhost.ua VPN.Domain= OpenVPN.CACert=/var/lib/vpn/ca.crt OpenVPN.Cert=/var/lib/vpn/client.crt OpenVPN.Key=/var/lib/vpn/client.key where vpnhost is my VPN server. Connman-vpn doesn't see these settings. Help me please with this problem. -- Best regards, Yevhen ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Can't connect to VPN
I'm building connman for Rasberry Pi device with following configure options:
--build=x86_64-linux --host=arm-oe-linux-gnueabi
--target=arm-oe-linux-gnueabi --prefix=/usr
--exec_prefix=/usr --bindir=/usr/bin
--sbindir=/usr/sbin --libexecdir=/usr/lib/connman
--datadir=/usr/share--sysconfdir=/etc
--sharedstatedir=/com --localstatedir=/var
--libdir=/usr/lib --includedir=/usr/include
--oldincludedir=/usr/include
--infodir=/usr/share/info --mandir=/usr/share/man
--disable-silent-rules
--disable-dependency-tracking
--with-libtool-sysroot=/home/administrator/openembedded-core/pi-build/tmp-eglibc/sysroots/raspberrypi
ac_cv_path_WPASUPPLICANT=/usr/sbin/wpa_supplicant
ac_cv_path_PPPD=/usr/sbin/pppd --enable-debug --enable-threads
--enable-loopback --enable-ethernet --enable-openvpn
--enable-wifi --enable-tist --enable-bluetooth --enable-tist
--enable-tools --enable-test --disable-polkit
--enable-client --enable-nls --disable-gtk-doc
--disable-gtk-doc-html --disable-gtk-doc-pdf
I create a connection with connect-provider and ONLY after that I
see some output from vpn-get script and can connect to VPN. BUT
until reboot!
After reboot I get nothing on vpn-get execution and can't connect to
existing VPN provider.
Also I checked /var/lib/connman/ directory and settings folder is there.
I attached connman-vpn debug log.
--
Best regards,
Yevhen
connman-vpnd[216]: Connection Manager VPN daemon version 1.10
connman-vpnd[216]: src/dbus.c:__connman_dbus_init()
connman-vpnd[216]: src/agent.c:__connman_agent_init()
connman-vpnd[216]: vpn/vpn-provider.c:__vpn_provider_init()
connman-vpnd[216]: src/agent.c:connman_agent_driver_register() Registering
driver 0x332b4 name vpn
connman-vpnd[216]: vpn/vpn-manager.c:__vpn_manager_init()
connman-vpnd[216]: vpn/vpn-ipconfig.c:__vpn_ipconfig_init()
connman-vpnd[216]: vpn/vpn-rtnl.c:__vpn_rtnl_init()
connman-vpnd[216]: src/task.c:__connman_task_init()
connman-vpnd[216]: src/plugin.c:__connman_plugin_init()
connman-vpnd[216]: driver 0x8804ac name openvpn
connman-vpnd[216]: provider type openvpn
connman-vpnd[216]: vpn/vpn-rtnl.c:__vpn_rtnl_start()
connman-vpnd[216]: conn 0x878460
connman-vpnd[216]: vpn/vpn-provider.c:__vpn_provider_get_connections()
connman-vpnd[216]: lo {newlink} index 1 operstate 0 UNKNOWN
connman-vpnd[216]: eth0 {create} index 2 type 1 ETHER
connman-vpnd[216]: eth0 {update} flags 102467 UP,RUNNING,LOWER_UP
connman-vpnd[216]: eth0 {newlink} index 2 address B8:27:EB:C7:AF:EA mtu 1500
connman-vpnd[216]: eth0 {newlink} index 2 operstate 6 UP
connman-vpnd[216]: No VPN configurations found, quitting.
connman-vpnd[216]: Terminating
connman-vpnd[216]: src/plugin.c:__connman_plugin_cleanup()
connman-vpnd[216]: driver 0x8804ac name openvpn
connman-vpnd[216]: src/task.c:__connman_task_cleanup()
connman-vpnd[216]: vpn/vpn-rtnl.c:__vpn_rtnl_cleanup()
connman-vpnd[216]: vpn/vpn-ipconfig.c:__vpn_ipconfig_cleanup()
connman-vpnd[216]: eth0 {remove} index 2
connman-vpnd[216]: vpn/vpn-manager.c:__vpn_manager_cleanup()
connman-vpnd[216]: vpn/vpn-provider.c:__vpn_provider_cleanup()
connman-vpnd[216]: src/agent.c:connman_agent_driver_unregister() Unregistering
driver 0x332b4 name vpn
connman-vpnd[216]: src/agent.c:__connman_agent_cleanup()
connman-vpnd[216]: src/dbus.c:__connman_dbus_cleanup()
connman-vpnd[216]: Exit
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
Re: Can't connect to VPN
I checked /var/lib/connman after reboot and settings are there. There is a /var/lib/connman/provider_vpnhost_ua_ directory and it has settings file with following content: [vpnhost_ua_] Name=MyVpn Type=openvpn Host=vpnhost.ua VPN.Domain= OpenVPN.CACert=/var/lib/vpn/ca.crt OpenVPN.Cert=/var/lib/vpn/client.crt OpenVPN.Key=/var/lib/vpn/client.key where vpnhost is my VPN server. Connman-vpn doesn't see these settings. Any thoughts? -- Best regards, Yevhen ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Can't connect to VPN
Hi! I'm using connman v1.10. I created settings for my VPN connection in /var/lib/connman directory. I want connman to bring VPN connection automatically at boot time. But connman-vpn daemon doesn't see config files: when I run vpn-get script to get available VPN services I see No VPN configurations found, quitting in syslog. I can connect to VPN only if I execute connect-provider script which creates connection and then connects to it. Then I get some output from vpn-get, but until reboot of connman-vpn service. Very strange issue. Could you help me, please. -- Best regards, Yevhen ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
