Comment 3 for bug 1046154

Revision history for this message
Thomas Hood (jdthood) wrote :

Hi there iox.

Your system is probably misconfigured in one or more ways.

If you are using NetworkManager and dnsmasq and resolvconf then /etc/resolv.conf will list only "nameserver 127.0.0.1". But you say that you are using NetworkManager and dnsmasq and with resolvconf installed you had

    nameserver 195.81.137.130
    nameserver 195.81.155.194
    nameserver 192.168.163.200
    search dummy.intranet

Here 127.0.0.1 is not listed. It looks as if dnsmasq is not really activated. The internal nameserver is, I take it, 192.168.163.200. This should be listed first, not last.

If you are using NetworkManager to establish openvpn connections then you don't need to change any scripts. NetworkManager receives the nameserver addresses from openvpn and submits them to resolvconf.

Your original problem may have been due to bug #1003842. The fact that the connection type (and thus speed) was a factor makes it more probable that #1003842 was the problem.

In your initial attempts to solve the original problem it is possible that you changed the NetworkManager, resolvconf, etc., configurations. These should be returned to their original state. The workaround for #1003842 is to comment out the line

    dns=dnsmasq

in /etc/NetworkManager/NetworkManager.conf.