Advisory
If you are running into connectivity issues after upgrade, run "netclient pull" on your clients. The recommended upgrade process is to first upgrade the server, and then the clients.
If you are experiencing issues on initial setup, please check out the MQ troubleshooting doc. This is the most common issue for a first time setup: For MQ issues (most common first place to look), please reference this Gist before opening an issue: https://gist.github.com/mattkasun/face2a7c1f32031a2126ff7243caad12
What's new?
- Zombie Node Deletion: If a duplicate node is created (zombie), it will be added to a quarantine list. Nodes are listed as zombies if they are not "checking in", and have the same mac address as a functioning node. Zombies are deleted after 10 minutes.
- Sort nodes by address or name in UI
What's fixed?
- Relay logic: several issues with relay addresses were fixed.
- add traffic keys during node update to avoid info getting wiped
- external client cleanup of ingress gateway
Known Issues
- Windows Service: The old netclient Windows Service does not get uninstalled during upgrade. It also does not restart automatically on failure, which is absolutely necessary to function. If you're running an older Windows netclient, you must go to Windows Services, search for netclient, and change the settings so that it will "restart on failure"
- downtime during a relay peer update - takes about 30 seconds for an updated node to become reachable
- sometimes, p2p connection can only be established using a ping
- rarely, node update causes wireguard interface to disappear - workaround: run "netclient pull"
- you can update a node to a duplicate ip address (same as another node)
- sometimes, ping to peer froze after upgrade. - workaround: run "netclient pull"