Despite the update to 2.4.0-6, I'm still experiencing the same issue as before.
The only information could find are from these errors from the syslog. It took approximately 15-20 minutes for the display to shut off for power saving (19:57), based off of the first error message. May 23 20:15:35 $hostname kernel: [ 1399.479807] perf: interrupt took too long (2515 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 May 23 20:25:26 $hostname kernel: [ 1989.911138] perf: interrupt took too long (3145 > 3143), lowering kernel.perf_event_max_sample_rate to 63500 May 23 20:34:46 $hostname wpa_supplicant[639]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN May 23 20:34:47 $hostname wpa_supplicant[639]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE May 23 20:34:47 $hostname wpa_supplicant[639]: dbus: Failed to construct signal May 23 20:38:03 $hostname kernel: [ 2747.578044] perf: interrupt took too long (3936 > 3931), lowering kernel.perf_event_max_sample_rate to 50750 May 23 20:53:10 $hostname nm-openvpn[1242]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1602', remote='link-mtu 1634' May 23 20:53:10 $hostname nm-openvpn[1242]: WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1532' May 23 20:56:46 $hostname wpa_supplicant[639]: nl80211: send_and_recv->nl_recvmsgs failed: -33 The final message is due to the ping I used to test the connection. Regards, Prescott -------- Original Message -------- Subject: Re: Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect Local Time: May 22, 2017 8:58 AM UTC Time: May 22, 2017 1:58 PM From: a...@inittab.org To: Prescott <presc...@hidalgo-monroy.com>, 863...@bugs.debian.org Debian Bug Tracking System <sub...@bugs.debian.org> On Sun, May 21, 2017 at 06:40:31PM -0500, Prescott wrote: > Package: openvpn > Version: 2.4.0-5 > Severity: important > > Dear Maintainer, > > After the upgrade to openvpn 2.4.0-5 (from *-4), an issue has been > occuring where after having been connected to the VPN for an > approximate amount of time of around 30-45 minutes, the network > connection will drop. NetworkManager continues to state that the VPN > is currently active, but no network is reachable. The only way to > restart the VPN network is to bring the connection up again. > > As stated before, I am using openvpn through NetworkManger, and use > nmcli with a configured VPN config file and a separate password file from a > paid service I > subscribe to. > Hi, Could you try 2.4.0-6 just uploaded to unstable? It fixes an issue that matches your symptoms. Regards, Alberto -- Alberto Gonzalez Iniesta | Formación, consultoría y soporte técnico mailto/sip: a...@inittab.org | en GNU/Linux y software libre Encrypted mail preferred | http://inittab.com Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D 4BF2 009B 3375 6B9A AA55
