nils/gluon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: releases/v2018.1: add regressions to known issues

Browse Source 
Fixes #1519
This commit is contained in:
Matthias Schiffer 2018-08-26 13:30:55 +02:00
parent b4e87400ca
commit bc0d240d75
No known key found for this signature in database
GPG Key ID: 16EF3F64CB201D9C
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/releases/v2018.1.rst
View File

@ -400,3 +400,21 @@ Known issues
Optimizations in Gluon 2018.1 have significantly improved memory usage. Optimizations in Gluon 2018.1 have significantly improved memory usage.
There are still known bugs leading to unreasonably high load that we hope to There are still known bugs leading to unreasonably high load that we hope to
solve in future releases. solve in future releases.
* Configuration loss on upgrade under certain circumstances
(`#1496 <https://github.com/freifunk-gluon/gluon/issues/1496>`_)
The issue can only occur when upgrading from 2018.1 and there are multiple
mirror entries in *site.conf* (specifically, an early failure for one of the
mirrors, e.g. during DNS resolution, followed by a successful upgrade from a
different mirror triggers the issue).
This is a regression in Gluon 2018.1.
* Next-node ARP issue
(`#1488 <https://github.com/freifunk-gluon/gluon/issues/1488>`_)
A routing table issue leads to ARP requests being sent from the next-node IPv4 address, but with
a node-specific source MAC address. This can make the next-node IPv4 address unreachable.
This is a regression in Gluon 2018.1.