Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
ffbs-gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
darkbit
ffbs-gluon
Commits
b8c81a45
Unverified
Commit
b8c81a45
authored
6 years ago
by
Matthias Schiffer
Browse files
Options
Downloads
Patches
Plain Diff
docs: update v2018.1 release notes
parent
839afa57
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/releases/v2018.1.rst
+18
-0
18 additions, 0 deletions
docs/releases/v2018.1.rst
with
18 additions
and
0 deletions
docs/releases/v2018.1.rst
+
18
−
0
View file @
b8c81a45
...
...
@@ -400,3 +400,21 @@ Known issues
Optimizations in Gluon 2018.1 have significantly improved memory usage.
There are still known bugs leading to unreasonably high load that we hope to
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.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment