Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update vpn-troubleshooting.md

Browse Source
This commit is contained in:
Enjeck Cleopatra 2020-11-01 14:50:05 +01:00 committed by GitHub
parent c23fe80a4b
commit cf04fba222
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
user/troubleshooting/vpn-troubleshooting.md
View File

@ -8,7 +8,7 @@ permalink: /doc/vpn-troubleshooting/
## Tips ## Tips
* Check the VPN service's log in the VPN VM by running: * If using qubes-vpn, check the VPN service's log in the VPN VM by running:
~~~ ~~~
sudo journalctl -u qubes-vpn-handler sudo journalctl -u qubes-vpn-handler
~~~ ~~~
@ -19,10 +19,13 @@ permalink: /doc/vpn-troubleshooting/
* Use `iptables -L -v` and `iptables -L -v -t nat` to check firewall rules. The latter shows the critical PR-QBS chain that enables DNS forwarding. * Use `iptables -L -v` and `iptables -L -v -t nat` to check firewall rules. The latter shows the critical PR-QBS chain that enables DNS forwarding.
## VPN does not reconnect after suspend ## VPN does not reconnect after suspend
After suspend/resume, your VPN may not automatically reconnect. In order to get it to work, you must kill your VPN system and restart it.
This applies when using OpenVPN.
After suspend/resume, OpenVPN may not automatically reconnect. In order to get it to work, you must kill the OpenVPN process and restart it.
## VPN stuck at "Ready to start link" ## VPN stuck at "Ready to start link"
After setting up your VPN system and restarting the VM, you may be repeatedly getting the popup "Ready to start link", but the VPN isn't connected. After setting up OpenVPN and restarting the VM, you may be repeatedly getting the popup "Ready to start link", but the VPN isn't connected.
To figure out the root of the problem, check the VPN logs in `/var/logs/syslog`. The log may reveal issues like missing libraries, which you can then install. To figure out the root of the problem, check the VPN logs in `/var/logs/syslog`. The log may reveal issues like missing OpenVPN libraries, which you can then install.