v0.1.3

Machines are now named only as <machine>.<network-name> in the hosts file. A name with the network's suffix, such as laptop.home, always goes through Hawser; a bare name such as laptop is left to the local network, so two machines on the same LAN reach each other directly by their bare names.

Upgrading changes names. If you used bare names to reach machines over Hawser, switch to <machine>.<network-name>. Each machine rewrites its hosts block when it restarts on the new version.

Downloads for Linux on x86-64, arm64 and armv7 (Raspberry Pi):

• .deb for Debian, Ubuntu and Raspberry Pi OS: sudo apt install ./hawser_0.1.3_<arch>.deb
• .rpm for Fedora, RHEL and openSUSE: sudo dnf install ./hawser-0.1.3-1.<arch>.rpm
• .apk for Alpine: sudo apk add --allow-untrusted ./hawser_0.1.3_<arch>.apk
• .tar.gz for any other distribution: unpack, then sudo ./install.sh ./hawser

Then sudo systemctl restart hawser. Every binary is static and needs nothing but Linux 5.6 or later. SHA256SUMS covers all files.

v0.1.2

The first public release of Hawser: a private network between your own machines, over kernel WireGuard. Fixed addresses, names in the hosts file, direct paths where they work and relaying through the coordinator where they do not, single-use invites, and a systemd service.

Downloads for Linux on x86-64, arm64 and armv7 (Raspberry Pi):

• .deb for Debian, Ubuntu and Raspberry Pi OS: sudo apt install ./hawser_0.1.2_<arch>.deb
• .rpm for Fedora, RHEL and openSUSE: sudo dnf install ./hawser-0.1.2-1.<arch>.rpm
• .apk for Alpine: sudo apk add --allow-untrusted ./hawser_0.1.2_<arch>.apk
• .tar.gz for any other distribution: unpack, then sudo ./install.sh ./hawser

Every binary is static and needs nothing but Linux 5.6 or later. SHA256SUMS covers all files. Setting up a network is in the README.