Releases: brocaar/chirpstack-network-server
v3.12.3
v3.12.2
v3.12.2
Improvements
- Update
LinkADRAnshandling for devices with ADR disabled to align with 4.3.1.1 of LoRaWAN 1.0.4 specs.
Bugfixes
- Fix max. supported TxPower index which was introduced after ADR refactor.
- Fix counting uplink history so that only items with same TxPowerIndex are counted.
v3.12.1
v3.12.0
v3.12.0
Features
Private gateways
This adds the option to add a service-profile to a gateway and a service-profile flag to make all gateways under that service-profile private. It also adds a global configuration option to make all gateways private. When a gateway is private, only devices under the same service-profile will be able to use the gateway.
Pluggable ADR algorithms
This adds the option to configure custom ADR algorithms through a plugin system. See the examples/adr-plugin directory for an example plugin skeleton.
Improvements
- Implement uplink frame counter for Prometheus. (#507)
v3.12.0-test.2
v3.12.0-test.2
v3.12.0-test.1
v3.12.0-test.1
v3.11.0
v3.11.0
Features
Passive roaming
This release provides an experimental implementation of the Passive Roaming implementation as specified by the LoRaWAN Backend Interfaces v1.0.0 specification.
Improvements
Improve uplink de-duplication
This removes the de-duplication that was also performed by the MQTT backend. It also updates the current deduplication function to include the full TXInfo within the de-duplication key. Uplinks received on multiple channels will therefore be processed (and MIC validated) separately.
Add stats interval to gateway profile
This makes it possible to set the gateway stats interval when supported by the gateway (currently only Concentratord is supported).
Internal join-server cleanup
This removes old join-server code on favor of the client code which is also used for Passive Roaming (as both are based on the LoRaWAN Backend Interfaces specification).
Expose gateway expiration date
When creating a gateway certificate, the expiration is now exposed in the API response.
Join-server DNS resolving
When no join-server is pre-configured, DNS resolving is enabled and the JoinEUI does resolve, the the same certificate configuration will be used as when connecting to the default join-server.
Add tls_enabled option to Redis config.
In earlier releases, it was possible to configure the Redis endpoint by URL, which allowed to enable TLS. The configuration changed when support for Redis Sentinel and Redis Cluster was implemented. This adds back the option to enable TLS.
Bugfixes
v3.11.0-test.1
v3.11.0-test.1
v3.10.0
ChirpStack Network Server v3.10.0
Features
Multi-downlink commands and ACKs
With this feature, ChirpStack Network Server will send all downlink opportunities (e.g. RX1 and RX2) at once to the gateway, reducing the number of roundtrip in case of failures. Previously ChirpStack Network Server would send the next downlink opportunity on a received nACK. In case of a retry, this saves one roundtrip reducing the risk of a failed downlink due to network latency. The gateway will always send at most one downlink.
Note: This feature requires ChirpStack Gateway Bridge v3.9 or later, but is backwards compatible with previous versions, in which case ChirpStack Network Server will fallback into the old behavior. This backwards compatibility has some overhead, which can be controlled by the multi_downlink_feature configuration variable.
Disable device
This feature makes it possible to (temporarily) disable a device, in which case uplinks are ignored.
Join Server integration
The Join Server integration has been updated, so that it is no longer required to rely on DNS resolving of the Join Server. It is now possible to configure a per JoinEUI endpoint of the Join Server.
Geolocation cleanup
This removes the Geolocation Server integration (relying on LoRa Cloud) from ChirpStack Network Server. The reason for this is that there are various options for geolocation, some of them relying on the decrypted FRMPayload, e.g. in case of Wifi and GNSS sniffing. To provide one unified integration, this integration has been moved to ChirpStack Application Server.
Note: This will deprecate ChirpStack Geolocation Server as v3.11 will provide a per-application configurable LoRa Cloud integration.
Gateway client-certificates
This makes it possible to generate per-gateway client-certificates which can be used to implement gateway authentication and authorization. For example a MQTT broker can be configured to validate the client-certificate against a pre-configured CA certificate and if valid it can use the CommonName of the certificate (which contains the gateway ID) to authorize publish / subscribe to certain topics.
Improvements
- Expose to Application Server if received uplink was confirmed or unconfirmed.
- Improve error handling and ignore uplink when uplink is received through unknown gateway.
- Avoid downlink mac-commands for ABP devices when factory frequencies have been correctly setup and are in sync with network channels.
- Support multiple Redis addresses for clustering. (#491)
Upgrading
Important note:
This version improves the error handling when an uplink is received through an unknown gateway. Previously this was logged as an error, this has changed to a warning. Uplinks received through unknown gateways will be ignored. Make sure that all gateways in your network are configured in ChirpStack!
v3.10.0-test.3
v3.10.0-test.3