|
|
@@ -0,0 +1,55 @@
|
|
|
+Gluon 2016.2.4
|
|
|
+==============
|
|
|
+
|
|
|
+Bugfixes
|
|
|
+~~~~~~~~
|
|
|
+
|
|
|
+* Fix batman-adv (compat 15) not being able to transmit packages of specific sizes (`b7eeef9 <https://github.com/freifunk-gluon/gluon/commit/b7eeef9b04b44a70b2a953c4efe35a3fdceba2db>`_)
|
|
|
+
|
|
|
+ We suspect that this issue was also the reason for the autoupdater/wget hangs observed by many communities.
|
|
|
+ Non-Gluon-nodes like gateways should be updated to batman-adv 2017.0.1 to get the fix.
|
|
|
+
|
|
|
+* Fix build after ftp.all.kernel.org discontinuation (`#1059 <https://github.com/freifunk-gluon/gluon/issues/1059>`_)
|
|
|
+
|
|
|
+* Fix high load because of frequent calls of the respondd initscript (`9a0aeb9 <https://github.com/freifunk-gluon/gluon/commit/9a0aeb9b7482df4e4515e61356b9d393e3a7eacb>`_)
|
|
|
+
|
|
|
+ The respondd restart triggers added in v2016.2.3 ran a significant portion of the respondd initscript for each router advertisement
|
|
|
+ received. This was fixed by a backport of a netifd patch.
|
|
|
+
|
|
|
+* x86 sysupgrade fixes (`41fd50d <https://github.com/freifunk-gluon/gluon/commit/41fd50d20ba31d73c4796c5b2d4eb44ad2258b90>`_,
|
|
|
+ `ad37e2b <https://github.com/freifunk-gluon/gluon/commit/ad37e2b6b43b2c3389356d892b04f3873d8f6b93>`_)
|
|
|
+
|
|
|
+ This fixes sysupgrade on mmcblk and similar devices.
|
|
|
+
|
|
|
+Other changes
|
|
|
+~~~~~~~~~~~~~
|
|
|
+
|
|
|
+* The manifest generator has been extended to generate SHA256 checksums in addition to SHA512 ones
|
|
|
+ (`f9d59be <https://github.com/freifunk-gluon/gluon/commit/f9d59be731efd31a26c59e049ccbdc4b1762f6b1>`_)
|
|
|
+
|
|
|
+ We have recently switched the autoupdater to SHA256 in the Gluon master to avoid mixing two different
|
|
|
+ lengths of hashes for no good reason. This makes the manifests of Gluon v2016.2.x compatible with the
|
|
|
+ new autoupdater so it doesn't prevent backports or downgrades.
|
|
|
+
|
|
|
+ **Note:** Downgrades of major Gluon versions are generally unsupported and will often lead to
|
|
|
+ broken configurations.
|
|
|
+
|
|
|
+Known Issues
|
|
|
+~~~~~~~~~~~~
|
|
|
+
|
|
|
+* x86 sysupgrade (sometimes) loses config when kernel partition grows (`#1010 <https://github.com/freifunk-gluon/gluon/issues/1010>`_)
|
|
|
+
|
|
|
+ This issue affects upgrades from v2016.2.x and older to the Gluon master only, we hope to fix it before the next
|
|
|
+ major release.
|
|
|
+
|
|
|
+* 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.
|
|
|
+
|
|
|
+* 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 promicious mode is disallowed).
|
|
|
+
|
|
|
+* Inconsistent respondd API (`#522 <https://github.com/freifunk-gluon/gluon/issues/522>`_)
|
|
|
+
|
|
|
+ The current API is inconsistent and will be replaced eventually. The old API will still be supported for a while.
|
Matthias Schiffer