docs: Add v2022.1.3 release notes
This commit is contained in:
parent
4f8f6e7585
commit
190d7f8701
@ -5,6 +5,7 @@ Release Notes
|
|||||||
:caption: Gluon 2022.1
|
:caption: Gluon 2022.1
|
||||||
:maxdepth: 2
|
:maxdepth: 2
|
||||||
|
|
||||||
|
v2022.1.3
|
||||||
v2022.1.2
|
v2022.1.2
|
||||||
v2022.1.1
|
v2022.1.1
|
||||||
v2022.1
|
v2022.1
|
||||||
|
40
docs/releases/v2022.1.3.rst
Normal file
40
docs/releases/v2022.1.3.rst
Normal file
@ -0,0 +1,40 @@
|
|||||||
|
Gluon 2022.1.3
|
||||||
|
==============
|
||||||
|
|
||||||
|
Bugfixes
|
||||||
|
--------
|
||||||
|
|
||||||
|
* Ipq40xx Wave2 devices temporarily use non-ct firmware again to work around 802.11s unicast package loss in ath10k-ct
|
||||||
|
(`#2692 <https://github.com/freifunk-gluon/gluon/issues/2692>`_)
|
||||||
|
|
||||||
|
* Modify kernel builds slightly to work around a boot hang on various devices based on the QCA9563 SoC - especially the Unifi AC-* devices
|
||||||
|
(`#2784 <https://github.com/freifunk-gluon/gluon/issues/2784>`_)
|
||||||
|
|
||||||
|
* Work around an issue with wifi setup timing by waiting a bit while device initialisation is ongoing
|
||||||
|
(`#2779 <https://github.com/freifunk-gluon/gluon/issues/2779>`_)
|
||||||
|
|
||||||
|
|
||||||
|
Known issues
|
||||||
|
------------
|
||||||
|
|
||||||
|
* Upgrading EdgeRouter-X from versions before v2020.1.x may lead to a soft-bricked state due to bad blocks on the NAND flash which the NAND driver before this release does not handle well.
|
||||||
|
(`#1937 <https://github.com/freifunk-gluon/gluon/issues/1937>`_)
|
||||||
|
|
||||||
|
* The integration of the BATMAN_V routing algorithm is incomplete.
|
||||||
|
|
||||||
|
- Mesh neighbors don't appear on the status page. (`#1726 <https://github.com/freifunk-gluon/gluon/issues/1726>`_)
|
||||||
|
Many tools have the BATMAN_IV metric hardcoded, these need to be updated to account for the new throughput
|
||||||
|
metric.
|
||||||
|
- Throughput values are not correctly acquired for different interface types.
|
||||||
|
(`#1728 <https://github.com/freifunk-gluon/gluon/issues/1728>`_)
|
||||||
|
This affects virtual interface types like bridges and VXLAN.
|
||||||
|
|
||||||
|
* Default TX power on many Ubiquiti devices is too high, correct offsets are unknown
|
||||||
|
(`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
|
||||||
|
|
||||||
|
Reducing the TX power in the Advanced Settings is recommended.
|
||||||
|
|
||||||
|
* In configurations without VXLAN, the MAC address of the WAN interface is modified even when Mesh-on-WAN is disabled
|
||||||
|
(`#496 <https://github.com/freifunk-gluon/gluon/issues/496>`_)
|
||||||
|
|
||||||
|
This may lead to issues in environments where a fixed MAC address is expected (like VMware when promiscuous mode is disallowed).
|
Loading…
Reference in New Issue
Block a user