I've seen the nak UI saying that it was currently connected to a wired connection, when in fact it hadn't been for several hours. this was after (deliberately) telling it to connect to a wireless network with an incorrect password.
meanwhile, the VPN connection shows as connected, despite the fact that it wasn't (since no internet connection was available). here are the logs at the time:
Fri Mar 11 06:44:02 2016 UDPv4 link remote: [AF_INET]81.xxx.xxx.188:1194
Fri Mar 11 06:45:02 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Fri Mar 11 06:45:02 2016 TLS Error: TLS handshake failed
Fri Mar 11 06:45:02 2016 SIGUSR1[soft,tls-error] received, process restarting
Fri Mar 11 06:45:04 2016 UDPv4 link local: [undef]
Fri Mar 11 06:45:04 2016 UDPv4 link remote: [AF_INET]81.xxx.xxx.188:1194
Fri Mar 11 06:46:04 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Fri Mar 11 06:46:04 2016 TLS Error: TLS handshake failed
Fri Mar 11 06:46:04 2016 SIGUSR1[soft,tls-error] received, process restarting
(repeats as above)
I've seen the nak UI saying that it was currently connected to a wired connection, when in fact it hadn't been for several hours. this was after (deliberately) telling it to connect to a wireless network with an incorrect password.
screenshot: http://s7.postimg.org/tjbm5n2jf/Screenshot_from_2016_03_11_06_51_46.png
meanwhile, the VPN connection shows as connected, despite the fact that it wasn't (since no internet connection was available). here are the logs at the time: