Activity log for bug #226185

Date Who What changed Old value New value Message
2008-05-03 16:33:06 Cory Albrecht bug added bug
2008-07-21 13:47:29 Thierry Carrez openvpn: status New Invalid
2008-07-22 07:51:32 Thierry Carrez openvpn: status Invalid New
2008-08-21 09:01:58 Thierry Carrez openvpn: status New Incomplete
2008-08-21 09:01:58 Thierry Carrez openvpn: statusexplanation Reopening for more discussion. What are you using as DHCP client ? Also are you using Network-Manager ? Are you using Network-Manager-OpenVPN ? I'm still convinced openvpn calls resolvconf properly, however if the other elements of the system (DHCP client / Network Manager...) modify /etc/resolv.conf without using resolvconf, openVPN's update-resolv-conf will indeed trash their settings. The system must either fully use resolvconf or fully use some other way of keeping /etc/resolv.conf sane. Note that using network-manager-openVPN instead of update-resolv-conf to update /etc/resolv.conf is apparently also buggy (DHCP keeps on overwriting the settings, see bug 247257). Also see bug 107564 for related problems and solutions. Let's set it to Incomplete, so that you can complete it in the future (or someone else can). Thanks !
2009-03-04 16:08:39 Thierry Carrez openvpn: status Incomplete Invalid
2009-03-04 16:08:39 Thierry Carrez openvpn: statusexplanation Let's set it to Incomplete, so that you can complete it in the future (or someone else can). Thanks ! Tom Dickson: your request is a separate issue. This bug was about update-resolv-conf not restoring old values, and will be set to Invalid since update-resolv-conf works properly. To avoid confusion, could you please file a separate bug about adding documentation to make it clearer how to use update-resolv-conf ? Thanks in advance.
2011-05-18 07:58:53 Andreas Steffan bug added subscriber Andreas Steffan