v2014.3.rst 5.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131
  1. Gluon 2014.3
  2. ============
  3. New hardware support
  4. ~~~~~~~~~~~~~~~~~~~~
  5. * Linksys WRT160NL
  6. New features
  7. ~~~~~~~~~~~~
  8. New autoupdater
  9. ---------------
  10. The autoupdater has been rewritten and now limits the time in which updates are
  11. performed normally to the span from 04:00 to 05:00.
  12. The manifest now has two new fields: DATE specifies the time the update was released
  13. and is set automatically by ``make manifest``. PRIORITY specifies the maximum number of
  14. days until the update should be performed (thus lower numbers mean the priority is higher). It must
  15. be set either in ``site.mk`` or on the ``make manifest`` command line.
  16. During the days specified by PRIORITY the update probability will start at 0 and slowly rise to 1
  17. after all PRIORITY days have passed. If more than PRIORITY+1 days have passed, the updater will fall back
  18. to hourly update attempts so nodes which are never active between 04:00 and 05:00 also get an update eventually.
  19. **Note:** For the new update logic to work, a valid NTP server reachable over the mesh (over IPv6) must
  20. be configured in the ``site.mk``. When the updater can't determine the correct time, it will fall back to
  21. a behavior similar to the old implementation.
  22. Seperation of announced data
  23. ----------------------------
  24. The data announced by alfred has been split into two data types:
  25. * *nodeinfo* (type 158) contains all static information about a node
  26. * *statistics* (type 159) contains all dynamic information about a node
  27. Both types also contain a new field ``node_id`` which contains an arbitrary unique ID
  28. (currently the primary MAC address) which can be used to correlate the *nodeinfo*
  29. and *statistics* information.
  30. gluon-announced
  31. ---------------
  32. A new daemon has been added in a new package ``gluon-announced``. This daemon can be
  33. used for querying the *nodeinfo* data of a node via link-local multicast on the ad-hoc
  34. interfaces.
  35. At the moment, this daemon is not used, but we recommend including it in ``site.mk`` nevertheless
  36. as we plan to implement a new status page showing some information about the neighbor nodes in
  37. the next version of Gluon.
  38. VPN over IPv6
  39. -------------
  40. Using fastd over IPv6 should now work fine (although it hasn't been tested extensively).
  41. Please note that the MTU 1426 used by many communities for VPN over IPv4 is too big for IPv6 as
  42. the IPv6 header is 20 bytes longer (fastd over IPv4 has an overhead of 66 bytes,
  43. fastd over IPv6 has an overhead of 86 bytes).
  44. More modular Config Mode
  45. ------------------------
  46. The package ``gluon-config-mode`` has been split up into multiple packages to simplify the development of own
  47. extensions. The low-level logic (handling of the button, starting the services for the config mode) has been moved
  48. into a new package ``gluon-setup-mode``, while ``gluon-config-mode`` only contains the frontend now.
  49. Extended Expert Mode
  50. --------------------
  51. The Expert Mode how has a nice info page. In addition, the new package ``gluon-luci-portconfig`` has been added
  52. which allows simple configuration of batman-adv on the WAN interface.
  53. Site validators
  54. ---------------
  55. The content of the ``site.conf`` is now validated when the images are built to make it less likely to accidentially
  56. build broken images.
  57. gluon-firewall
  58. --------------
  59. The package ``gluon-firewall`` has been removed, its features are now part of the packages ``gluon-core`` and
  60. ``gluon-mesh-batman-adv``.
  61. gluon-ath9k-workaround
  62. ----------------------
  63. This package installs a cron job which tries to recognize ath9k hangs and restart the WLAN while recording some information.
  64. It is very rudimentary and we can't really recommend using it on "production" nodes.
  65. Bugfixes
  66. ~~~~~~~~
  67. Improved ath9k stability
  68. ------------------------
  69. Multiple bugs in the WLAN driver ath9k were fixed upstream, which should greatly improve the WLAN stability.
  70. odhcp6c 50d-Bug
  71. ---------------
  72. An important update for odhcp6c fixes a bug which caused Gluon nodes to lose their IPv6 addresses on br-client after an uptime
  73. of 50 days, making the nodes unable perform an automated update (besides other issues).
  74. IPv6 preference
  75. ---------------
  76. Commands like ``wget`` now prefer IPv6 for domains with both AAAA and A records, allowing to use such domains for the autoupdater URLs
  77. and as NTP servers in the ``site.conf``.
  78. Site changes
  79. ~~~~~~~~~~~~
  80. * ``site.conf``
  81. - The ``probability`` fields for the autoupdater branches can be dropped as they aren't used anymore
  82. - The type of the ``enabled`` options of the ``gluon-simple-tc`` configuration has been changed to boolean, so ``true`` and ``false`` must be used instead of 1 and 0 now
  83. * ``site.mk``
  84. - Obsolete packages:
  85. + ``gluon-firewall``
  86. - Recommended new packages:
  87. + ``gluon-announced``
  88. + ``gluon-luci-portconfig``
  89. - GLUON_PRIORITY must be set in ``site.mk`` or on the ``make manifest`` commandline. Use ``GLUON_PRIORITY ?= 0`` in ``site.mk`` to allow overriding it on the commandline.
  90. Internals
  91. ~~~~~~~~~
  92. Some internal changes not mentioned before which are interesting for developers:
  93. * Many more shell scripts have been converted to Lua
  94. * ``gluon-mesh-vpn-fastd`` now uses the new package ``gluon-wan-dnsmasq``, which provides a secondary DNS server on port 54
  95. that is only reachable from *localhost* and uses the DNS servers on the WAN interface for everything. This allowed us to
  96. remove some ugly hacks which were making the DNS servers used depend on the domain being resolved.
  97. For IPv6, the default route is now controlled via packet marks, so the secondary DNS server and fastd set the packet mark
  98. so they use the default route provided on the WAN interface instead of the mesh.