site.rst 18 KB

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