Hi, Jeff Licquia wrote: > If network-manager-openvpn does things to break networking without > resolvconf being installed, then we need to make sure that we install > resolvconf in the normal case when n-m-openvpn is installed.
ehh.. that is definitely NOT a solution, because it will open up problems for another user base of n-m-openvpn. 1) The actual problem seems to be a bug in nm or in nm-openvpn (depending on the pov), where /etc/resolv.conf is overwritten if there is no dns pushed. That is: nm-openvpn transmit an empty list and nm seems to take this for a reason to delete out all entries in resolv.conf. This would be solved by resolvconf, because network-manager wouldn't alter /etc/resolv.conf *at all anymore* 2) Forcing resolvconf would break functionality for those who *want* to use (from the openvpn endpoint) pushed settings, because they just won't get them. So the only real solution to this problem is a check either in nm or nm-openvpn that impedes the behaviour. Regards, Patrick
signature.asc
Description: Digital signature
