Red Hat Bugzilla – Bug 455899
I forget to vpnc-disconnect, next startup painfully slow
Last modified: 2008-09-10 02:41:38 EDT
I do *not* use NetworkManager.
Very often I forget to vpnc-disconnect on shutdown/reboot.
As a consequence, the vpn version of /etc/resolv.conf is still active on the
next startup, which results in a painfully slow startup, because of dns lookup
failures and timeouts.
Could the vpnc package be enhanced to automatically issue a vpnc-disconnect when
we go to shutdown? (runlevel 6 ?)
I have used upstart event for cleaning up this just after rc.sysinit is done.
Hopefully it will work.
vpnc-0.5.1-6.fc9 has been submitted as an update for Fedora 9
vpnc-0.5.1-6.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update vpnc'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-6782
Thank you very much for the work on this one.
Note I'm currently travelling and not in my usual environment, using network manager for wireless.
I have installed your package, and it looks good so far. I am still able to manually connect to the VPN (after having set up the connection with network manager). I tried a reboot (while on VPN) and the resolv.conf got reset to empty.
I can do a test in my usual infrastructure in about a week.
resolv.conf contents should be restored to the contents of /var/run/vpnc/resolv.conf-backup before the reboot happened. Was that file empty?
When I said "it was empty" I meant, it only had some comments, from NetworkManager saying "do not edit", and no nameserver entries. This was because my default setting was to no startup anything automatically after boot. I assume it matched the backup you mentioned.
vpnc-0.5.1-6.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.