So I received my new Nexus 6P yesterday, and spent last night setting it up. However this morning I've run into an odd problem, and not sure how to solve it. I'm using OpenVPN connect to connect to our office (pfSense router running OpenVPN), and I had tested it last night and it works fine (when connected to my home WiFi (pure IPv4)). However, this morning on LTE I was having problems (basically appears traffic routes if I use IP's, but DNS just doesn't work at all), and I'm wondering if this is related to the fact that when on LTE I'm getting an IPv6 address. I was going to try and disable that, but evidently I have to root my device to disable IPv6 (impressed IPv6 is even working with T-Mobile)..
Some additional data..
The server is configured to redirect all traffic over the VPN and it is handing out both DNS and WINS servers to clients. I've looked at the log and it looks ok ( I see log entries for the DNS ([dhcp-option] [DNS] [192.168.20.1] for example))..
Actually digging a bit in the command line, it looks like it may not be setting the DNS servers properly even though they're being handed to it (I see them in the openvpn connect log).. As right now I'm connected via WiFi and I look at the DNS server and it's my WiFi connections DNS server, not the remote one (which works because IPv4). So when I'm connected via LTE, the problem is the DNS server is still an IPv6 address (fd00:976a::9), while there's no route to that address over my IPv4 OpenVPN tunnel. This makes sense. I can't change the DNS via setprop unfortunately as again I don't have root.
So any idea's what is going wrong here? I've tried turning on/off the DNS Fallback setting as well and that doesn't help. I assume something is preventing the OpenVPN connect client from changing the DNS.
Nexus 6P Issue
-
- OpenVpn Newbie
- Posts: 2
- Joined: Wed Mar 09, 2016 4:25 pm
Re: Nexus 6P Issue
As an update, I at least found a work around. If I go into the APN for my device, I can switch the transport to IPv4 which at least allows me to connect. However I did some testing and can verify that it's not overriding the default DNS servers (so no local specific DNS resolution works). But it's an infinite improvement from earlier. So the question still remains as to why the OpenVPN Connect client isn't honoring the DNS servers being provided to it.