Releases: gravitl/netmaker
Releases · gravitl/netmaker
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.
v0.8.3
NOTICE: v0.8.3 and v0.8.2 contains breaking changes for netclients. If upgrading from v0.8.1 or lower, you must perform the following actions on all netclients, or uninstall and rejoin the network:
create /etc/netclient/config folder
move all files in /etc/netclient besides the netclient into the config folder
if a new network is joined: remove existing netclient@.service files and netclient-network.timer files from /etc/systemd/system
if 3 is performed, run systemctl-daemon reload
Alternatively, you can run "netclient uninstall" on each client, replace the netclient with the new version, and rejoin the network.
What's New?
- Integrated Netclient code into Netmaker. Netmaker no longer runs Netclient binary. Instead, it makes direct function calls. This reduces the image size for Netmaker by 50%.
- Enabled HA topology for Netmaker: https://netmaker.readthedocs.io/en/develop/server-installation.html#highly-available-installation. UDP Hole Punching implemenation made full HA infeasible. Now, distributed servers with UDP Hole Punching will work.
What's Fixed?
- Minor changes to nm-quick install script (changed docker install to docker.io) and quick install instructions (changed apt install command).
- Fixed a bug that caused MTU settings to revert to default on checkin
Known Issues
- Overly verbose logging on Netmaker server with Netclient logs. Will change verbosity in next release.
v0.8.2
NOTICE: v0.8.2 contains breaking changes for netclients. If upgrading from v0.8.1 or lower to v0.8.2, you must perform the following actions on all netclients, or uninstall and rejoin the network:
- create /etc/netclient/config folder
- move all files in /etc/netclient besides the netclient into the config folder
- if a new network is joined: remove existing netclient@.service files and netclient-network.timer files from /etc/systemd/system
- if 3 is performed, run systemctl-daemon reload
Alternatively, you can run "netclient uninstall" on each client, replace the netclient with the new version, and rejoin the network.
What's New?
- Moved netclient config files under /etc/netclient/config. This allows for running the tiny dockerized version of netmaker/netclient (beware of breaking changes, see above)
- Added a configurable checkin time for server (set env var CHECKIN_INTERVAL). Default of 15 seconds for all clients. When set, this value is passed to clients via the access token. Clients will not receive updated values for checkin interval. This is only set on Join (but can be changed manually).
- Linux now has one checkin systemd service timer for all networks, instead of one per network
- IsServer is now adjustable, allowing for manual debugging of server issues on netclient.
v0.8.1
What's New?
- Added contained mode for server, netclient management, specified with CLIENT_MODE=contained
- Created smaller images for Containers, they are 1/10 the size they used to be..
- Added default setting to help with upgraded nodes from 0.7
- DNS simplified, can now set static DNS configs, use coredns as a generic DNS server
What's Fixed?
- Ingress deletion issue when no ext clients present #284
- Egress Deletion issue, removes ingress post-up/down #285
- Mac Client copies binary appropriately,
Known issues
- Mac binary currently not present in release, would require a build on Mac right now
- Mac has not been tested with M1 chips
- Library issues running netclient in certain environments (SUSE, OpenWRT)
- relay server will not forward traffic to egress gateway behind relay
- old files still in repo (old docs, scripts, etc)
- Kubernetes manifests out of date
- Resolvectl does not work on some systems
- Sometimes peers appear on a relayed node, when they should not
v0.8.0
What's New?
- Windows client with NT support. Run fully meshed Windows nodes - Requires v0.4.9 of WireGuard for Windows
- Make sure to use
Powershell as Admin
- Make sure to use
- Mac client with userspace (wireguard-go) support. Run fully meshed Mac nodes
- Relay Server functionality for nodes - designate nodes as "relay servers" for hard-to-reach nodes (behind double NAT's, Firewalls, etc)
- Configurable MTU for nodes (default set to 1280). Fixes previous connectivity issues for certain environments
- (experimental) Userspace support for Boringtun and Wireguard-Go
What's Fixed?
- Logging on netclient improved - now shows output of failed commands for traceability
- Can add dashes to network and key names
- #277
- #266
- #245
- #254
Known issues
- Lack of documentation for new features: Mac, Windows, Relay
- Mac has not been tested with M1 chips
- Library issues running netclient in certain environments (SUSE, OpenWRT)
- relay server will not forward traffic to egress gateway behind relay
- old files still in repo (old docs, scripts, etc)
- Kubernetes manifests out of date
- Socket leaks in Nginx with low CPU (1cpu shared)
- Sometimes peers appear on a relayed node, when they should not
v0.7.3
What's New?
- Automated Ext Client egress gateway range addition to allowed ips
- Added optional Ext Client DNS field on network level - will propogate to ext clients when set
- Added Ext Client DNS to docs but not built
- UI updated to reflect changes
What's Fixed?
- QR code mapping on UI fixed
Known issues
- No docs for new DNS field yet