Wifi disconnects for a couple of seconds at random, throws off OpenVPN

linkandzelda · 2018-11-24 13:18:53

I loaded Arch on my laptop (Dell XPS 9370) about a month ago. At the same time I loaded an OpenVPN profile on it. I noticed that at random OpenVPN would disconnect and would fail to reconnect, resulting in the system going offline for about 300 seconds. The reconnect timer of 60s would fail to establish a handshake, leaving it to try again after 300 seconds. But whenever the net goes down I just restart openvpn manually and its back up and connected immediately, although this is an annoying fix. For the record this VPN profile does not have any problems on another machine,

At first I thought this was some kind of idle thing letting the wifi disconnect, and it might be, because power management is enabled and I'm not sure how to disable it. Either way this is the result of my findings so far and I am not sure how to proceed.

The status of "netctl-auto@wlp2s0" reports this when the issue happens. I obscured the name of the network:

Nov 23 17:48:09 xps wpa_actiond[426]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 23 17:48:14 xps wpa_actiond[426]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'

I've looked back and this is very common, here's a few more instances of when it disconnected:

Nov 01 08:49:44 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 01 08:49:49 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 01 10:06:37 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 01 10:06:42 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 02 15:14:59 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 02 15:15:04 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 02 21:19:53 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 02 21:19:58 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 02 21:20:29 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 02 21:20:35 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 03 15:29:11 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 03 15:29:16 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 04 13:55:12 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 04 13:55:17 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 05 10:16:01 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 05 10:16:06 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 06 09:38:01 xps wpa_actiond[431]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 06 09:38:06 xps wpa_actiond[431]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 06 18:44:36 xps wpa_actiond[431]: Interface 'wlp2s0' disconnected from network 'NETWORK'
Nov 06 18:45:08 xps wpa_actiond[448]: Interface 'wlp2s0' connected to network 'NETWORK'
Nov 07 08:42:42 xps wpa_actiond[448]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 07 08:42:47 xps wpa_actiond[448]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 07 14:20:01 xps wpa_actiond[448]: Interface 'wlp2s0' disconnected from network 'NETWORK'
Nov 07 14:47:07 xps wpa_actiond[443]: Interface 'wlp2s0' connected to network 'NETWORK'
Nov 07 14:49:41 xps wpa_actiond[443]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 07 14:49:46 xps wpa_actiond[443]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 07 15:35:51 xps wpa_actiond[443]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 07 15:35:56 xps wpa_actiond[443]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 08 09:56:32 xps wpa_actiond[443]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 08 09:56:37 xps wpa_actiond[443]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 09 10:10:21 xps wpa_actiond[443]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 09 10:10:26 xps wpa_actiond[443]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 09 19:39:52 xps wpa_actiond[443]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 09 19:39:57 xps wpa_actiond[443]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 10 19:34:34 xps wpa_actiond[443]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 10 19:34:39 xps wpa_actiond[443]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 11 12:27:29 xps wpa_actiond[454]: Interface 'wlp2s0' connected to network 'NETWORK'
Nov 12 10:00:56 xps wpa_actiond[454]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 12 10:01:01 xps wpa_actiond[454]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 12 15:22:49 xps wpa_actiond[454]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 12 15:22:54 xps wpa_actiond[454]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 13 10:08:13 xps wpa_actiond[454]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 13 10:08:18 xps wpa_actiond[454]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 14 10:07:13 xps wpa_actiond[448]: Interface 'wlp2s0' connected to network 'NETWORK'
Nov 15 14:07:11 xps wpa_actiond[448]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 15 14:07:16 xps wpa_actiond[448]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 16 09:59:26 xps wpa_actiond[448]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 16 09:59:31 xps wpa_actiond[448]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 17 09:36:06 xps wpa_actiond[448]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 17 09:36:11 xps wpa_actiond[448]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 18 10:13:56 xps wpa_actiond[448]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 18 10:14:01 xps wpa_actiond[448]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 19 09:22:50 xps wpa_actiond[448]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 19 09:22:55 xps wpa_actiond[448]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 20 19:54:37 xps wpa_actiond[448]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 20 19:54:42 xps wpa_actiond[448]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 21 10:16:30 xps wpa_actiond[448]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 21 10:16:35 xps wpa_actiond[448]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 21 10:28:49 xps wpa_actiond[448]: Interface 'wlp2s0' disconnected from network 'NETWORK'
Nov 21 10:29:30 xps wpa_actiond[426]: Interface 'wlp2s0' connected to network 'NETWORK'
Nov 23 17:48:09 xps wpa_actiond[426]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 23 17:48:14 xps wpa_actiond[426]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'
Nov 23 17:54:02 xps wpa_actiond[426]: Interface 'wlp2s0' disconnected from network 'NETWORK'
Nov 23 17:54:09 xps wpa_actiond[24976]: Interface 'wlp2s0' connected to network 'NETWORK'
Nov 23 17:58:51 xps wpa_actiond[24976]: Interface 'wlp2s0' disconnected from network 'NETWORK'
Nov 23 17:58:58 xps wpa_actiond[25989]: Interface 'wlp2s0' connected to network 'NETWORK'
Nov 24 09:39:16 xps wpa_actiond[25989]: Interface 'wlp2s0' lost connection to network 'NETWORK'
Nov 24 09:39:21 xps wpa_actiond[25989]: Interface 'wlp2s0' reestablished connection to network 'NETWORK'

As for the strength of the network, I am about 10-15 feet from the router so it should not be struggling, and it is a 5G network. When it's connected it works fine.
I'm not sure how to proceed in identifying what causes this behaviour?

ewaller · 2018-11-24 16:09:32

What are the output of find /etc/systemd ?

linkandzelda · 2018-11-24 16:13:33

ewaller wrote:

What are the output of find /etc/systemd ?

Here is the output:

% find /etc/systemd  
/etc/systemd
/etc/systemd/system.conf
/etc/systemd/user.conf
/etc/systemd/journal-remote.conf
/etc/systemd/system
/etc/systemd/system/sockets.target.wants
/etc/systemd/system/sockets.target.wants/sshd.socket
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/openvpn-client@xps13.service
/etc/systemd/system/multi-user.target.wants/netctl-auto@wlp2s0.service
/etc/systemd/system/multi-user.target.wants/plexmediaserver.service
/etc/systemd/system/transmission.service.d
/etc/systemd/system/transmission.service.d/username.conf
/etc/systemd/system/plexmediaserver.service.d
/etc/systemd/system/plexmediaserver.service.d/override.conf
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/display-manager.service
/etc/systemd/resolved.conf
/etc/systemd/journal-upload.conf
/etc/systemd/logind.conf
/etc/systemd/journald.conf
/etc/systemd/user
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/gpg-agent.socket
/etc/systemd/user/sockets.target.wants/dirmngr.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-browser.socket
/etc/systemd/user/sockets.target.wants/pulseaudio.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-extra.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-ssh.socket
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/network
/etc/systemd/timesyncd.conf
/etc/systemd/coredump.conf

ewaller · 2018-11-24 16:23:11

That looks okay. I was looking for multiple things trying to control the wireless; I don't see any conflicts.

What is the wifi chipset?
Do you have access to the router logs?

Oh, and welcome to the Arch Linux forums

linkandzelda · 2018-11-24 16:29:12

ewaller wrote:

That looks okay. I was looking for multiple things trying to control the wireless; I don't see any conflicts.
What is the wifi chipset?
Do you have access to the router logs?
Oh, and welcome to the Arch Linux forums

Thanks for the welcome!

lspci lists the card as below:

02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

I own the router, but the funny thing is that I forgot the logins for the admin panel so I can't check the logs.

seth · 2018-11-24 16:43:16

Consumer routers have reset buttons, time to invoke it.
Please post a complete journal/dmesg for the incident ("context")

Could be some power saving, do you use any daemons?

linkandzelda · 2018-11-24 17:03:38

The router log does not show much, it's mostly filled with the below:

109	Nov 24 09:59:59	DHCP	INFO	DHCPS:Recv DISCOVER from 9C:B6:D0:8D:F7:C9
108	Nov 24 09:59:59	DHCP	INFO	DHCPS:Send NAK
107	Nov 24 09:59:59	DHCP	INFO	DHCPS:Recv REQUEST from 9C:B6:D0:8D:F7:C9
106	Nov 24 09:51:08	DHCP	INFO	DHCPS:Send ACK to 192.168.0.103
105	Nov 24 09:51:08	DHCP	INFO	DHCPS:Recv REQUEST from C0:48:E6:30:02:C3
104	Nov 24 09:51:08	DHCP	INFO	DHCPS:Send OFFER with ip 192.168.0.103
103	Nov 24 09:51:08	DHCP	INFO	DHCPS:Recv DISCOVER from C0:48:E6:30:02:C3
102	Nov 24 09:51:08	DHCP	INFO	DHCPS:Send OFFER with ip 192.168.0.103
101	Nov 24 09:51:07	DHCP	INFO	DHCPS:Recv DISCOVER from C0:48:E6:30:02:C3
100	Nov 24 09:36:23	DHCP	INFO	DHCPS:Send ACK to 192.168.0.100
99	Nov 24 09:36:23	DHCP	INFO	DHCPS:Recv REQUEST from D8:5B:2A:37:32:83
98	Nov 24 09:36:12	DHCP	INFO	DHCPS:Send ACK to 192.168.0.101
97	Nov 24 09:36:12	DHCP	INFO	DHCPS:Recv REQUEST from D0:22:BE:27:16:B1

This is around 9:39 am when it happened today. The laptop's mac is 9C:B6:D0:8D:F7:C9 so no logs at the time of disconnect. This is showing logs of type ALL with filter ALL.

I'm not running any power management daemons as far as I know, the only power management things I did was something for intel video.

Here's some output which might be useful?

% dmesg -T | grep wlp2s0
[Fri Nov 23 17:54:03 2018] audit: type=1130 audit(1542995644.760:78): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl-auto@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fri Nov 23 17:54:07 2018] wlp2s0: authenticate with c0:4a:00:e4:61:9a
[Fri Nov 23 17:54:07 2018] wlp2s0: send auth to c0:4a:00:e4:61:9a (try 1/3)
[Fri Nov 23 17:54:07 2018] wlp2s0: authenticated
[Fri Nov 23 17:54:07 2018] wlp2s0: associate with c0:4a:00:e4:61:9a (try 1/3)
[Fri Nov 23 17:54:07 2018] wlp2s0: RX AssocResp from c0:4a:00:e4:61:9a (capab=0x411 status=0 aid=4)
[Fri Nov 23 17:54:07 2018] wlp2s0: associated
[Fri Nov 23 17:54:07 2018] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[Fri Nov 23 17:54:08 2018] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by c0:4a:00:e4:61:9a
[Fri Nov 23 17:58:50 2018] wlp2s0: deauthenticating from c0:4a:00:e4:61:9a by local choice (Reason: 3=DEAUTH_LEAVING)
[Fri Nov 23 17:58:50 2018] audit: type=1131 audit(1542995932.590:79): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl-auto@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fri Nov 23 17:58:51 2018] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[Fri Nov 23 17:58:51 2018] audit: type=1130 audit(1542995933.440:80): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl-auto@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fri Nov 23 17:58:56 2018] wlp2s0: authenticate with c0:4a:00:e4:61:9a
[Fri Nov 23 17:58:56 2018] wlp2s0: send auth to c0:4a:00:e4:61:9a (try 1/3)
[Fri Nov 23 17:58:56 2018] wlp2s0: authenticated
[Fri Nov 23 17:58:56 2018] wlp2s0: associate with c0:4a:00:e4:61:9a (try 1/3)
[Fri Nov 23 17:58:56 2018] wlp2s0: RX AssocResp from c0:4a:00:e4:61:9a (capab=0x411 status=0 aid=4)
[Fri Nov 23 17:58:56 2018] wlp2s0: associated
[Fri Nov 23 17:58:56 2018] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[Fri Nov 23 17:58:56 2018] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by c0:4a:00:e4:61:9a
[Fri Nov 23 22:38:10 2018] wlp2s0: deauthenticating from c0:4a:00:e4:61:9a by local choice (Reason: 3=DEAUTH_LEAVING)
[Sat Nov 24 09:39:19 2018] wlp2s0: authenticate with c0:4a:00:e4:61:9a
[Sat Nov 24 09:39:19 2018] wlp2s0: send auth to c0:4a:00:e4:61:9a (try 1/3)
[Sat Nov 24 09:39:19 2018] wlp2s0: authenticated
[Sat Nov 24 09:39:19 2018] wlp2s0: associate with c0:4a:00:e4:61:9a (try 1/3)
[Sat Nov 24 09:39:19 2018] wlp2s0: RX AssocResp from c0:4a:00:e4:61:9a (capab=0x411 status=0 aid=5)
[Sat Nov 24 09:39:19 2018] wlp2s0: associated
[Sat Nov 24 09:39:19 2018] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by c0:4a:00:e4:61:9a

seth · 2018-11-24 18:02:17

seth wrote:

a complete journal/dmesg for the incident ("context")

We can't eg. see what the kernel module is doing and a disconnect at 9:39 isn't even recorded, the suspicious fraction is

[Fri Nov 23 17:54:07 2018] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[Fri Nov 23 17:54:08 2018] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by c0:4a:00:e4:61:9a
[Fri Nov 23 17:58:50 2018] wlp2s0: deauthenticating from c0:4a:00:e4:61:9a by local choice (Reason: 3=DEAUTH_LEAVING)
[Fri Nov 23 17:58:56 2018] wlp2s0: authenticate with c0:4a:00:e4:61:9a

linkandzelda · 2018-11-24 18:36:32

seth wrote:

seth wrote:
a complete journal/dmesg for the incident ("context")
We can't eg. see what the kernel module is doing and a disconnect at 9:39 isn't even recorded, the suspicious fraction is
[Fri Nov 23 17:54:07 2018] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[Fri Nov 23 17:54:08 2018] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by c0:4a:00:e4:61:9a
[Fri Nov 23 17:58:50 2018] wlp2s0: deauthenticating from c0:4a:00:e4:61:9a by local choice (Reason: 3=DEAUTH_LEAVING)
[Fri Nov 23 17:58:56 2018] wlp2s0: authenticate with c0:4a:00:e4:61:9a

Could you tell me how to get those logs and I will post them. My log finding knowledge is limited.

seth · 2018-11-24 21:01:25

"sudo journalctl -b" (from a boot where this happened), you can use https://wiki.archlinux.org/index.php/Li … in_clients to upload it.

linkandzelda · 2018-11-24 23:08:19

seth wrote:

"sudo journalctl -b" (from a boot where this happened), you can use https://wiki.archlinux.org/index.php/Li … in_clients to upload it.

That command was quite useful. I won't post it's results now because there's too much sensitive info like VPN ip, mail sync service results, which I need to obscure. However it taught me this from this small snippet:

Nov 24 09:39:24 xps openvpn[26002]: Initialization Sequence Completed
Nov 24 09:55:21 xps dhcpcd[26022]: wlp2s0: hardware address 7c:bb:8a:ed:ed:e2 claims 192.168.0.102
Nov 24 09:55:26 xps dhcpcd[26022]: wlp2s0: hardware address 7c:bb:8a:ed:ed:e2 claims 192.168.0.102
Nov 24 10:00:06 xps dhcpcd[26022]: wlp2s0: NAK: from 192.168.0.1
Nov 24 10:00:07 xps dhcpcd[26022]: wlp2s0: deleting route to 192.168.0.0/24
Nov 24 10:00:07 xps dhcpcd[26022]: wlp2s0: deleting default route via 192.168.0.1
Nov 24 10:00:07 xps dhcpcd[26022]: wlp2s0: soliciting a DHCP lease
Nov 24 10:00:08 xps dhcpcd[26022]: wlp2s0: offered 192.168.0.104 from 192.168.0.1
Nov 24 10:00:08 xps dhcpcd[26022]: wlp2s0: probing address 192.168.0.104/24
Nov 24 10:00:13 xps dhcpcd[26022]: wlp2s0: leased 192.168.0.104 for 7200 seconds
Nov 24 10:00:13 xps dhcpcd[26022]: wlp2s0: adding route to 192.168.0.0/24
Nov 24 10:00:13 xps dhcpcd[26022]: wlp2s0: adding default route via 192.168.0.1
Nov 24 10:02:05 xps openvpn[26002]: [server] Inactivity timeout (--ping-restart), restarting
Nov 24 10:02:05 xps openvpn[26002]: SIGUSR1[soft,ping-restart] received, process restarting
Nov 24 10:02:05 xps openvpn[26002]: Restart pause, 5 second(s)
Nov 24 10:02:10 xps openvpn[26002]: TCP/UDP: Preserving recently used remote address: [AF_INET]VPN.OBSCURED.IP:PORT
Nov 24 10:02:10 xps openvpn[26002]: Socket Buffers: R=[212992->212992] S=[212992->212992]
Nov 24 10:02:10 xps openvpn[26002]: UDP link local: (not bound)
Nov 24 10:02:10 xps openvpn[26002]: UDP link remote: [AF_INET]2VPN.OBSCURED.IP:PORT
Nov 24 10:03:10 xps openvpn[26002]: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Nov 24 10:03:10 xps openvpn[26002]: TLS Error: TLS handshake failed
Nov 24 10:03:10 xps openvpn[26002]: SIGUSR1[soft,tls-error] received, process restarting
Nov 24 10:03:10 xps openvpn[26002]: Restart pause, 5 second(s)

This point I was afk and the above repeats for the whole time until you can see when I came back I restarted openvpn, fixing the issue:

Nov 24 10:11:49 xps sudo[17582]:      laz : TTY=pts/19 ; PWD=/home/laz ; USER=root ; COMMAND=/usr/bin/systemctl restart openvpn-client@xps13
Nov 24 10:11:49 xps sudo[17582]: pam_unix(sudo:session): session opened for user root by laz(uid=0)
Nov 24 10:11:49 xps systemd[1]: Stopping OpenVPN tunnel for xps13...

I think this gave me a new angle to explore, thanks.

Last edited by linkandzelda (2018-11-24 23:09:39)

Arch Linux

#1 2018-11-24 13:18:53

Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#2 2018-11-24 16:09:32

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#3 2018-11-24 16:13:33

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#4 2018-11-24 16:23:11

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#5 2018-11-24 16:29:12

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#6 2018-11-24 16:43:16

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#7 2018-11-24 17:03:38

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#8 2018-11-24 18:02:17

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#9 2018-11-24 18:36:32

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#10 2018-11-24 21:01:25

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

#11 2018-11-24 23:08:19

Re: Wifi disconnects for a couple of seconds at random, throws off OpenVPN

Board footer