site.rst 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489
  1. Site configuration
  2. ==================
  3. The ``site`` consists of the files ``site.conf`` and ``site.mk``.
  4. In the first community based values are defined, which both are processed
  5. during the build process and runtime.
  6. The last is directly included in the make process of Gluon.
  7. Configuration
  8. -------------
  9. The ``site.conf`` is a lua dictionary with the following defined keys.
  10. hostname_prefix
  11. A string which shall prefix the default hostname of a device.
  12. site_name
  13. The name of your community.
  14. site_code
  15. The code of your community. It is good practice to use the TLD of
  16. your community here.
  17. prefix4 \: optional
  18. The IPv4 Subnet of your community mesh network in CIDR notation, e.g.
  19. ::
  20. prefix4 = '10.111.111.0/18'
  21. Required if ``next_node.ip4`` is set.
  22. prefix6
  23. The IPv6 subnet of your community mesh network, e.g.
  24. ::
  25. prefix6 = 'fdca::ffee:babe:1::/64'
  26. timezone
  27. The timezone of your community live in, e.g.
  28. ::
  29. -- Europe/Berlin
  30. timezone = 'CET-1CEST,M3.5.0,M10.5.0/3'
  31. ntp_server
  32. List of NTP servers available in your community or used by your community, e.g.:
  33. ::
  34. ntp_servers = {'1.ntp.services.ffeh','2.ntp.services.ffeh'}
  35. This NTP servers must be reachable via IPv6 from the nodes. If you don't want to set an IPv6 address
  36. explicitly, but use a hostname (which is recommended), see also the :ref:`FAQ <faq-dns>`.
  37. opkg \: optional
  38. ``opkg`` package manager configuration.
  39. There are two optional fields in the ``opkg`` section:
  40. - ``openwrt`` overrides the default OpenWrt repository URL
  41. - ``extra`` specifies a table of additional repositories (with arbitrary keys)
  42. ::
  43. opkg = {
  44. openwrt = 'http://opkg.services.ffeh/openwrt/%n/%v/%S/packages',
  45. extra = {
  46. modules = 'http://opkg.services.ffeh/modules/gluon-%GS-%GR/%S',
  47. },
  48. }
  49. There are various patterns which can be used in the URLs:
  50. - ``%n`` is replaced by the OpenWrt version codename (e.g. "chaos_calmer")
  51. - ``%v`` is replaced by the OpenWrt version number (e.g. "15.05")
  52. - ``%S`` is replaced by the target architecture (e.g. "ar71xx/generic")
  53. - ``%GS`` is replaced by the Gluon site code (as specified in ``site.conf``)
  54. - ``%GV`` is replaced by the Gluon version
  55. - ``%GR`` is replaced by the Gluon release (as specified in ``site.mk``)
  56. regdom \: optional
  57. The wireless regulatory domain responsible for your area, e.g.:
  58. ::
  59. regdom = 'DE'
  60. Setting ``regdom`` is mandatory if ``wifi24`` or ``wifi5`` is defined.
  61. wifi24 \: optional
  62. WLAN configuration for 2.4 GHz devices.
  63. ``channel`` must be set to a valid wireless channel for your radio.
  64. There are currently three interface types available. You many choose to
  65. configure any subset of them:
  66. - ``ap`` creates a master interface where clients may connect
  67. - ``mesh`` creates an 802.11s mesh interface with forwarding disabled
  68. - ``ibss`` creates an ad-hoc interface
  69. Each interface may be disabled by setting ``disabled`` to ``true``.
  70. This will only affect new installations.
  71. Upgrades will not changed the disabled state.
  72. Additionally it is possible to configure the ``supported_rates`` and ``basic_rate``
  73. of each radio. Both are optional, by default hostapd/driver dictate the rates.
  74. If ``supported_rates`` is set, ``basic_rate`` is required, because ``basic_rate``
  75. has to be a subset of ``supported_rates``.
  76. The example below disables 802.11b rates.
  77. ``ap`` requires a single parameter, a string, named ``ssid`` which sets the
  78. interface's ESSID.
  79. ``mesh`` requires a single parameter, a string, named ``id`` which sets the mesh id.
  80. ``ibss`` requires two parametersr: ``ssid`` (a string) and ``bssid`` (a MAC).
  81. An optional parameter ``vlan`` (integer) is supported.
  82. Both ``mesh`` and ``ibss`` accept an optional ``mcast_rate`` (kbit/s) parameter for
  83. setting the default multicast datarate.
  84. ::
  85. wifi24 = {
  86. channel = 11,
  87. supported_rates = {6000, 9000, 12000, 18000, 24000, 36000, 48000, 54000},
  88. basic_rate = {6000, 9000, 18000, 36000, 54000},
  89. ap = {
  90. ssid = 'entenhausen.freifunk.net',
  91. },
  92. mesh = {
  93. id = 'entenhausen-mesh',
  94. mcast_rate = 12000,
  95. },
  96. ibss = {
  97. ssid = 'ff:ff:ff:ee:ba:be',
  98. bssid = 'ff:ff:ff:ee:ba:be',
  99. mcast_rate = 12000,
  100. },
  101. },
  102. wifi5 \: optional
  103. Same as `wifi24` but for the 5Ghz radio.
  104. next_node \: package
  105. Configuration of the local node feature of Gluon
  106. ::
  107. next_node = {
  108. ip4 = '10.23.42.1',
  109. ip6 = 'fdca:ffee:babe:1::1',
  110. mac = 'ca:ff:ee:ba:be:00'
  111. }
  112. The IPv4 next-node address is optional.
  113. mesh \: optional
  114. Options specific to routing protocols.
  115. At the moment, only the ``batman_adv`` routing protocol has such options:
  116. The optional value ``gw_sel_class`` sets the gateway selection class. The default
  117. class 20 is based on the link quality (TQ) only, class 1 is calculated from
  118. both the TQ and the announced bandwidth.
  119. ::
  120. mesh = {
  121. batman_adv = {
  122. gw_sel_class = 1,
  123. },
  124. }
  125. fastd_mesh_vpn
  126. Remote server setup for the fastd-based mesh VPN.
  127. The `enabled` option can be set to true to enable the VPN by default.
  128. If `configurable` is set to `false` or unset, the method list will be replaced on updates
  129. with the list from the site configuration. Setting `configurable` to `true` will allow the user to
  130. add the method ``null`` to the beginning of the method list or remove ``null`` from it,
  131. and make this change survive updates. Setting `configurable` is necessary for the
  132. package `gluon-luci-mesh-vpn-fastd`, which adds a UI for this configuration.
  133. In any case, the ``null`` method should always be the first method in the list
  134. if it is supported at all. You should only set `configurable` to `true` if the
  135. configured peers support both the ``null`` method and methods with encryption.
  136. You can set syslog_level from verbose (default) to warn to reduce syslog output.
  137. ::
  138. fastd_mesh_vpn = {
  139. methods = {'salsa2012+umac'},
  140. -- enabled = true,
  141. -- configurable = true,
  142. -- syslog_level = 'warn',
  143. mtu = 1280,
  144. groups = {
  145. backbone = {
  146. -- Limit number of connected peers from this group
  147. limit = 1,
  148. peers = {
  149. peer1 = {
  150. key = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
  151. -- Having multiple domains prevents SPOF in freifunk.net
  152. remotes = {
  153. 'ipv4 "vpn1.entenhausen.freifunk.net" port 10000',
  154. 'ipv4 "vpn1.entenhausener-freifunk.de" port 10000',
  155. },
  156. },
  157. peer2 = {
  158. key = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
  159. -- You can also omit the ipv4 to allow both connection via ipv4 and ipv6
  160. remotes = {'"vpn2.entenhausen.freifunk.net" port 10000'},
  161. },
  162. },
  163. -- Optional: nested peer groups
  164. -- groups = {
  165. -- lowend_backbone = {
  166. -- limit = 1,
  167. -- peers = ...
  168. -- },
  169. -- },
  170. },
  171. -- Optional: additional peer groups, possibly with other limits
  172. -- peertopeer = {
  173. -- limit = 10,
  174. -- peers = { ... },
  175. -- },
  176. },
  177. bandwidth_limit = {
  178. -- The bandwidth limit can be enabled by default here.
  179. enabled = false,
  180. -- Default upload limit (kbit/s).
  181. egress = 200,
  182. -- Default download limit (kbit/s).
  183. ingress = 3000,
  184. },
  185. }
  186. mesh_on_wan \: optional
  187. Enables the mesh on the WAN port (``true`` or ``false``).
  188. mesh_on_lan \: optional
  189. Enables the mesh on the LAN port (``true`` or ``false``).
  190. poe_passthrough \: optional
  191. Enable PoE passthrough by default on hardware with such a feature.
  192. autoupdater \: package
  193. Configuration for the autoupdater feature of Gluon.
  194. The mirrors are checked in random order until the manifest could be downloaded
  195. successfully or all mirrors have been tried.
  196. ::
  197. autoupdater = {
  198. branch = 'stable',
  199. branches = {
  200. stable = {
  201. name = 'stable',
  202. mirrors = {
  203. 'http://[fdca:ffee:babe:1::fec1]/firmware/stable/sysupgrade/',
  204. 'http://autoupdate.entenhausen.freifunk.net/firmware/stable/sysupgrade/',
  205. },
  206. -- Number of good signatures required
  207. good_signatures = 2,
  208. pubkeys = {
  209. 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', -- someguy
  210. 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', -- someother
  211. }
  212. }
  213. }
  214. }
  215. All configured mirrors must be reachable from the nodes via IPv6. If you don't want to set an IPv6 address
  216. explicitly, but use a hostname (which is recommended), see also the :ref:`FAQ <faq-dns>`.
  217. roles \: optional
  218. Optional role definitions. Nodes will announce their role inside the mesh.
  219. This will allow in the backend to distinguish between normal, backbone and
  220. service nodes or even gateways (if they advertise that role). It is up to
  221. the community which roles to define. See the section below as an example.
  222. ``default`` takes the default role which is set initially. This value should be
  223. part of ``list``. If you want node owners to change the role via config mode add
  224. the package ``gluon-luci-node-role`` to ``site.mk``.
  225. The strings to display in the LuCI interface can be configured per language in the
  226. ``i18n/en.po``, ``i18n/de.po``, etc. files of the site repository using message IDs like
  227. ``gluon-luci-node-role:role:node`` and ``gluon-luci-node-role:role:backbone``.
  228. ::
  229. roles = {
  230. default = 'node',
  231. list = {
  232. 'node',
  233. 'test',
  234. 'backbone',
  235. 'service',
  236. },
  237. },
  238. setup_mode \: package
  239. Allows skipping setup mode (config mode) at first boot when attribute
  240. ``skip`` is set to ``true``. This is optional and may be left out.
  241. ::
  242. setup_mode = {
  243. skip = true,
  244. },
  245. legacy \: package
  246. Configuration for the legacy upgrade path.
  247. This is only required in communities upgrading from Lübeck's LFF-0.3.x.
  248. ::
  249. legacy = {
  250. version_files = {'/etc/.freifunk_version_keep', '/etc/.eff_version_keep'},
  251. old_files = {'/etc/config/config_mode', '/etc/config/ffeh', '/etc/config/freifunk'},
  252. config_mode_configs = {'config_mode', 'ffeh', 'freifunk'},
  253. fastd_configs = {'ffeh_mesh_vpn', 'mesh_vpn'},
  254. mesh_ifname = 'freifunk',
  255. tc_configs = {'ffki', 'freifunk'},
  256. wifi_names = {'wifi_freifunk', 'wifi_freifunk5', 'wifi_mesh', 'wifi_mesh5'},
  257. }
  258. Packages
  259. --------
  260. The ``site.mk`` is a Makefile which should define constants
  261. involved in the build process of Gluon.
  262. GLUON_SITE_PACKAGES
  263. Defines a list of packages which should be installed additionally
  264. to the ``gluon-core`` package.
  265. GLUON_RELEASE
  266. The current release version Gluon should use.
  267. GLUON_PRIORITY
  268. The default priority for the generated manifests (see the autoupdater documentation
  269. for more information).
  270. GLUON_REGION
  271. Region code to build into images where necessary. Valid values are the empty string,
  272. ``us`` and ``eu``.
  273. GLUON_LANGS
  274. List of languages (as two-letter-codes) to be included in the web interface. Should always contain
  275. ``en``.
  276. .. _site-config-mode-texts:
  277. Config mode texts
  278. -----------------
  279. The community-defined texts in the config mode are configured in PO files in the ``i18n`` subdirectory
  280. of the site configuration. The message IDs currently defined are:
  281. gluon-config-mode:welcome
  282. Welcome text on the top of the config wizard page.
  283. gluon-config-mode:pubkey
  284. Information about the public VPN key on the reboot page.
  285. gluon-config-mode:reboot
  286. General information shown on the reboot page.
  287. There is a POT file in the site example directory which can be used to create templates
  288. for the language files. The command ``msginit -l en -i ../../docs/site-example/i18n/gluon-site.pot``
  289. can be used from the ``i18n`` directory to create an initial PO file called ``en.po`` if the ``gettext``
  290. utilities are installed.
  291. .. note::
  292. An empty ``msgstr``, as is the default after running ``msginit``, leads to
  293. the ``msgid`` being printed as-is. It does *not* hide the whole text, as
  294. might be expected.
  295. Depending on the context, you might be able to use comments like
  296. ``<!-- empty -->`` as translations to effectively hide the text.
  297. Site modules
  298. ------------
  299. The file ``modules`` in the site repository is completely optional and can be used
  300. to supply additional package feeds from which packages are built. The git repositories
  301. specified here are retrieved in addition to the default feeds when ``make update``
  302. it called.
  303. This file's format is very similar to the toplevel ``modules`` file of the Gluon
  304. tree, with the important different that the list of feeds must be assigned to
  305. the variable ``GLUON_SITE_FEEDS``. Multiple feed names must be separated by spaces,
  306. for example::
  307. GLUON_SITE_FEEDS='foo bar'
  308. The feed names may only contain alphanumerical characters, underscores and slashes.
  309. For each of the feeds, the following variables are used to specify how to update
  310. the feed:
  311. PACKAGES_${feed}_REPO
  312. The URL of the git repository to clone (usually ``git://`` or ``http(s)://``)
  313. PACKAGES_${feed}_COMMIT
  314. The commit ID of the repository to use
  315. PACKAGES_${feed}_BRANCH
  316. Optional: The branch of the repository the given commit ID can be found in.
  317. Defaults to the default branch of the repository (usually ``master``)
  318. These variables are always all uppercase, so for an entry ``foo`` in GLUON_SITE_FEEDS,
  319. the corresponding configuration variables would be ``PACKAGES_FOO_REPO``,
  320. ``PACKAGES_FOO_COMMIT`` and ``PACKAGES_FOO_BRANCH``. Slashes in feed names are
  321. replaced by underscores to get valid shell variable identifiers.
  322. Examples
  323. --------
  324. site.mk
  325. ^^^^^^^
  326. .. literalinclude:: ../site-example/site.mk
  327. :language: makefile
  328. site.conf
  329. ^^^^^^^^^
  330. .. literalinclude:: ../site-example/site.conf
  331. :language: lua
  332. i18n/en.po
  333. ^^^^^^^^^^
  334. .. literalinclude:: ../site-example/i18n/en.po
  335. :language: po
  336. i18n/de.po
  337. ^^^^^^^^^^
  338. .. literalinclude:: ../site-example/i18n/de.po
  339. :language: po
  340. modules
  341. ^^^^^^^
  342. .. literalinclude:: ../site-example/modules
  343. :language: makefile
  344. site-repos in the wild
  345. ^^^^^^^^^^^^^^^^^^^^^^
  346. This is a non-exhaustive list of site-repos from various communities:
  347. * `site-ffa <https://github.com/tecff/site-ffa>`_ (Altdorf, Landshut & Umgebung)
  348. * `site-ffac <https://github.com/ffac/site>`_ (Regio Aachen)
  349. * `site-ffbs <https://github.com/ffbs/site-ffbs>`_ (Braunschweig)
  350. * `site-ffhb <https://github.com/FreifunkBremen/gluon-site-ffhb>`_ (Bremen)
  351. * `site-ffda <https://github.com/freifunk-darmstadt/site-ffda>`_ (Darmstadt)
  352. * `site-ffeh <https://github.com/freifunk-ehingen/site-ffeh>`_ (Ehingen)
  353. * `site-fffl <https://github.com/freifunk-flensburg/site-fffl>`_ (Flensburg)
  354. * `site-ffgoe <https://github.com/freifunk-goettingen/site-ffgoe>`_ (Göttingen)
  355. * `site-ffgt-rhw <https://github.com/ffgtso/site-ffgt-rhw>`_ (Guetersloh)
  356. * `site-ffhh <https://github.com/freifunkhamburg/site-ffhh>`_ (Hamburg)
  357. * `site-ffho <https://git.c3pb.de/freifunk-pb/site-ffho>`_ (Hochstift)
  358. * `site-ffhgw <https://github.com/lorenzo-greifswald/site-ffhgw>`_ (Greifswald)
  359. * `site-ffka <https://github.com/ffka/site-ffka>`_ (Karlsruhe)
  360. * `site-ffki <http://git.freifunk.in-kiel.de/ffki-site/>`_ (Kiel)
  361. * `site-fflz <https://github.com/freifunk-lausitz/site-fflz>`_ (Lausitz)
  362. * `site-ffl <https://github.com/freifunk-leipzig/freifunk-gluon-leipzig>`_ (Leipzig)
  363. * `site-ffhl <https://github.com/freifunk-luebeck/site-ffhl>`_ (Lübeck)
  364. * `site-fflg <https://github.com/kartenkarsten/site-fflg>`_ (Lüneburg)
  365. * `site-ffmd <https://github.com/FreifunkMD/site-ffmd>`_ (Magdeburg)
  366. * `site-ffmwu <https://github.com/freifunk-mwu/sites-ffmwu>`_ (Mainz, Wiesbaden & Umgebung)
  367. * `site-ffmyk <https://github.com/FreifunkMYK/site-ffmyk>`_ (Mayen-Koblenz)
  368. * `site-ffmo <https://github.com/ffruhr/site-ffmo>`_ (Moers)
  369. * `site-ffmg <https://github.com/ffruhr/site-ffmg>`_ (Mönchengladbach)
  370. * `site-ffm <https://github.com/freifunkMUC/site-ffm>`_ (München)
  371. * `site-ffhmue <https://github.com/Freifunk-Muenden/site-conf>`_ (Münden)
  372. * `site-ffms <https://github.com/FreiFunkMuenster/site-ffms>`_ (Münsterland)
  373. * `site-neuss <https://github.com/ffne/site-neuss>`_ (Neuss)
  374. * `site-ffniers <https://github.com/ffruhr/site-ffniers>`_ (Niersufer)
  375. * `site-ffnw <https://git.nordwest.freifunk.net/ffnw-firmware/siteconf/tree/master>`_ (Nordwest)
  376. * `site-ffrgb <https://github.com/ffrgb/site-ffrgb>`_ (Regensburg)
  377. * `site-ffrn <https://github.com/Freifunk-Rhein-Neckar/site-ffrn>`_ (Rhein-Neckar)
  378. * `site-ffruhr <https://github.com/ffruhr?utf8=✓&query=site>`_ (Ruhrgebiet, Multi-Communities)
  379. * `site-ffs <https://github.com/freifunk-stuttgart/site-ffs>`_ (Stuttgart)
  380. * `site-fftr <https://github.com/freifunktrier/site-fftr>`_ (Trier)