As for the NAT-rules part of the howto, I doubled all the rules while setting the VPN as interface as instructed. Should I disable IPv6 on pfSense? Since PIA doesn't seem to support it. Current IP Address: //' -e 's/<.$//'Ĭurl ipinfo.io/ip Both show an IP-address that's not my public IPv4-address issued by my ISP, nor the private address issued by my router to pfSense's WAN-interface, so I guess its working :)
I solved that by changing the port from 1194 to 1198 and the encryption algorithm from BF-CBC (128-bit) to AES-128-CBC (for standard certificates), see for more info.Īfter that, the VPN showed as "up", so I accessed pfSense's console and ran both```Ĭurl -s | sed -e 's/.
Private internet access loading plus#
Plus option "Auth digest algorithm" is not listed in the howto, I left the default setting as it was, SHA1 (160-bit)Īfter finishing following the howto, I ended up with "reconnecting tls-error" as status and this in the log:Īug 30 14:25:40 openvpn 26470 TLS: Initial packet from 46.166.137.250:1194, sid=95cdf14a 8a04e2c6Īug 30 14:25:40 openvpn 26470 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, 30 14:25:40 openvpn 26470 OpenSSL: error:14090086:SSL routines:SS元_GET_SERVER_CERTIFICATE:certificate verify failedĪug 30 14:25:40 openvpn 26470 TLS_ERROR: BIO read tls_read_plaintext errorĪug 30 14:25:40 openvpn 26470 TLS Error: TLS object -> incoming plaintext read errorĪug 30 14:25:40 openvpn 26470 TLS Error: TLS handshake failedĪug 30 14:25:40 openvpn 26470 TCP/UDP: Closing socketĪug 30 14:25:40 openvpn 26470 SIGUSR1 received, process restartingĪug 30 14:25:40 openvpn 26470 Restart pause, 2 second(s) Not sure if it's the right choice though… I got a bit confused at the compression setting, there is nothing to check, instead there's a drop down menu with 5 options, I set it to "enabled with adaptive compression".
Private internet access loading Pc#
Since I do not want all traffic to go through VPN, just one or two specific programs, I figured I'd set up a virtual pc with pfSense and Squid and set the programs in question to connect to Squid so that the traffic goes through pfSense and it's VPN client. Just now I went through this howto to set up a virtualized pfSense as VPN client. PIA VPN works it's the 'bypass' exception that does not. PIAVPN_VPNV6 / WAN / / / Interface PIAVPN_VPNV4ĭeleted: OPT2 I appreciate the detail of the original PIA VPN tutorial and all of the subsequent contributions, I've not been able to combine all of that into a working VPN + Bypass configuration. Run the entire local 192.168.1.X net through the PIA VPN - except a few specific static IP devices. All IPs for devices are static IPs on the same 192.168.1.X network but they all just use the tunnel.Īny idea of what to observe or what config to check or change would be appreciated.
I've read, searched and tried every config modification I can find no luck. I've successfully configured PIA VPN and confirms a PIA IP address but something is preventing any Firewall exception Rule I create (to 'bypass' VPN) from having those IP routed around VPN – such rules appear to be just ignored. While I appreciate the detail of the original PIA VPN tutorial and all of the subsequent contributions, I've not been able to combine all of that into a working VPN + Bypass configuration. I see the same "Management" things anyways with or without some of the above advanced options. Oct 18 01:25:58 openvpn 13031 MANAGEMENT: Client disconnected Oct 18 01:25:58 openvpn 13031 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock Oct 18 01:25:51 openvpn 13031 MANAGEMENT: Client disconnected Oct 18 01:25:51 openvpn 13031 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock Oct 18 01:25:46 openvpn 13031 MANAGEMENT: Client disconnected I'm able to connect just fine to PIA, but I'm seeing this in the logs every 10-15 seconds or so.
0 kommentar(er)
