24.06.002 changelog

24.06.002

Released on 21 June, 2024.

Client

On Windows: At boot, awake from sleep, or certain network change events, there was a race condition between bowtie-dns and the network interface coming online. An upstream test was added and the service is much more resilient to network change events of any kind.
Bowtie refuses to install routes that will cause conflicts with already existing system routes. This logic was too aggressive, and now Bowtie will install routes that overlap but do no conflict.
For example, if you have a system route 10.0.0.0/24 and wish to install a Bowtie route at 10.0.0.0/8 this will now work. The 10.0.0.0/24 route is more specific and the OS will preferentially route to it. The Bowtie route will not interfere with the existing system route.
Bowtie will now not switch networks from one wireguard peer to another as long as the previous peer is still up.
The Bowtie installer now deletes any log files created by older versions of Bowtie that used different log file names.
A MacOS segfault introduced in 24.05.003 has been fixed.

On MacOS Bowtie now creates a _bowtie system user and uses it to run the DNS daemon. (Linux has used the bowtie user since 24.05.001)
Wireguard handshake status added to support help page.

Controllers now support the ability to perform regularly-scheduled backups and restore from those backups either interactively or automatically. Consult the backup and restore documentation for additional information.