Releases: gravitl/netmaker
Releases · gravitl/netmaker
v0.11.1
What's New:
- DNS: Should now be functional on Windows, Mac, FreeBSD, and Linux
Fixed issues:
- Windows join issue fixed
- UI rendering issues resolved
- Minor patches to install scripts
- Additional gateway logic (iptables) to return traffic consistently
- Removed CGO from client builds (no longer dependent on system C libraries)
- Fixed logic with IsHub
Known issues
- Windows has a few bugs to sort out, reliability is not consistent
- Docker netclient updates are not reliable
v0.11.0
Important Notes:
- Do not upgrade from an existing installation to 0.11.0. No upgrade path has been defined and it will fail.
- This is a pre-production release and has not been marked as 'stable'.
3. If running FreeBSD, DO NOT USE 0.11.0. FreeBSD is known to be broken in 0.11.0. We are working to resolve this
What's new
- Comms network - Every node now joins the "comms network" before joining any other network. This greatly increases the stability of client-server communications by having a separate network for updates.
- Point-to-Site networks - A new form of network can be created on the UI, the "Point-to-Site" (P2S) network. This is similar to a concentrator or hub-and-spoke network. There is basically just one "access point" in the network, which is the hub. This is how the comms network works.
Fixed issues:
- Windows issues
- OpenWRT issues
- Various bugs
- Network-wide node updates
- Stabilized node updates
Known issues
1. cannot run upgrades from existing systems
2. FreeBSD DOES NOT RUN.
v0.10.0
Depricated: for new installs, please use 0.11.0
Important Notes:
- Do not upgrade from an existing installation to 0.10.0. No upgrade path has been defined and it will fail.
- This is a pre-production release and has not been marked as 'stable'.
- If Running Windows netclient, either keep the WireGuard app open or not open at all. If you open it and you exit/kill it completely, it will cause your tunnels to disappear. Netclient may bring them back after 10+ minutes, but it will cause downtime.
What's new
- Message Queue
- Interactive UI Node Graph
- Private DNS and SSH over WireGuard
- Host Networking Enabled
- UDP Hole Punch Switch
- Static Server Client
- Opt-Out Telemetry
- UI Tweaks: filter ext clients by gateway, save rows per page
Fixed issues:
- Route setting
- Static nodes
- Switching on/off hole punching
- local routing w/ hole punching
- UI errors
Known issues
1. cannot run upgrades from existing systems
2. Sometimes UI requests stick in pending or error out, despite completing on the server side
3. networks of more than 50 nodes will not function properly due to message size from server (need to implement chunking)
4. ipv6 routes do not get set
v0.9.4
What's new
- added wg-quick equivalent functions for MacOS client to remove dependency and move towards official installer (coming soon)
- increased Caddy proxy server security
- Docs overhaul (egress, ingress, UI labelling)
Fixed issues:
- Fixed issue with "local" networks (IsLocal)
- Minor server code fixes
Known issues
- DNS for different linux clients buggy
- Windows still needs fixes
v0.9.3
What's new
- Increased Server Stability
- UI allows for approval of key-less node joining
- Linux clients more reliant on wireguard-tools, switch to using official WG conf files
- Removed Abilty for RCE through postup/down, can be enabled with RCE Server flag
- Disabled post commands on UI when server isn't in RCE mode
- Can specify tenant for Azure AD oauth via AZURE_TENANT env on server
Fixed issues:
- Admin can delete accounts again: #560
- Egress Gateway Ranges now visible/reachable from relayed nodes, #498
- Minor UI enhancements around notifications
- Minor log changes
Known issues
- DNS for different linux clients buggy
- Windows client resets
- Windows needs work
- Mac client needs stability
v0.9.2
v0.9.1
What's New?
- Deployment templates for k8s VPN
- Enhanced userspace client / docker image
What's Fixed?
- Removed FWMark due to know issues
- Cleaned up some UI bugs
- Minor client updates for better functionality
Known Issues
- duplicate logs on client and server in some scenarios
- still issues with 0.0.0.0/0 (though there is now another way)
- lack of documentation
- some scenarios require restarting client machine or connecting multiple times to start connection successfully
v0.9.0
What's New?
- Major Netmaker UI Refactor
- New look and feel
- breadcrumbs
- toasts
- New option to display keys permanently in UI (DISPLAY_KEYS) for ease of deployment
- FreeBSD Support
- OpenWRT Support (with scripts)
- Docker client
- Link to 1-Click Install on DigitalOcean
What's Fixed?
- Issue setting routes on Windows
- Increased garbage collection on server
Known Issues
- Windows installer will sometimes fail. Running twice should fix
- OpenWRT instructions unclear
- No ARM versions for server or client docker containers
- Removing ingress gateway makes a unhealthy node look "healthy" temporarily
- an egress gateway of of 0.0.0.0/0 will not be populated to netclients
v0.8.5
What's New?
- Oauth support for GitHub, Google, and Azure AD: https://netmaker.readthedocs.io/en/master/oauth.html
- Quick Install now deploys a network by default and can optionally deploy a hub-and-spoke (regular) VPN.
- netclient-install.sh will detect version, OS, cpu, and install wireguard
- netclient's backup config files to help with potential ungraceful shutdown file corruption
What's Fixed?
- removed GLIB (C) dependencies on netclient (increases compatibility across linux distributions)
Known Issues
- installing netclient in userspace mode fails
- changing the default interface name on a network may break the server sync function
- an egress gateway of of 0.0.0.0/0 will not be populated to netclients
v0.8.4
What's New?
- Run server in userspace mode.
- Use PostgreSQL as a backing database (DATABASE=postgres)
- Helm charts to support HA on Kubernetes with an HA PostgreSQL Cluster, Userspace WG (no WG dependencies): https://github.com/gravitl/netmaker-helm/
- removed node name length limit
- netclient name's self based on hostname
- install script detects OS/arch
What's Fixed?
- Security enhancements
- Server code separated from netclient
Known Issues
- Potential library incompatibilities on certain systems. Please open issue on GitHub if your linux distro is not supported.