Problems with resolv.conf on hard crash.
My machine had a hard crash last night. When I rebooted, the resolv.conf was still the one set by leap. But because my EIP was not actually started, I could not access the net, either on or off the EIP. Attempting to start EIP also failed for the same reason. I manually edited resolv.conf to fix the problem.
I think the solution is for eip to check resolv.conf on startup to see if it is in a sane state, and if not, fix it.
In the long term, it would be good for this to happen on boot (i.e. without having to start the client). A simple boottime script that checks the resolv.conf to make sure it is in a sane state would work great.
FYI, this is on the 0.3.7 client 64bits.
(from redmine: created on 2013-12-02, closed on 2014-07-10, relates #4585 (closed), relates #4823 (closed), relates #5738 (closed), relates #5655 (closed))