Running OpenVPN Connect 1.1.16 (build74) on a MotoX 2014
I have two profiles - one for my 4G data connection and one for my WiFi.
My Wifi subnet is 172.18.2.0/24 IP 172.18.2.52, the OpenVPN server is 172.18.2.1 and the 4G is dynamic, naturally.
It seems that OpenVPN keeps trying to access the OpenVPN server 172.18.2.1 through the 4G interface even though the WiFi is on the same subnet as the OpenVPN server. Only when I disable the 4G, I am able to connect the the OpenVPN server. After this, I can enable the 4G, and the OpenVPN tunnel continues to work.
This was not a problem before upgrading to Android 5.0 in 2014. I expected this to be a error related to the Android OS, and I expected the issue to be resolved in the next android update... This took ages, and now, a couple of weeks ago, when I received Android 5.0.1 (I think... System info still reports 5.0), the issue persists.
Anyone of you knows a workaround to this issue?
Client config is:
------------------
client
dev tun
local 172.18.2.52
lport 0
proto udp
remote 172.18.2.1 11194
resolv-retry infinite
persist-key
persist-tun
ca ca.crt
cert motox.crt
key motox.key
ns-cert-type server
remote-cert-tls server
tls-auth ta.key 1
cipher AES-256-CBC
comp-lzo
verb 3
------------------------
Regards, Lars.
Binding on wrong interface (I guess)
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
-
- OpenVpn Newbie
- Posts: 13
- Joined: Sun Jun 14, 2015 8:01 am
- Traffic
- OpenVPN Protagonist
- Posts: 4066
- Joined: Sat Aug 09, 2014 11:24 am
Re: Binding on wrong interface (I guess)
As the server generally configures the client can you post your server config please.
-
- OpenVpn Newbie
- Posts: 13
- Joined: Sun Jun 14, 2015 8:01 am
Re: Binding on wrong interface (I guess)
Sorry for taking so long. Meanwhile a new Android update was reaching my phone making the problem even worse as this Android version will not auto connect wifi network that it classifies as "no connection".Traffic wrote:As the server generally configures the client can you post your server config please.
My server conf:
$ cat wifi.conf
----------
local x.x.x.x
port 11194
proto udp
dev tun1
ca /something.crt
cert /something.crt
key /something.key # This file should be kept secret
dh /something.pem
server 10.19.5.0 255.255.255.0
ifconfig-pool-persist ipp_wifi.txt
push "redirect-gateway def1"
push "redirect-gateway def1 bypass-dhcp"
push "dhcp-option DNS a.b.c.d"
push "dhcp-option WINS e.f.g.h"
client-to-client
keepalive 10 120
tls-auth /somethingta.key 0 # This file is secret
cipher AES-256-CBC
comp-lzo
max-clients 10
user _openvpn
group _openvpn
persist-key
persist-tun
status openvpn_wifi-status.log 10
status-version 2
crl-verify /somethingcrl.pem
log-append /something.log
verb 4
mute 20
---------
Regards, Lars.
-
- OpenVpn Newbie
- Posts: 13
- Joined: Sun Jun 14, 2015 8:01 am
Re: Binding on wrong interface (I guess)
...but actually I think the problem is at the client side as described on my original post. The client does not even seem to hit the server.Traffic wrote:As the server generally configures the client can you post your server config please.
Regards, Lars.
- Traffic
- OpenVPN Protagonist
- Posts: 4066
- Joined: Sat Aug 09, 2014 11:24 am
Re: Binding on wrong interface (I guess)
Your sever is redirecting your client gateway with:
Do not connect to both VPNs at the same time .. do they work separately ?bonne wrote:push "redirect-gateway def1 bypass-dhcp"
-
- OpenVpn Newbie
- Posts: 13
- Joined: Sun Jun 14, 2015 8:01 am
Re: Binding on wrong interface (I guess)
Problem seemed to be on Android. Captive portal detection had to be disabled:
http://android.stackexchange.com/questi ... k-on-wi-fi
http://android.stackexchange.com/questi ... k-on-wi-fi