If none of this works, comment on their forum linking to this issue and the solutions you tried. Don't forget to restart openvpn after every change. We created ProtonVPN to protect the 1 last update 2 Does Hulu Work With Ipvanish journalists and activists who use ProtonMail. Servers in 190+ Countrieshow to Does Hulu Work With Ipvanish for Freedom. Does Hulu Work With Ipvanish Watch Hulu With A Vpn. As a last try, you could change the subnet (remove ipp.txt too) or look at other differences between this configuration and the psense one. Does Hulu Work With Ipvanish Surf The Web Privately. I don't think so, it talks specifically about DNS. Try to change push "redirect-gateway def1 bypass-dhcp" to push "redirect-gateway def1".ĭo you think that might be why I'm getting this warning? redirect-gateway def1 to your configuration file. If OpenVPN connects to the server properly but your IP address does not change, you are probably missing the "-redirect-gateway" option. Try to enable this option in Tunnelblick. Since the DNS queries originate from the VPN, which is outside of that network, the queries will not be answered. Often a DHCP-supplied server will only respond to queries which originate within that network. When DHCP is renewed, the change is ignored (because "Monitor connection" isn't checked) and the VPN-supplied DNS server is replaced with the DHCP-supplied server. You don't have "Monitor connection" checked. Only when connecting to an OpenVPN server created with openvpn-install I see this warning (but again, it's just a warning and everything works as expected) In fact, I've been connecting from this same laptop to an OpenVPN server running in my firewall (pfSense) for years, and I've never seen this warning before. Note that this is not the first OpenVPN solution I set up. Client: Tunnelblick 3.8.2a (build 5481).I'm using the latest version of Tunnelblick: "Tunnelblick: macOS 10.15.5 (19F101) Tunnelblick 3.8.2a (build 5481)" In Tunnelblick I've manually enabled "Route all IPv4 traffic through the VPN".Įverything works, and there's no DNS leak (I can confirm that). In this case, 10.1.0.1 is the IP of my DNS server within the LAN that I would normally connect to (this is set through DHCP so it's not static). When I connect with Tunnelblick, I always get this warning: "Warning: DNS server address 10.1.0.1 is not a public IP address and is not being routed through the VPN." I set up an OpenVPN server using this script. My issue is about the script, and not OpenVPN itself (I believe).
0 Comments
Leave a Reply. |