Husarnet Versions Save

Husarnet is a Peer-to-Peer VPN to connect your laptops, servers and microcontrollers over the Internet with zero configuration.

v2.0.180

7 months ago

Changelog:

  • [Installer] Remove non-essential error messages
  • [Core] Make config directory creation errors more visible
  • [CLI] Make notification and hook status reporting more coherent with the overall layout
  • [Core] Fix husarnet-local hostname adding
  • [Core] Fix race-condition in daemon's HTTP API
  • [Core] Reduce verbosity of non essential messages

v2.0.170

11 months ago

Changelog:

  • [Platforms] Add amd64 support for MacOS
  • [Platforms] Various tweaks for MacOS
  • [Core] gcc13 compile error and memory error by @jbbjarnason

v2.0.160

11 months ago

Changelog:

  • [Core] Fix notifications on read-only file systems
  • [Core] Make service installer handle more cases
  • [Core] Make logging less verbose on production builds but include human-readable timestamps
  • [Core] Don't include debugging symbols in production builds
  • [Platforms] Various MacOS tweaks and fixes

v2.0.141

1 year ago

Changelog:

  • [Platforms] Added ArchLinux builds and repository
  • [Platforms] Unified installation methods/scripts for all platforms
  • [CLI] Added an option for sending announcements to the users that will be shown in CLI
  • [CLI] Added a warning about a Daemon running old configuration and needing a restart

v2.0.78

1 year ago

Changelog:

  • [CLI] added --follow flag to husarnet status
  • [CLI] implemented a command for removing devices via CLI (husarnet dashboard device rm)
  • [Windows] multiple small tweaks to the installation process
  • [CLI] added husarnet daemon logs command category for remote log management
  • [Daemon] added a hook mechanism for executing user scripts on various daemon events

v2.0.52

1 year ago

Changelog:

  • [Windows] Fixed the newline issue in hosts file
  • [Windows] Made restart prompt more robust
  • [Linux] Added integration tests for Debian
  • [Linux] Made the deb package manifest include more low-level dependencies
  • [Linux] Made integration tests for Linux run on CI too
  • [MacOS] Preliminary work for the new port was added to the repo

v2.0.18

1 year ago

v2.0.22

1 year ago

Changelog:

  • added a non-interactive version of husarnet dashboard login CLI command
  • fix Windows platform build
  • fix Docker platform hostname recognition
  • update libsodium to latest stable
  • add husarnet daemon genid util

v2.0.13

1 year ago

Changelog:

  • switched to a more widely adopted emoji set for CLI
  • fixed RPM builds
  • changed the logging logic to be less verbose on some axis and more on others
  • reworked a websetup connection thread (this includes fixes for join workflows)
  • updated the post-install/remove to be more resilient to errors

v2.0.0

1 year ago

After almost a year of work the day has come! We're finally releasing Husarnet 2.0!

Let's start with action items for you first and then we'll describe what has changed with more details.

  1. There are now two separate binaries husarnet-daemon and husarnet (CLI). If your scripts are using those paths directly - you need to to update them
  2. CLI commands have changed - please have a look at updated Husarnet Documentation - for the detailed changes and, again, if your scripts are using those - update them
  3. During the first start of the husarnet-daemon it will migrate your data to a new format. No actions should be required for you there

…and that's it! Now let us describe what we've changed, why this was needed and what it means for you.

  1. Unified experience for all of the platforms - the previous version of the codebase made it difficult to support various platforms in a unified way. As we want to grow onto new platforms, we needed to make necessary changes to make it as unified as possible. Now, for example, the CLI experience on Windows and Linux platforms will be the same. Keep an eye for new platforms soon!
  2. API-centric approach - we've started a migration from custom protocols to industry-standard ones. Now you can control husarnet-daemon using regular HTTP API. That means no more CLI parsing in your scripts - you'll be getting regular JSON responses that you can parse using tools like jq. CLI is currently using this feature but it's not yet marked as fully stable. We will publish detailed docs at our documentation page when it makes it to stable.
  3. Dashboard API - instead of keeping a special API for enterprise customers only, we've now rolled a GraphQL API available to all of our users. You can now manage your devices/groups using it. New CLI is already capable of interacting with it. Try it out using husarnet dashboard -h! As per husarnet-daemon API - we are not marking it as fully stable right now and the documentation will be available at the later time.
  4. Naming change - this is a part of a process that will take place over next couple months - we're making naming more consistent and intuitive. So far the most important change is Husarnet Network to Husarnet Group. Right now this change is reflected in CLI only, but it'll make more sense once it makes into new Dashboard.
  5. Short join codes - join codes can now use a short format (without the Websetup IP prefix that is automatically added using the license file).
  6. CLI is written in Go - in order to ease a development of new features our CLI is now written in Go. Right now it's not made to be importable from other packages, but we plan to make it so. You'll then be able to use our logic for communication with both Husarnet Daemons and Husarnet Dashboard in your projects!
  7. Semver - we've finally joined the semver bandwagon and will stick to it. Our plan is to keep development and regular patches on the patch section and release all the things relevant for users on minor section. That means you can expect changelogs and blog posts about new features more often.
  8. Dropped ROS 1 master node marking - over the next couple of weeks we will be dropping the support for marking nodes as ROS master. This feature was increasingly complex to support while the userbase dropped steadily.

That's not all, but 8 is a good, "round" number so let's keep it at it for now ;) We're extremely excited for this release and looking forward to any feedback from you.