Netrinos Client v1.2.4 - Release Notes

What’s New

New netrinos doctor command - Comprehensive system health check that verifies your installation and network configuration (replaces the older check command)
- Shows clear status for all components with ✓ (installed) or ✗ (missing) indicators
- Detects common configuration issues and provides solutions
- EdgeNode users: Highlights critical requirements like IPv4 forwarding

Smarter peer-to-peer connections - Improved algorithm for establishing direct connections between devices
- Faster connection establishment with nearby peers
- Better handling of devices behind firewalls
- Automatic fallback to relay when direct connection isn’t possible
- Optimized for mixed networks with both v1.2.3 and v1.2.4 clients

New CLI commands for EdgeNode management:
- netrinos uiport - Change the web interface port (default: 88)
- netrinos scan - Control network scanning (on/off/now)
- netrinos wgport auto - Automatic WireGuard port selection helps bypass ISP port restrictions
Better network scanning - More efficient scanning with clearer status reporting
Enhanced Client UI - Desktop app now provides one-click access to EdgeNode web interfaces, similar to the web portal

Enhanced file corruption protection - Configuration files are now written to temporary storage first, then moved atomically
- Prevents corruption if disk becomes full during write
- Ensures configuration integrity even during unexpected shutdowns

Faster sync times - Optimized connection testing reduces sync time from minutes to seconds
Smarter retries - Progressive backoff prevents excessive retesting of offline devices
Resource efficiency - Better CPU and network usage during peer discovery

Fixed file permission issues affecting Ubuntu 20.04 and older
Fixed GUI not showing correct login state on startup
Fixed GUI authentication not syncing with command-line login
Fixed route management issues on macOS
Fixed configuration saving errors on EdgeNode devices
Fixed connection status incorrectly showing devices as offline
Fixed log messages appearing at wrong severity levels
Fixed log level setting not persisting after restart
Fixed package upgrades on Debian/Ubuntu that could fail due to file locks, preventing the client from being updated