You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,15 +93,15 @@ Set a Hub or HaaS up first, so you can generate the necessary peer configuration
93
93
94
94
### Maintenance
95
95
96
-
You can (re)configure WireGuard peers (on bare metal as well, thanks to code shared by [LinuxServer.io](https://github.com/linuxserver/docker-wireguard)):
96
+
You can (re)configure WireGuard peers (on bare metal as well, thanks to code shared by [LinuxServer.io](https://github.com/linuxserver/docker-wireguard)). Add WireGuard peers or modify the AllowedIPs of existing ones, show peer config QR codes, and delete peers with:
97
97
98
-
- Add WireGuard peers, or modify the AllowedIPs of existing ones, with `sudo bash wireguard/add.sh <peer_name> [option]`.
99
-
- Show peer config QR codes with `sudo bash wireguard/get.sh <peer_name>`.
100
-
- Delete peers with `sudo bash wireguard/del.sh <peer_name>`.
101
-
102
-
To complete adding a SaaH, create an `SERVER_ALLOWEDIPS_PEER_[SaaH]=` environment variable -- using the peer's name sans the brackets -- for the WireGuard service with the difference of `0.0.0.0/1,128.0.0.0/1,::/1,8000::/1` and the peer's IP. This [AllowedIPs Calculator](https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator) is pretty nifty.
98
+
```{bash}
99
+
sudo bash wireguard/add.sh <peer_name> [option]
100
+
sudo bash wireguard/get.sh <peer_name>
101
+
sudo bash wireguard/del.sh <peer_name>
102
+
```
103
103
104
-
Complete the above or any other CUD operation by running `sudo bash restart.sh`. By default, `add.sh` sets the peer to route outgoing traffic through the VPN. You can change this default by modifying AllowedIPs in `compose.yml`. The option it takes may be one of:
104
+
By default, `add.sh` sets the peer to route outgoing traffic through the VPN. You can change this default by modifying AllowedIPs in `compose.yml`. The option it takes may be one of:
105
105
106
106
```{bash}
107
107
-e, --internet Route all traffic through the VPN
@@ -110,6 +110,8 @@ Complete the above or any other CUD operation by running `sudo bash restart.sh`.
110
110
-o, --outgoing Route outgoing traffic through the VPN
111
111
```
112
112
113
+
After running `add.sh` on a HaaS to create its SaaH peer, create an `SERVER_ALLOWEDIPS_PEER_[SaaH]` environment variable -- using the peer's name sans the brackets -- for the WireGuard service with the difference of `0.0.0.0/1,128.0.0.0/1,::/1,8000::/1` and the peer's IP. This [AllowedIPs Calculator](https://www.procustodibus.com/blog/2021/03/wireguard-allowedips-calculator) is pretty nifty.
114
+
113
115
> [!NOTE]
114
116
> While `start.sh` brings everything up, `restart.sh` only restarts WireGuard unless you first export `CLS_WG_ONLY=false`.
0 commit comments