Releases: gt4o4/netclient
v1.5.1
Netclient v1.5.1 Release Notes π
π Whatβs New
π Firewall Mark Support
Added support for configuring a firewall mark via the install command.
π Traffic Logs (Beta)
Traffic Logs have now moved into Beta.
- Traffic Logs are now enriched with relevant domain tagging, making network activity easier to audit and investigate.
π Default Netclient Port Update
The default Netclient port has been changed to 51821/udp (previously 443/udp).
π§° Improvements & Fixes
Docker Netclient
- Updated the Netclient Docker deployment to run in the foreground, moving away from daemon management inside the container.
Scalability Improvements
- Improved peer synchronization by caching peer information and only refreshing when a peer update is triggered.
Windows
- Netclient now uses the provided interface name on Windows.
DNS
- Added a Noop DNS Config Manager fallback when DNS Manager initialization fails.
- Added Windows Active Directory compatibility mode.
Egress Routes
- Netclient now automatically avoids adding conflicting routes with local interfaces.
Internet Gateways
- Internet Gateways are now marked unhealthy when a node is disconnected or a peer is not found.
CLI Commands
- Fixed missing
endpoint-ip6flag name. - Removed the MTU flag from CLI configuration (this can now be configured via the control plane).
π Known Issues
-
IPv6-only machines
Netclients cannot currently auto-upgrade on IPv6-only systems. -
Multi-network join performance
Multi-network netclient joins using an enrollment key still require optimization. -
systemd-resolved DNS limitation
On systems using systemd-resolved in uplink mode, only the first 3 entries inresolv.confare honored; additional entries are ignored. This may cause DNS resolution issues. Stub mode is recommended.
v1.5.1-rc1
Netclient v1.5.0 Release Notes π
π Whatβs New
π Overlapping Egress Ranges (beta)
- Virtual NAT mode enables multiple egress routers to share overlapping IP ranges by assigning each egress a virtual range from a configurable pool.
- Configurable per-network IPv4 pool and site prefix length for virtual range allocation.
- Eliminates routing conflicts when multiple sites need to egress the same destination CIDRs (e.g., multiple offices routing to the same cloud VPC).
- Supports both direct NAT and virtual NAT modes for flexible egress configurations.
π§ macOS Local DNS Resolver
-
Darwin netclients now run their own local DNS resolver.
Benefits
-
More consistent DNS resolution
-
Improved compatibility with macOS networking stack
-
Reduced dependency on system DNS behavior
-
π Internet Gateways on macOS
-
Darwin netclients can now:
-
Use Internet Gateways
-
Participate in fully routed internet traffic
-
This brings feature parity closer to Linux and Windows clients.
-
π§° Improvements & Fixes
DNS:
-
Debian DNS configuration fix
-
Improved Windows DNS management
GeoLocation:
-
Consolidated IP location API usage
-
Added fallback mechanisms
Windows:
-
Improved logging
-
Fixed installer issues
-
Version command corrections
-
Better adapter error handling
LAN Routing:
-
Added configurable interface exclusion
-
Fixes Kubernetes endpoint detection conflicts
Known Issues π
-
netclients cannot auto-upgrade on ipv6-only machines.
-
Need to optimize multi-network netclient join with enrollment key
-
On systems using systemd-resolved in uplink mode, the first 3 entries in resolv.conf are used and rest are ignored. So it might cause DNS issues. Stub mode is preferred.
v1.5.0-gbc1
Netclient v1.5.0 Release Notes π
π Whatβs New
π Overlapping Egress Ranges (beta)
- Virtual NAT mode enables multiple egress routers to share overlapping IP ranges by assigning each egress a virtual range from a configurable pool.
- Configurable per-network IPv4 pool and site prefix length for virtual range allocation.
- Eliminates routing conflicts when multiple sites need to egress the same destination CIDRs (e.g., multiple offices routing to the same cloud VPC).
- Supports both direct NAT and virtual NAT modes for flexible egress configurations.
π§ macOS Local DNS Resolver
-
Darwin netclients now run their own local DNS resolver.
Benefits
-
More consistent DNS resolution
-
Improved compatibility with macOS networking stack
-
Reduced dependency on system DNS behavior
-
π Internet Gateways on macOS
-
Darwin netclients can now:
-
Use Internet Gateways
-
Participate in fully routed internet traffic
-
This brings feature parity closer to Linux and Windows clients.
-
π§° Improvements & Fixes
DNS:
-
Debian DNS configuration fix
-
Improved Windows DNS management
GeoLocation:
-
Consolidated IP location API usage
-
Added fallback mechanisms
Windows:
-
Improved logging
-
Fixed installer issues
-
Version command corrections
-
Better adapter error handling
LAN Routing:
-
Added configurable interface exclusion
-
Fixes Kubernetes endpoint detection conflicts
Known Issues π
-
netclients cannot auto-upgrade on ipv6-only machines.
-
Need to optimize multi-network netclient join with enrollment key
-
On systems using systemd-resolved in uplink mode, the first 3 entries in resolv.conf are used and rest are ignored. So it might cause DNS issues. Stub mode is preferred.