Repository navigation
GHOSTWIRE v0.10.2
Fixes for taking over pivpn and for peers without DNS.
Changes
- Password first.
install -yreads the admin password from standard input before it changes anything. Without one, or with one that is too short, it stops and the server stays as it was. Before, a pivpn takeover without a password stopped halfway and left a config behind. - Never next to pivpn. Install refuses to run while pivpn's WireGuard (
wg-quick@wg0) is running or enabled, for example after going back to pivpn, and says how to go on. A takeover that fails before pivpn is stopped removes its config again. - pivpn's NAT rules. The takeover removes pivpn's NAT rules (iptables-persistent or ufw) and comments them out for the next boot, so the NAT setting in GHOSTWIRE now decides. Before, peers still reached the internet with NAT switched off. A failed takeover and
GHOSTWIRE uninstallput the rules back. - No DNS for a peer. A peer set to no DNS (
"dns": []) keeps that setting. Before, it was saved as the server default and the config got the server's DNS servers. Empty AllowedIPs are refused.
Update
Copy the binary for your server to it and run, as root:
chmod +x GHOSTWIRE-v0.10.2-linux-amd64
sudo ./GHOSTWIRE-v0.10.2-linux-amd64 updateServers on v0.10.0 or later show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.
On a server that took over pivpn with an earlier version, pivpn's NAT rules are still there. To remove them, run sudo /opt/ghostwire/GHOSTWIRE install -y once after the update; it keeps all settings and restarts the service.
Files
| File | For |
|---|---|
GHOSTWIRE-v0.10.2-linux-amd64 |
64-bit x86 servers |
GHOSTWIRE-v0.10.2-linux-arm64 |
64-bit ARM, e.g. Raspberry Pi OS 64-bit |
GHOSTWIRE-v0.10.2-linux-armv7 |
Raspberry Pi OS 32-bit |
SHA256SUMS |
checksums: shasum -a 256 -c SHA256SUMS |