v2017.1.1.rst 1.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. Gluon 2017.1.1
  2. ==============
  3. Bugfixes
  4. ~~~~~~~~
  5. * The autoupdater manifest has been extended to allow automatic upgrades from
  6. old *x86-kvm* and *x86-xen_domu* systems to the new *x86-generic* image
  7. (`869ceb4 <https://github.com/freifunk-gluon/gluon/commit/869ceb425cd5f9db3eafddcc52377fd94c6ba0dd>`_)
  8. * Make flash writable again on Ubiquiti PicoStations with certain bootloader
  9. versions (and possibly other devices)
  10. (`9a787c9 <https://github.com/freifunk-gluon/gluon/commit/9a787c9878069158151c843b8fd9aa338815d61e>`_)
  11. Units affected by this issue running Gluon v2017.1 can't leave config mode and
  12. no regular sysupgrades are possible. TFTP recovery is necessary to make them
  13. work again.
  14. * Add workaround to prevent sporadic segfaults of busybox (ash) when running shell scripts on ar71xx
  15. (`#1157 <https://github.com/freifunk-gluon/gluon/issues/1157>`_)
  16. * Disable batman-adv multicast optimizations to work around issue causing large
  17. amounts of management traffic
  18. (`819758f <https://github.com/freifunk-gluon/gluon/commit/819758f4250af8820851945ba1a6c17748b0ab4b>`_)
  19. Multicast optimizations will be enabled again when a proper fix is available.
  20. Known issues
  21. ~~~~~~~~~~~~
  22. * Default TX power on many Ubiquiti devices is too high, correct offsets are unknown (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
  23. Reducing the TX power in the Advanced Settings is recommended.
  24. * 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>`_)
  25. This may lead to issues in environments where a fixed MAC address is expected (like VMware when promicious mode is disallowed).
  26. * Inconsistent respondd API (`#522 <https://github.com/freifunk-gluon/gluon/issues/522>`_)
  27. The current API is inconsistent and will be replaced eventually. The old API will still be supported for a while.