Skip to content
This repository has been archived by the owner on Jul 23, 2021. It is now read-only.

UI sometimes incorrectly reports connected to Wired connection (and connected to VPN) #87

Open
hjwp opened this issue Mar 11, 2016 · 0 comments

Comments

@hjwp
Copy link

hjwp commented Mar 11, 2016

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:

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)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant