v2017.1.2.rst 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. Gluon 2017.1.2 (in development)
  2. ===============================
  3. New features
  4. ~~~~~~~~~~~~
  5. * Preserve *gw_mode* on sysupgrades (`#1196 <https://github.com/freifunk-gluon/gluon/issues/1196>`_)
  6. When a Gluon node is used as uplink (for example by connecting it to a router with
  7. a DHCP server directly, instead of using non-Gluon servers for the internet uplink),
  8. the *gw_mode* must be set to *server* on that node. The changed *gw_mode* is now
  9. preserved on upgrades.
  10. * Allow configuring the batman-adv routing algorithm (*BATMAN IV* or *BATMAN V*)
  11. in *site.conf* (`#1185 <https://github.com/freifunk-gluon/gluon/issues/1185>`_)
  12. *BATMAN V* still hasn't received extensive testing (and is incompatible with *BATMAN IV*).
  13. This new option allows to set up *BATMAN V*-based test meshes. If unset, the routing
  14. algorithm will default to *BATMAN IV*.
  15. Configuration:
  16. .. code-block:: lua
  17. mesh = {
  18. batman_adv = {
  19. routing_algo = 'BATMAN_V'
  20. }
  21. }
  22. * New *show-release* Make target
  23. The command ``make show-release`` can be used to print the release number
  24. defined by *GLUON_RELEASE* to the standard output. This can be useful for build scripts
  25. when a ``$(shell ...)`` expression is used in *site.mk* to generate the release
  26. number.
  27. Bugfixes
  28. ~~~~~~~~
  29. * The image build code used for some devices has been fixed, solving multiple
  30. issues (`#1193 <https://github.com/freifunk-gluon/gluon/issues/1193>`_)
  31. Problems caused by this issue include:
  32. - sysupgrade rejecting Allnet images
  33. - OpenMesh devices losing their configuration on upgrades
  34. This is a regression in Gluon v2017.1.
  35. * Improve sysupgrade error handling (`#1160 <https://github.com/freifunk-gluon/gluon/issues/1160>`_)
  36. If for some reason processes don't react to SIGKILL (usually because of a kernel bug),
  37. a node could hang forever in sysupgrade, requiring a power cycle. This has been
  38. fixed, triggering a reboot instead.
  39. * Also display *gluon-config-mode:novpn* message when Tunneldigger is installed, but disabled
  40. (`#1172 <https://github.com/freifunk-gluon/gluon/issues/1172>`_)
  41. It was only displayed on nodes with fastd before.
  42. Known issues
  43. ~~~~~~~~~~~~
  44. * Default TX power on many Ubiquiti devices is too high, correct offsets are unknown (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
  45. Reducing the TX power in the Advanced Settings is recommended.
  46. * 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>`_)
  47. This may lead to issues in environments where a fixed MAC address is expected (like VMware when promicious mode is disallowed).
  48. * Inconsistent respondd API (`#522 <https://github.com/freifunk-gluon/gluon/issues/522>`_)
  49. The current API is inconsistent and will be replaced eventually. The old API will still be supported for a while.
  50. * Sporadic segfaults of busybox (ash) when running shell scripts on ar71xx
  51. (`#1157 <https://github.com/freifunk-gluon/gluon/issues/1157>`_)
  52. The workaround added in Gluon v2017.1.1 has greatly reduced the frequency of
  53. segfaults, but did not make them disappear completely.