I install pivpn on my raspberry pi 3 and I connect to my pivpn server from remote location over WAN. Maybe someone can explain how pivpn server works. Could someone please tell me why the client failed to connect to the OpenVPN server? Thanks! I expected a connection initiation with the VPN server, but as you can see that is not what occurred. Where 'my-public-ip-address' is my actual publicly displayed IP address. ^CFri Aug 19 15:33:31 2016 event_wait : Interrupted system call (code=4)įri Aug 19 15:33:31 2016 SIGINT received, process exiting RX bytes:14123715 (13.4 MiB) TX bytes:0 (0.0 B)Ĭode: Select all openvpn -config client.ovpnįri Aug 19 15:33:29 2016 Unrecognized option or missing parameter(s) in client.ovpn:14: block-outside-dns (2.3.4)įri Aug 19 15:33:29 2016 OpenVPN 2.3.4 arm-unknown-linux-gnueabihf built on Jan 23 2016įri Aug 19 15:33:29 2016 library versions: OpenSSL 1.0.1t, LZO 2.08įri Aug 19 15:33:29 2016 Control Channel Authentication: tls-auth using INLINE static key fileįri Aug 19 15:33:29 2016 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authenticationįri Aug 19 15:33:29 2016 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authenticationįri Aug 19 15:33:29 2016 Socket Buffers: R= S=įri Aug 19 15:33:29 2016 UDPv4 link local: įri Aug 19 15:33:29 2016 UDPv4 link remote: my-public-ip-address:1194 RX packets:32257 errors:0 dropped:32257 overruns:0 frame:0 Wlan0 Link encap:Ethernet HWaddr b8:27:eb:49:9e:ef TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 TX packets:200 errors:0 dropped:0 overruns:0 carrier:0 RX packets:200 errors:0 dropped:0 overruns:0 frame:0 TX packets:7632 errors:0 dropped:0 overruns:0 carrier:0 RX packets:54391 errors:0 dropped:26996 overruns:0 frame:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Tue Aug 16 18:04:50 2016 SIGINT received, process exitingĮth0 Link encap:Ethernet HWaddr b8:27:eb:1c:cb:ba ^CTue Aug 16 18:04:50 2016 RESOLVE: signal received during DNS resolution attempt
Tue Aug 16 18:04:45 2016 RESOLVE: Cannot resolve host address: : Name or service not known
Tue Aug 16 18:04:40 2016 RESOLVE: Cannot resolve host address: : Name or service not known Tue Aug 16 18:04:40 2016 Control Channel Authentication: tls-auth using INLINE static key file Tue Aug 16 18:04:40 2016 WARNING: this configuration may cache passwords in memory - use the auth-nocache option to prevent this
0 kommentar(er)
