WIP Update instructions for VPN automation

assets/openvpn_always_on_setup_guide.md

@@ -125,23 +125,17 @@ Check network interfaces:
 ip a
 ```
 
-Or verify your public IP:
-
-```bash
-curl ifconfig.me
-```
-
-The IP should correspond to the VPN, not your ISP.
+You should see an interface named `tun0` or similar with an IP address starting with `172.24.4.`
 
 ---
 
 ## 8. Behavior Summary
 
-| Event | Result |
-|------|-------|
-| VPN connection drops | Automatically reconnects |
-| VPN server unavailable | Retries indefinitely |
-| Server reboot | VPN reconnects on startup |
+| Event                     | Result                           |
+|---------------------------+----------------------------------|
+| VPN connection drops      | Automatically reconnects         |
+| VPN server unavailable    | Retries indefinitely             |
+| Server reboot             | VPN reconnects on startup        |
 | Network delay during boot | systemd retries until successful |
 
 ---
@@ -154,3 +148,17 @@ The IP should correspond to the VPN, not your ISP.
 
 ---
 
+## Troubleshooting
+
+### Disconnecting Existing VPN Connections
+
+Some users have experienced that connecting to GoodAccess **disconnects an existing VPN or ssh connection**.
+This may happen because OpenVPN is configured to redirect all network traffic through the GoodAccess tunnel, which overrides your local or other VPN routes and may make the machine inaccessible in its local network.
+
+If this occurs, you can prevent the redirection by starting OpenVPN with
+```sh
+openvpn --config <your_config>.ovpn --pull-filter ignore redirect-gateway
+```
+This tells the OpenVPN client **not** to override your default gateway, allowing your other VPN or ssh connection to remain active.
+
+**TODO** describe how this can be configured in when starting the VPN as a system service.

assets/readme/README.participant.md

@@ -11,16 +11,7 @@ This guide is for data scientists and medical research sites participating in a
 ## Setup
 0. Add this line to your `/etc/hosts`: `172.24.4.65 dl3.tud.de dl3`
 1. Make sure your compute node satisfies the specification and has the necessary software installed.
-2. Set up the VPN. A VPN is necessary so that the swarm nodes can communicate with each other securely across firewalls. For that purpose,
-    1. Install OpenVPN
-       ```bash
-       sudo apt-get install openvpn
-       ```
-    2. If you have a graphical user interface(GUI), follow this guide to connect to the
-       VPN: [VPN setup guide(GUI).pdf](../VPN%20setup%20guide%28GUI%29.pdf)
-    3. If you have a command line interface(CLI), follow this guide to connect to the
-       VPN: [VPN setup guide(CLI).md](../VPN%20setup%20guide%28CLI%29.md)
-    4. You may want to clone this repository or selectively download VPN-related scripts for this purpose.
+2. Set up the VPN. A VPN is necessary so that the swarm nodes can communicate with each other securely across firewalls. For that purpose, follow the instructions in [openvpn_always_on_setup_guide.md](../openvpn_always_on_setup_guide.md).
 
 ## Prepare Dataset