Netmaker v0.18.6

Limitations

• Egress to 0.0.0.0/0 (internet gateways) is currently disabled. Will be re-implemented in a near-future release. If you use or need internet gateways, either stay with 0.17.1, or use the following list of ranges in place of 0.0.0.0/0:
  0.0.0.0/5,8.0.0.0/7,11.0.0.0/8,12.0.0.0/6,16.0.0.0/4,32.0.0.0/3,64.0.0.0/2,128.0.0.0/3,160.0.0.0/5,168.0.0.0/6,172.0.0.0/12,172.32.0.0/11,172.64.0.0/10,172.128.0.0/9,173.0.0.0/8,174.0.0.0/7,176.0.0.0/4,192.0.0.0/9,192.128.0.0/11,192.160.0.0/13,192.169.0.0/16,192.170.0.0/15,192.172.0.0/14,192.176.0.0/12,192.192.0.0/10,193.0.0.0/8,194.0.0.0/7,196.0.0.0/6,200.0.0.0/5,208.0.0.0/4

• EE should still be considered pre-release, and we do not recommend upgrading yet.

Follow Upgrade Instructions Carefully - You must upgrade server before netclients

1. You must be on v0.17.1 in order to upgrade
2. SSH to your Netmaker server
3. Run the upgrade script: wget https://raw.githubusercontent.com/gravitl/netmaker/release_v0.18.5/scripts/nm-upgrade.sh && chmod +x nm-upgrade.sh && ./nm-upgrade.sh
4. Follow prompts until the upgrade process on the server is completed.
5. Upgrade all netclients using whichever method you prefer. Either download the netclient from the release page or follow the upgrade instructions for your operating system (e.x. "apt-get install netclient")

whats new

• no new features

whats fixed

• a few ext client/ingress issues
  • viewing addresses (UI)
  • when deleting an ingress gateway, ext clients are now removed from peers immediately
  • ext client peers should be populated immediately after creation
  • ext clients no longer reset public key when disabled/enabled
  • can delete an ingress without clients
• removed unnecessary host update
• host nat type is now collected from clients
• fix peer update issue where caclulation was happening to frequently
• nm-quick && nm-upgrade
• EMQX image change && api routes

known issues

• Caddy does not handle netmaker exporter well for EE
• Migration causes a listen port of 0 for some upgraded hosts
• Docker clients can not re-join after deletion
• Innacurate Ext Client Metrics
• Issue with Mac + IPv6 addressing
• Nodes on same local network may not always connect
• List populates egress ranges twice
• If you do NOT set STUN_LIST on server, it could lead to strange behavior on client
• No internet gateways/default routes