Ξ welcome to cryptostorm's member forums ~ you don't have to be a cryptostorm member to post here Ξ ∞ take a peek at our legendary cryptostorm_is twitter feed if you're into that kind of thing ∞ Ξ we're rolling out voodoo network security across cryptostorm - big things happening, indeed! Ξ Ξ any OpenVPN configs found on the forum are likely outdated. For the latest, visit GitHub Ξ
Looking for assistance with a cryptostorm connection issue? Post here & we'll help out. Also: if you're not sure where to post, do so here & we'll move things around as needed. Also: for quickest support, email our oddly calm & easygoing support reps at [email protected]
Platform My workstation is running Mint 17.1 KDE, with OpenVPN 2.3.2.
This is something I've noticed recently (mostly while connected to Turing). After a couple of days, the session seems to turn "stale", and the DNS resolvers become either unavailable or simply don't resolve anything, not even Google. My connection is intended to be up 24/7, since my computer is also up 24/7. Killing and then restarting the VPN session cures the problem.
I can't remember exactly, but is definitely been happening sporadically over the last four weeks. What I will say is that it only appears to be happening on Turing (I have a VM which spends most of its life connected to Cantus, but it does not appear to be suffering this issue).
The logs don't show anything untoward, and the VPN does not appear to disconnect. I'm now wondering if it's a bug in dnsmasq...the next time it happens I'll try to grab some pcaps.