v0.18.6 release.md

This commit is contained in:
dcarns 2023-04-13 13:19:04 -04:00 committed by GitHub
parent b2ce1db711
commit a498fc43c9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -1,27 +1,28 @@
# Netmaker v0.18.6 # Netmaker v0.18.6
## **Wait till out of pre-release to fully upgrade**
## whats new ## whats new
- Logic for ext client ACLs (not really usable until new UI is finished) - no new features
- Default proxy mode, enables users to determine if all Hosts should have proxy enabled/disabled/auto by default
- specify with DEFAULT_PROXY_MODE="on/off/auto"
## whats fixed ## whats fixed
- Proxy Peer calculation improvements - a few ext client/ingress issues
- DNS is populated correctly after registration by enrollment key - viewing addresses (UI)
- Migrate is functional for Windows/Mac **note** Ports may be set to 0 after an upgrade, can be adjusted via UI to fix - when deleting an ingress gateway, ext clients are now removed from peers immediately
- Interface data is sent on netclient register - ext client peers should be populated immediately after creation
- Upgrade script - ext clients no longer reset public key when disabled/enabled
- Latency issue with Node <-> Node Metrics - can delete an ingress without clients
- Ports set from server for Hosts on register/join are actually used - 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 ## known issues
- Caddy does not handle netmaker exporter well for EE - Caddy does not handle netmaker exporter well for EE
- Migration causes a listen port of 0 for upgraded hosts - Migration causes a listen port of 0 for some upgraded hosts
- Docker clients can not re-join after deletion - Docker clients can not re-join after deletion
- Innacurate Ext Client Metrics - Innacurate Ext Client Metrics
- Issue with Mac + IPv6 addressing - Issue with Mac + IPv6 addressing
- Nodes on same local network may not always connect - Nodes on same local network may not always connect
- List populates egress ranges twice - List populates egress ranges twice
- If you do NOT set STUN_LIST on server, it could lead to strange behavior on client - If you do NOT set STUN_LIST on server, it could lead to strange behavior on client
- No internet gateways/default routes