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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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