lukn555 wrote: > Sorry for the late reply, I suffered the same but I only just found out > how to fix this: I am glad you have something that works for you. However I read this and it feels like a workaround for a deeper problem. I applaud you sharing your solution with us. Thank you for doing that. But it should not be needed. > $ cat /lib/systemd/system-sleep/openvpn.sh >... > /bin/systemctl restart openvpn > $ cat /etc/pm/sleep.d/99openvpn >... > /etc/init.d/openvpn restart Basically restart openvpn after suspending. For both init systems. That is a big hammer. My question would be why that is needed. Openvpn will periodically test connectivity. After suspend the clock time will have expired and openvpn will probe connectivity. This will cause openvpn to restart the connection itself. That is what it does in my examination of the behavior on my laptops. I use openvpn all of the time on my laptops. I don't need to restart it specially when resuming from suspend. There are still some open questions about the nature of the failure. Such as whether the failure is actually networking related or DNS related. If one can ping by address then openvpn itself has successfully created a network connection. If it is DNS related then there is a different tree of questions to work down through. Bob
Attachment:
signature.asc
Description: Digital signature