Releases: gravitl/netmaker
Releases · gravitl/netmaker
v0.12.2
What's New
- Ext Clients are now reachable from other nodes connected to the ingress gateways
- Node IDs present in the Netclient
listcommand - Custom DNS entries are propagated to clients once again
- Upgraded Go Version
- Added verbosity (specified with -v, -vv, -vvv) i.e.
./netclient join -t <token> -vvv - Specify config path with -c on Netmaker server
- Dark mode on UI
What's Fixed
- repetitive IPtables issue
- stability issues around ext clients
Known Issues
- Windows: installs can be unreliable - Recommendation: if running into issues with the powershell install script, download the netclient.exe manually and run "netclient.exe join -t " (must already have WireGuard installed) or Use an ext client config, since mesh nodes can now communicate with ext clients.
Compatibility
- Netmaker v0.12.2 works with v0.11+ clients
v0.12.1
What's New
- Set default node ACL (enabled or disabled) on network create
- run iptables forwarding regularly to ensure MQ comms
- allow setting "0" keepalive
- docs moved to gravitl/netmaker-docs
- server routes added on ext clients
- set mtu on ext clients
What's Fixed
- comms network creation should be enforced
- keepalives now being sent
- egress gateway routes should be set on server now
- dns settings should be more reliable
- access keys more secure
- SQLite database reliability enhanced (avoids conflicting calls by locking DB)
Known Issues
-
Windows: installs can be unreliable - Recommendation: if running into issues with the powershell install script, download the netclient.exe manually and run "netclient.exe join -t " (must already have WireGuard installed)
-
Server reliability: On a subset of installs, even though server appears healthy and clients join successfully, clients are unable to communicate with each other. We are investigating the root cause and have been unable to replicate. If you encounter this issue, please provide notes about your installation in this issue: #945
Compatibility
- Netmaker v0.12.1 works with v0.11+ clients
v0.12.0
What's New
- Node ACLs, Ability to disallow and allow connections between nodes on the same network at will
- Ext Client Disabling/Enabling
- UI Reflects these changes
- Client Versions are displayed for nodes in UI
- Packages for RPM, Deb and Pacman
- New Logo
What's Fixed
- Windows client now receives Node Updates once again
- Minor Bug fixes around backend, client and UI
- Correct DNS propogation based on allowed peers
Known Issues
- Stability of Peer Updates may vary on connection to server
- Windows joining bug to be hotfixed
Compatibility
- Netmaker v0.12.0 works with v0.11+ clients
A workflow test release
DO NOT USE
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