Netmaker has just released version 0.24.2, bringing new features and improvements to enhance your network management experience. Here’s a breakdown of what’s new and what’s improved in this latest release.

New Features ✨

Static Host Functionality

In this update, Netmaker introduces static host functionality, allowing users to set separate settings for port and endpoint IPs. This provides greater flexibility and control over your network configurations, making it easier to manage static hosts.

Enhanced Remote-Access-Client

The Remote-Access-Client now includes network info and metadata info, providing users with detailed insights and better management capabilities for remote access clients.

Fixes and Improvements 🛠

Improved Failover Functionality

Netmaker has made significant improvements to its failover functionality, ensuring that your network remains resilient and operational even in the face of disruptions.

Local Peer Routing in Dual-Stack Environments

With this update, local peer routing in dual-stack environments is now more efficient, improving overall network performance and reliability.

Resolved Stale Node Issues on Multinet with netclient uninstall

The issue of stale nodes on multinet when using netclient uninstall has been addressed, ensuring a cleaner and more reliable network environment.

IPv6 Internet Gateways Improvements

Improvements have been made to IPv6 Internet gateways, enhancing connectivity and performance for IPv6 networks.

Handled New Oauth User SignUp via Remote-Access-Client

The Remote-Access-Client now better handles new Oauth user signups, streamlining the process and improving user experience.

PeerUpdate Improvements

Enhancements around default host and multi-nets have been implemented in the PeerUpdate process, ensuring more accurate and reliable peer updates.

Known Issues 🐞

Erratic Traffic Data in Metrics

There are reports of erratic traffic data in metrics. The team is aware and working on a fix for this issue.

Stale Peer on Interface

A stale peer can appear on the interface when forcibly removed from multiple networks at once. This is a known issue and is being actively investigated.

‍

Stay tuned for more updates and improvements in future releases. Happy networking!