-
GHOSTWIRE v0.3.2 Stable
released this
2026-10-04 21:14:51 +00:00 | 3 commits to main since this releaseA small fix for servers that get IPv6 automatically from their router.
Changes
- IPv6 keeps working with forwarding on: to route VPN traffic, GHOSTWIRE turns on IPv6 forwarding, and Linux then ignores the router's announcements. A server that gets its IPv6 address and route that way (SLAAC, e.g. a Raspberry Pi at home) lost its IPv6 connection after a reboot or when the route expired.
installandupdatenow setaccept_ra=2on the network cards and the IPv6 uplink, as pivpn does, so the server keeps listening to the router. Interfaces where router announcements are switched off (accept_ra=0) are left alone. - New health check, "IPv6 router announcements": it turns red while the uplink still ignores router announcements, and says to run
update.
Update
Copy the binary for your server to it and run, as root:
chmod +x GHOSTWIRE-v0.3.2-linux-amd64 sudo ./GHOSTWIRE-v0.3.2-linux-amd64 updateThe update rewrites
/etc/sysctl.d/99-ghostwire.confand applies it right away; no reboot is needed. Coming from v0.3.1 or earlier, nothing else changes. For a new installation, useinstallinstead ofupdate; see the README.Files
File For GHOSTWIRE-v0.3.2-linux-amd6464-bit x86 servers GHOSTWIRE-v0.3.2-linux-arm6464-bit ARM, e.g. Raspberry Pi OS 64-bit GHOSTWIRE-v0.3.2-linux-armv7Raspberry Pi OS 32-bit SHA256SUMSchecksums: shasum -a 256 -c SHA256SUMSDownloads
- IPv6 keeps working with forwarding on: to route VPN traffic, GHOSTWIRE turns on IPv6 forwarding, and Linux then ignores the router's announcements. A server that gets its IPv6 address and route that way (SLAAC, e.g. a Raspberry Pi at home) lost its IPv6 connection after a reboot or when the route expired.