Asus RT-N66U router PIA setup
Greetings.
I have an ASUS RT-N66U router running stock ASUS WRT firmware 3.0.0.4.380_8228.
PIA website support indicates this stock setup is supported. I've followed all directions, pretty simple, but when I
hit "activate" all I get is the spinning wheel, it never connects and activates.
Reading these forums I tried using PIA DNS servers on the router but it didn't change my results. PIA tech support sent a standard response, saying that only certain configurations are supported, but it didn't indicate that ASUS WRT firmware is supported, even though the website indicates it IS supported.
I don't want to fiddle with flashing DD-WRT unless absolutely necessary. PIA support is conflicted, is ASUS WRT firmware supported or not? Has anyone else gotten stock firmware to work?
I'm copying the last bit of my router system log below if it helps. I've tried connecting to the router via cable and wifi both. Any help would be appreciated, thanks!
-Mark C
I have an ASUS RT-N66U router running stock ASUS WRT firmware 3.0.0.4.380_8228.
PIA website support indicates this stock setup is supported. I've followed all directions, pretty simple, but when I
hit "activate" all I get is the spinning wheel, it never connects and activates.
Reading these forums I tried using PIA DNS servers on the router but it didn't change my results. PIA tech support sent a standard response, saying that only certain configurations are supported, but it didn't indicate that ASUS WRT firmware is supported, even though the website indicates it IS supported.
I don't want to fiddle with flashing DD-WRT unless absolutely necessary. PIA support is conflicted, is ASUS WRT firmware supported or not? Has anyone else gotten stock firmware to work?
I'm copying the last bit of my router system log below if it helps. I've tried connecting to the router via cable and wifi both. Any help would be appreciated, thanks!
-Mark C
Apr 12 14:57:14 ddns update: asusddns_update: 0
Apr 12 14:57:14 ddns: ddns update ok
Apr 12 14:57:14 dhcp client: bound 24.33.237.246 via 24.33.236.1 during 78231 seconds.
Apr 12 15:10:33 rc_service: httpd 295:notify_rc restart_vpncall
Apr 12 15:10:34 openvpn[22314]: OpenVPN 2.3.2 mipsel-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [eurephia] [MH] [IPv6] built on Mar 16 2018
Apr 12 15:10:34 openvpn[22320]: UDPv4 link local: [undef]
Apr 12 15:10:34 openvpn[22320]: UDPv4 link remote: [AF_INET]208.167.254.22:502
Apr 12 15:11:34 openvpn[22320]: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Apr 12 15:11:34 openvpn[22320]: TLS Error: TLS handshake failed
Apr 12 15:11:34 openvpn[22320]: SIGUSR1[soft,tls-error] received, process restarting
Apr 12 15:11:36 openvpn[22320]: UDPv4 link local: [undef]
Apr 12 15:11:36 openvpn[22320]: UDPv4 link remote: [AF_INET]208.167.254.48:502
Apr 12 15:12:18 rc_service: httpd 295:notify_rc restart_vpncall
Apr 12 15:12:18 openvpn[22320]: event_wait : Interrupted system call (code=4)
Apr 12 15:12:18 openvpn[22320]: SIGTERM[hard,] received, process exiting
Comments
From your log, it looks like you're connecting over TCP port 502. We don't offer configuration files with an embedded cert for that particular port on our site, so my guess is that you don't have a cert in your config, which is why your connection is being rejected by our servers. You can either upload the correct cert or enter it manually by clicking the
Import the CA file or edit the .ovpn file manuallyoption in the OpenVPN client settings, like so:I also replied via e-mail, thanks. I'm posting here as well in the interest of supporting others that may have the same issue. The 4 or 5 OVPN files I downloaded from the guide all connect via TCP port 502 and have certificates embedded within.
I also tried an OVPN file without the certificate embedded and used another CA file from support. It did connect but I could not access web pages due to DNS failure. I tried the CA file that connects via IP address instead of server name and had the same result.