I have been having issues trying to connect my Slate AX to PIA WireGuard. I was able to get it to work via a workaround (that I don’t remember how I did) when first starting to beta test; however, I feel that the developers should know about this issue so that it could be fixed to perform the same way that any of the other products work. I have an original Slate, Shadow, Brume-W and Opal. They all connect to PIA fine. They are all on 3.212 vs the Slate AX which is on 4.0.1 beta2 so that could be the issue.
Since PIA does not provide an easy way to download a WireGuard configuration file, I connect all of my devices via the GL.iNet app. With the Slate AX, I get the following in the log:
Thu Jul 21 09:13:25 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Thu Jul 21 09:13:30 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Thu Jul 21 09:13:36 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
And it continues on and on.
It doesn’t look like there is much to decipher from that. Has anyone else had any issues with PIA?
Thanks!