07-28-2015, 07:19 PM
I have my own OpenVPN Access Server. To install my OpenVPN client and connect to my Access Server, I follow the instructions at https://openvpn.net/index.php/access-ser...ients.html. When I have the server redirect internet browsing, so that the network my Access Server is connected to handles the browsing, I can ping IP addresses, but I cannot ping domain names or browse the internet. For example, I can ping the Google public DNS server 8.8.8.8, but I cannot ping or browse to www.google.com.
I put in a ticket with the folks at OpenVPN. They led me to my /etc/resolv.conf file, which shows my nameserver as 127.0.0.1. When I changed the nameserver to 8.8.8.8, I could ping ip addresses and domain names and browse the internet. Using www.ipchicken.com, my internet browsing appeared to be coming from the same public IP address as my OpenVPN Access Server. This was the result I was looking for. But after rebooting, the nameserver returned to 127.0.0.1.
As a workaround for this, I added 8.8.8.8 as an Additional DNS Server in my Network Connections. I have been able to use another Ubuntu Linux based distro without this workaround. And the folks at OpenVPN suggested there might be something special going on with the distro I'm using (Linux Lite 2.4 64 bit) that could be causing the /etc/resolv.conf file to use the local loopback address as my nameserver.
For the record, I have LL 2.4 64bit running on my laptop and my desktop, and the behavior connecting to my OpenVPN Access Server is the same. I have to add 8.8.8.8 to my Network Connections settings, as a workaround, in order to get the expected behavior.
I put in a ticket with the folks at OpenVPN. They led me to my /etc/resolv.conf file, which shows my nameserver as 127.0.0.1. When I changed the nameserver to 8.8.8.8, I could ping ip addresses and domain names and browse the internet. Using www.ipchicken.com, my internet browsing appeared to be coming from the same public IP address as my OpenVPN Access Server. This was the result I was looking for. But after rebooting, the nameserver returned to 127.0.0.1.
As a workaround for this, I added 8.8.8.8 as an Additional DNS Server in my Network Connections. I have been able to use another Ubuntu Linux based distro without this workaround. And the folks at OpenVPN suggested there might be something special going on with the distro I'm using (Linux Lite 2.4 64 bit) that could be causing the /etc/resolv.conf file to use the local loopback address as my nameserver.
For the record, I have LL 2.4 64bit running on my laptop and my desktop, and the behavior connecting to my OpenVPN Access Server is the same. I have to add 8.8.8.8 to my Network Connections settings, as a workaround, in order to get the expected behavior.
Want to thank me? Click my [Thank] link.
