update

docs/releases/v2022.1.rst

@@ -345,6 +345,14 @@ for the VPN tunnel connection is now moved to the specific VPN provider
 configuration. For fastd this means that ``mesh_vpn.mtu`` needs to be
 moved to ``mesh_vpn.fastd.mtu``. (`#2352 <https://github.com//pull/2352>`__)
 
+Preconfigured Interfaces Roles
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Instead of ``mesh_on_wan`` and ``mesh_on_lan`` there is now a
+``interfaces`` block to configure the default behavior of network
+interfaces. Details can be found in the 
+:ref:`documentation<user-site-interfaces>`.
+
 Minor changes
 -------------
 
@@ -353,7 +361,8 @@ Minor changes
    ``bcm27xx-bcm2710``
 -  The GL.iNet GL-AR750S was moved to the ``ath79-nand`` subtarget
 -  Gluon now ships the ath10k-ct firmware derivation for
-   QCA9886/QCA9888/QCA9896/QCA9898/QCA9984/QCA9994/IPQ4018/IPQ4028/IPQ4019/IPQ4029
+   QCA9886 / QCA9888 / QCA9896 / QCA9898 / QCA9984 /
+   QCA9994 / IPQ4018 / IPQ4028 / IPQ4019 / IPQ4029
    radios (`#2541 <https://github.com//pull/2541>`__)
 -  WolfSSL instead of OpenSSL is now used when built with WPA3 support.
 -  The option to configure the wireless-channel independent from the
@@ -375,3 +384,28 @@ Known issues
 
 - A workaround for Android devices not waking up to their MLD subscriptions was removed,
   potentially breaking IPv6 connectivity for these devices after extended sleep periods
+
+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).